The operations that require write locks on the main storage tables are at the very top of the migrate_from_2.0_to_2.2.pgsql script. It's the block of SQL that recasts the messageblks as bytea instead of text. Depending on when you started using DBMail, you might already have bytea messageblks, and you'll be able to drop this portion of the upgrade script.
The remaining sections only add columns and new tables. Nothing is renamed or removed. I believe that it can safely run on a live table. Once the tables schemas are updated, you can take down your DBMail 2.0 processes and spin up DBMail 2.2. You then need to run dbmail-util -ay to populate the cache tables. I believe that you can safely do this while DBMail 2.2 is running; new messages will have their cache entries fully inserted, and old messages will run in a degraded mode. Aaron On Fri, Dec 1, 2006, Jesse Norell <[EMAIL PROTECTED]> said: > I believe one table (messageblks?) changed types such that it is no > longer possible to run 2.0 daemons against the 2.2 schema under > postgres. If that's correct, then no, you have to stop the 2.0 daemons > to update. > > If I'm wrong on that, and the 2.0 daemons can actually work with a 2.2 > schema, they you can probably leave the 2.0 pop/imap daemons running, > run the migration script against them while live (though I'd guess some > of the table locks will take so long, they might as well be down...), > then when done, shut down the 2.0 daemons, run the upgrade again (which > should be faster that time), then fire up 2.2. You're probably safer > just to shut down 2.0. :) > > > > On Fri, 2006-12-01 at 11:01 -0500, Rod K wrote: >> Is there any issues with leaving 2.0.11 >> running while migration is going on or once complete before shutting >> down 2.0.11 and restarting with 2.2? > -- > Jesse Norell - [EMAIL PROTECTED] > Kentec Communications, Inc. > > _______________________________________________ > DBmail mailing list > [email protected] > https://mailman.fastxs.nl/mailman/listinfo/dbmail > --
