Re: Geographical redundancy - Mailing list pgsql-general

From Ben
Subject Re: Geographical redundancy
Date
Msg-id Pine.LNX.4.64.0701021113160.8626@localhost.localdomain
Whole thread Raw
In response to Re: Geographical redundancy  (Dennis <aiwa_azca@yahoo.com>)
Responses Re: Geographical redundancy  (Dennis <aiwa_azca@yahoo.com>)
List pgsql-general
On Sat, 30 Dec 2006, Dennis wrote:

> I was thinking of maybe just having 2nd location receive a PG dump (full
> or incremental) every so often (an hour to 6 hours) and if the main
> location fails majorly, restore the PG cluster from the dump and switch
> DNS settings on the actual sites. I can make sure all website files are
> always in sync on both locations.

Well, first off, you can just rsync your archived WAL files. That may be
easier than playing with pg_dump:

http://www.postgresql.org/docs/8.2/interactive/continuous-archiving.html

But second, and more important given your data-loss desires, if you do it
this way you have a window where you can experience data loss.
Specifically, after a transaction is committed, that commit will be at
risk until the next transfer has completed.

pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: PostgreSQL 8.2.1 expected release date?
Next
From: Anthony Masinton
Date:
Subject: Combining data in different rows?