Hi,
I have set my Postgres into replication mode Master-Slave and it works good.
Though, I have some question about maintaining it.
Let me start from the beginning. How I set it up (briefly):
1. Stand Alone postgres (future MASTER) has been set to archive data to: /datastore/WAL (archive_command = 'cp %p /datastore/WAL/%f && gzip /datastore/WAL/%f ')
2. I have shared /datastore/WAL over NFS
3. I prepared SLAVE machine and created initial database out of MASTER's WAL-archival (over NFS) by preparing following file:
$ vi /var/lib/pgsql/9.2/data/recovery.conf
restore_command = 'gunzip -c /datastore/WAL/%f > %p'
standby_mode = 'on'
primary_conninfo = 'host=MASTER_IP_ port=5432 user=rep password=password'
trigger_file = '/var/lib/pgsql/MASTER.trigger'
4. One last thing - I keep archive_mode = off on the SLAVE.
The above works perfect.
Now, here I need your help to understand what is happening in case following scenario.
SCENARIO:
I turn off SLAVE for some time (and MASTER receives a lot of new data) and later I turn SLAVE on.
Is it true/correct:
- SLAVE restores missing data/delta over NFS (from MASTER's archival). This is due to existing /var/lib/pgsql/9.2/data/recovery.conf and entry: restore_command = 'gunzip -c /datastore/WAL/%f > %p'
- Once restore is done, SLAVE will keep replicate new data from MASTER (btw. it is SLAVE who request replication, correct?)
Can anyone please confirm that my above assumption is correct and if not correct it?
Best regards,
czezz
