From: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
---|---|
To: | guillaume(dot)smet(at)gmail(dot)com |
Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: New trigger option of pg_standby |
Date: | 2009-03-25 08:44:52 |
Message-ID: | 3f0b79eb0903250144k453b3927mffa8b08678ed057b@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi,
Thanks for the comment.
On Wed, Mar 25, 2009 at 3:50 PM, Guillaume Smet
<guillaume(dot)smet(at)gmail(dot)com> wrote:
> On Wed, Mar 25, 2009 at 7:29 AM, Fujii Masao <masao(dot)fujii(at)gmail(dot)com> wrote:
>> Attached patch fixes the above problem by adding a new trigger option
>> to pg_standby; the presence of this new trigger file causes recovery to
>> end after replaying all the available WAL files.
>
> Shouldn't it be the default? It seems like the most expected behaviour to me.
Yeah, I agree... but there may be scripts for warm-standby based on
the existing default behavior. So, I didn't make a new trigger the default.
Regards,
--
Fujii Masao
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center
From | Date | Subject | |
---|---|---|---|
Next Message | Guillaume Smet | 2009-03-25 08:55:49 | Re: New trigger option of pg_standby |
Previous Message | Scara Maccai | 2009-03-25 07:58:46 | Matching dimensions in arrays |