[Pgpool-general] Online recovery by PITR questions
Nico -telmich- Schottelius
nico-pgpool at schottelius.org
Thu May 8 16:39:21 UTC 2008
Hello again!
Just to summarise it:
The scripts
pgpool_remote_start,
recovery_1st_stage_command = 'copy-base-backup' and
recovery_2nd_stage_command = 'pgpool_recovery_pitr'
- must reside in the datadir of all backends
- get the parameters
DATA=$1
RECOVERY_TARGET=$2
RECOVERY_DATA=$3
- are called on some master node that is known to pgpool
The whole recovery process done by
- manually issue pcp_recovery_node
- pgpool executes CHECKPOINT on a master node
- pgpool executes SELECT pgpool_recovery('recovery-script,'target','PGDATA')"
on a master node
- This calls copy-base-backup
- UNCLEAR: This also calls pgpool_recovery_pitr?
- After that pgpool_remote_start is called by pgpool on master
- Then postgres does PITR
- Then the recovered postgres-server accepts connections again
UNCLEAR: -> How does pgpool detect when the postgresql-server is available
again?
- Then it is attached to the cluster again
- normal operation continues, all databases are accessable again
Is that correct so far?
And can you clearify the two unclear points?
Sincerly
Nico
--
Think about Free and Open Source Software (FOSS).
http://nico.schottelius.org/documentations/foss/the-term-foss/
PGP: BFE4 C736 ABE5 406F 8F42 F7CF B8BE F92A 9885 188C
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://pgfoundry.org/pipermail/pgpool-general/attachments/20080508/cad88324/attachment.bin
More information about the Pgpool-general
mailing list