Re: New trigger option of pg_standby
От | Fujii Masao |
---|---|
Тема | Re: New trigger option of pg_standby |
Дата | |
Msg-id | 3f0b79eb0904210448l36d9bb27u8b832540010a6f20@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: New trigger option of pg_standby (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>) |
Ответы |
Re: New trigger option of pg_standby
Re: New trigger option of pg_standby |
Список | pgsql-hackers |
Hi, On Tue, Apr 21, 2009 at 8:28 PM, Heikki Linnakangas <heikki.linnakangas@enterprisedb.com> wrote: > Simon Riggs wrote: >> >> If you do this, then you would have to change the procedure written into >> the 8.3 docs also. Docs aren't backpatchable. >> >> What you propose is *better* than raw pg_standby is now, but still not >> enough in all cases, as I think you know. > > No, I don't. What is the case where it doesn't work? It's the case which I described as the 2nd comment to your proposal. 1. pg_standby tries to restore a non-existent file 1-1. remove the trigger file 1-2. pg_standby exits with non-zero code 2. the startup process tries to read it from pg_xlog 2-1. it is applied 3. the startup process tries to restore the next file using pg_standby 3-1. pg_standby gets *stuck* since the requested file and trigger file don't exist. Regards, -- Fujii Masao NIPPON TELEGRAPH AND TELEPHONE CORPORATION NTT Open Source Software Center
В списке pgsql-hackers по дате отправления: