Hi, On Tue, Oct 6, 2009 at 10:42 PM, Alvaro Herrera <alvhe...@commandprompt.com> wrote: > Hmm. Without looking at the patch at all, this seems similar to how > autovacuum does things: autovac launcher signals postmaster that a > worker needs to be started. Postmaster proceeds to fork a worker. This > could obviously fail for a lot of reasons.
Yeah, I drew upon the autovac code. > Now, there is code in place to notify the user when forking fails, and > this is seen on the wild quite a bit more than one would like :-( I > think it would be a good idea to have a retry mechanism in the > walreceiver startup mechanism so that recovery does not get stuck due to > transient problems. Agreed. The latest patch provides the retry mechanism. Regards, -- Fujii Masao NIPPON TELEGRAPH AND TELEPHONE CORPORATION NTT Open Source Software Center -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
