From: | Ron Johnson <ron(dot)l(dot)johnson(at)cox(dot)net> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Converting 7.x to 8.x |
Date: | 2007-01-27 15:45:16 |
Message-ID: | 45BB738C.8050805@cox.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 01/27/07 04:13, Anton Melser wrote:
> On 26/01/07, Jim Nasby <decibel(at)decibel(dot)org> wrote:
>> On Jan 25, 2007, at 12:47 PM, Benjamin Smith wrote:
>> > On Tuesday 23 January 2007 13:55, Carlos wrote:
>> >> What would be the faster way to convert a 7.4.x database into an 8.x
>> >> database? A dump of the database takes over 20 hours so we want
>> >> to convert
>> >> the database without having to do a dump and resptore.
>> >
>> > You've probably already accounted for this, but make sure you've
>> > tried your
>> > options for loading the database. Using long ("insert") form vs
>> > copy can make
>> > a *huge* performance difference.
>>
>> In case no one's mentioned it already, you can also perform this
>> migration using Slony, by making the 7.4 database the master, and
>> replicating to an 8.x database.
>
> In case this is not what you meant above, you can pipe a dump directly
> into psql, so that keeps it to only 20hrs...
Using slony or "piped pg_dump" requires that you have *double* the
amount of disk space. Having a *very large* database and double
capacity of SCSI disks (including storage controllers, shelves, etc,
etc) is expensive, and might not be available.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFFu3OMS9HxQb37XmcRAraIAJ0TbS3O4kh5W5UDZJM/PaRZARkLOACeNteM
YMN6nG/6RzMOWv9apJxwO6Q=
=F96M
-----END PGP SIGNATURE-----
From | Date | Subject | |
---|---|---|---|
Next Message | Magnus Hagander | 2007-01-27 16:21:23 | Re: Stats collector frozen? |
Previous Message | Magnus Hagander | 2007-01-27 15:09:53 | Re: Predicted lifespan of different PostgreSQL branches |