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.
