In current pg_standby, the presence of the trigger file causes
recovery to end whether or not the next WAL file is available.
Thereby, some transactions in the available WAL files will be
lost. So, we cannot use this trigger file to promote the standby
to the primary.
I'd like to add new trigger file option into pg_standby, and end
recovery after redoing all the available WAL files. Concretely
speaking, I would always make pg_standby look for the trigger
file after trying to restore the WAL file once. If the trigger file
is present, pg_standby exits immediately without deleting the
trigger file. Subsequent pg_standby uses the existing trigger
This option is also useful for warm-standby.
Any comments welcome!
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center
pgsql-hackers by date
|Next:||From: Peter Eisentraut||Date: 2008-11-25 15:17:05|
|Subject: Re: Brittleness in regression test setup|
|Previous:||From: Tom Lane||Date: 2008-11-25 14:42:57|
|Subject: Re: Exporting PGINTERVALSTYLE prevents access to older server versions |