I also streaming replication _and_ ship WALs them to the slaves, something like: restore_command='rsync -pog master::postgresql-wals/%f %p', so normally the slaves are up to date (via streaming replication) and the WALs are also on the slaves to be able to recover (maybe to some PIT) from them in case something goes wrong.
The recommended setup should be handled more in detail in the docs, since this is a topic where you can make a lot of mistakes :-(
Gerhard
On Tue, Apr 19, 2011 at 11:16 AM, rudi
<rudolone@gmail.com> wrote:
On 04/19/2011 10:09 AM, Gerhard Hintermayer wrote:
assuming you have configured rsyncd on the server as:
[postgresql-data]
uid = postgres
path = /var/lib/postgresql/9.0/data
comment = PostgreSQL 9.0 data dir
exclude = postmaster.log pg_xlog/* postmaster.pid postgresql.conf
So you keep the old pg_xlog ... But, what about wal that the former master hasn't yet sent to the slave? I wonder if the former-master could apply them, becoming out-of-sync with the former-slave (that never recevied those wal).
thanks
--
rudi