From: | Dimitri Fontaine <dfontaine(at)hi-media(dot)com> |
---|---|
To: | Jesper Krogh <jesper(at)krogh(dot)cc> |
Cc: | Bruce Momjian <bruce(at)momjian(dot)us>, Robert Haas <robertmhaas(at)gmail(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Magnus Hagander <magnus(at)hagander(dot)net>, Peter Eisentraut <peter_e(at)gmx(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: pg_migrator to /contrib in a later 9.0 beta |
Date: | 2010-05-06 10:03:13 |
Message-ID: | 87aasdjqji.fsf@hi-media-techno.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Jesper Krogh <jesper(at)krogh(dot)cc> writes:
> I did go the painful way (dump+restore) at that point in time.
> It was an 8.1 - 8.3 migration. Since then data has grown and the dump
> restore is even less favorable on the 8.3 -> 9.0 migration.
>
> So in general the pg_migrator way seems to be the only way to aviod
> the slony way which is orders of magnitude more complicated.
Right in the middle there's the Londiste way. It works like Slony but
the setup is much easier.
Regards,
--
Dimitri Fontaine
PostgreSQL DBA, Architecte
From | Date | Subject | |
---|---|---|---|
Next Message | Yeb Havinga | 2010-05-06 10:08:46 | Re: max_standby_delay considered harmful |
Previous Message | Florian Pflug | 2010-05-06 09:36:20 | Re: max_standby_delay considered harmful |