Skip site navigation (1) Skip section navigation (2)

Peripheral Links

Header And Logo

PostgreSQL
| The world's most advanced open source database.

Site Navigation

Search archives
  Advanced Search

Re: Failover of the Primary database and starting the standby database in Postgresql in PITR configuraiton?


  • From: salman <salmanb(at)quietcaresystems(dot)com>
  • To: libra dba <libra(dot)dba(at)gmail(dot)com>
  • Cc: pgsql-admin(at)postgresql(dot)org
  • Subject: Re: Failover of the Primary database and starting the standby database in Postgresql in PITR configuraiton?
  • Date: Wed, 27 Feb 2008 16:05:47 -0500
  • Message-id: <47C5D0AB.7070102@quietcaresystems.com> <text/plain>



libra dba wrote:
continuing with the postgres replication using WARM STANDBY, what happens to
the wal_files which keeps on generating on the primary?

Do we have to manually remove them or they are removed automatically, once
they have been recovered on the warm standby?

Also a quick question, do we have to have a NFS for the wal_files, which
will be mounted on both the servers, or we can have folders on each server
and configure DRBD between them, so that whatever happens on one is copied
automatically on to the other.

Thanks!


This is what I use -- may not be the best approach, but it has worked quite well for me so far:

archive_command = 'gzip %p; rsync -av %p.gz -e \"ssh -p portNum -i /home/postgres/.ssh/id_dsa\" postgres(at)rhostname:/usr/local/postgresql/archives/recovery/%f.gz && rm -f %p.gz'







Home | Main Index | Thread Index

Privacy Policy | About PostgreSQL
Copyright © 1996 – 2012 PostgreSQL Global Development Group