Hi, On Tue, Apr 14, 2009 at 2:41 PM, Fujii Masao <masao.fu...@gmail.com> wrote: > I'd like to propose another simple idea; pg_standby deletes the > trigger file *whenever* the nextWALfile is a timeline history file. > A timeline history file is restored at the end of recovery, so it's > guaranteed that the trigger file is deleted whether nextWALfile > exists or not. > > A timeline history file is restored also at the beginning of > recovery, so the accidentally remaining trigger file is deleted > in early warm-standby as a side-effect of this idea.
Here is the revised patch as above. If you notice something, please feel free to comment. Regards, -- Fujii Masao NIPPON TELEGRAPH AND TELEPHONE CORPORATION NTT Open Source Software Center
pgstandby_change_trigger_0415.patch
Description: Binary data
-- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
