On Wed, Oct 13, 2010 at 12:59 PM, Evan D. Hoffman
wrote:
> The Slony method is one I hadn't considered. Since our database is so
> large, even a direct file copy would require some downtime (since we'd
>
If you do go the slony route, you may want to do the replication
incrementally. That is, in
On 14/10/10 00:59, Evan D. Hoffman wrote:
> Thanks, Brian & Jaime. Regarding Slony, would that allow for
> migration to a new version as well - i.e. moving from 8.2 on the old
> machine to 8.4 on the new machine via Slony with minimal downtime?
>
> The Slony method is one I hadn't considered. Si
Thanks, Brian & Jaime. Regarding Slony, would that allow for
migration to a new version as well - i.e. moving from 8.2 on the old
machine to 8.4 on the new machine via Slony with minimal downtime?
The Slony method is one I hadn't considered. Since our database is so
large, even a direct file cop
Yes, we've used Slony for migrating 8.2 -> 8.3 -> 8.4 and plan an using it to
migrate to 9.0 in the near future. You should be able to skip releases as well
like you say 8.2 -> 8.4.
You'll probably want to test out both slony and 8.4 on your development
machines first and make sure everything
Jaime Casanova writes:
> On Wed, Oct 13, 2010 at 11:03 AM, EDH wrote:
>> What I'd like to know is: if I install the latest 8.2.x release - I
>> see 8.2.18 RPMs are available - can I do a straight copy of the
>> contents of /var/lib/pgsql/data/ to the new server and start it up?
>> Or is dump & re
Evan,
Others can probably answer your question better about copying, but in general
we never do that but I think if you use the same arch and major release of
postgresql you will be okay.
We have used Slony successfully for all of our database upgrades, server
maintenance and database moves ov
On Wed, Oct 13, 2010 at 11:03 AM, EDH wrote:
[...]
>
> What I'd like to know is: if I install the latest 8.2.x release - I
> see 8.2.18 RPMs are available - can I do a straight copy of the
> contents of /var/lib/pgsql/data/ to the new server and start it up?
> Or is dump & restore the only real wa
I have a large Postgres DB (1100 GB) that I'd like to move to a new
physical machine. In the past I've done this via pg_dump & restore,
but the DB was much smaller then, and I'm concerned about how long
that would take. The version of pg currently in use is:
PostgreSQL 8.2.5 on x86_64-redhat-lin
