While doing some tests yesterday I ran into the situation where the
standby database would appear to go back into 'warm' mode after it was
restarted. The set of steps to reproduce the behaviour is:
1/ Setup master and replica with replica using pg_standby
2/ Initialize pgbench schema with size 100 in database 'postgres'
3/ Connect to replica, then disconnect (this step is not necessary I
*think* - just for checking that connection works at this point!)
4/ Shutdown and restart the replica - there is no "database has now
reached consistent state" message in the log, and you cannot connect
Again this is head from 2nd Nov with v5 patch applied on Freebsd
7.1-Prerelease.
The log fragment is:
LOG: restored log file "000000010000000000000068" from archive
DEBUG: executing restore command "pg_standby -l -d -s 2 -t
/tmp/pgsql.trigger.5439 /data0/pgarchive/8.4 000000010000000000000069
pg_xlog/RECOVERYXLOG 000000010000000000000060 2>>standby.log"
DEBUG: forked new backend, pid=2981 socket=7
FATAL: the database system is starting up
DEBUG: proc_exit(1)
DEBUG: shmem_exit(1)
DEBUG: exit(1)
DEBUG: reaping dead processes
DEBUG: server process (PID 2981) exited with exit code 1
regards
Mark
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
