I'll be running a test conversion on a duplicate DB today and will
report back.
I'm wondering if there isn't a better way to run the conversion.
Perhaps a model like this:
1) Create NEW DB with 2.2 schema
2) Upgrade daemons. stop 2.0
3) Copy minimal tables (at least users/alias/mailboxes) to new DB
4) Change config to use new DB
5) start 2.2
6) Import remaining tables
This would allow nearly continuous operation with the only drawback
being access to emails received prior to upgrade being delayed until
imported.
Matthew O'Connor wrote:
Totally non-scientific and based on my memory, after I got the process
down (I scripted everything on a test server), it took me maybe about
2 hours for about 6G of data on an 64 with a decent SATA drive, using
PostgreSQL 8.1. It was a lot slower, but just before 2.2 was release
Paul made a significant speed-up in the envelope created code.
I highly recommend testing your upgrade on a test server, I ran into
many problems before I finally got up an running on 2.2, and 2.2
daemons can *NOT* run against a 2.0 database.
Matt
Niblett, David A wrote:
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.
