Me too, as I have 32G I need to do, and expect a high pain and suffering rate.
-- David A. Niblett | email: [EMAIL PROTECTED] Network Administrator | Phone: (352) 334-3400 Gainesville Regional Utilities | Web: http://www.gru.net/ -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Friday, December 01, 2006 3:35 PM To: [email protected]; DBMail mailinglist Subject: Re: [Dbmail] postgresql migrate 2.0 to 2.2 I'm curious how long it would take to migrate this much data. On 12/1/2006, "Rod K" <[EMAIL PROTECTED]> wrote: >Tom, > >I'll do that. > >I think what I might do is shutdown dbmail-lmtpd and let postfix queue >inbound but leave POP and IMAP running until the messageblk update is >done. Then shutdown IMAP and POP3, complete the migrate script and >then start all under 2.2. > >Rod > >[EMAIL PROTECTED] wrote: >> Could you replicate the database and test the upgrade to see just how >> long it would take (if everything else hitting the database was off)? >> >> On 12/1/2006, "Rod K" <[EMAIL PROTECTED]> wrote: >> >> >>> I'm currently running dbmail 2.0.11 on a live server with about 15GB >>> of current email. I need to upgrade to 2.2. >>> >>> The problem is that the postgres migrate script is going to take a >>> long time to run with that much email and really, really don't want >>> to take down the server for that long. 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? >>> >>> > >_______________________________________________ >DBmail mailing list >[email protected] https://mailman.fastxs.nl/mailman/listinfo/dbmail > _______________________________________________ DBmail mailing list [email protected] https://mailman.fastxs.nl/mailman/listinfo/dbmail
