On Tue, Mar 8, 2011 at 12:04 PM, Fujii Masao <masao(dot)fujii(at)gmail(dot)com> wrote:
> On Wed, Feb 9, 2011 at 5:12 PM, Magnus Hagander <magnus(at)hagander(dot)net> wrote:
>> I was also worried about the non-hot-standby case, but I see that the
>> patch makes sure you can't enable pause when not in hot standby mode.
>> Which in itself might be surprising - perhaps we need a NOTICE for
>> when that happens as well?
> I didn't include this fix in the patch because I prefer FATAL to
> NOTICE for that.
> NOTICE doesn't stop recovery. So we might be unable to notice such a NOTICE
> message and stop the recovery before it's too late, i.e., the recovery has
> completed at the undesirable point. So I think that emitting FATAL is safer.
I included this fix in the patch, which emits FATAL if pause_at_recovery_target
is enabled while hot standby is disabled and the recovery target is set.
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center
In response to
pgsql-hackers by date
|Next:||From: Fujii Masao||Date: 2011-03-08 12:05:08|
|Subject: Re: Sync Rep v19|
|Previous:||From: Jan Urbański||Date: 2011-03-08 10:11:03|
|Subject: Re: pl/python tracebacks|
pgsql-committers by date
|Next:||From: User Fxjr||Date: 2011-03-08 15:50:38|
|Subject: npgsql - Npgsql2: Fixed problems with SSPI authentication when the |
|Previous:||From: Michael Meskes||Date: 2011-03-08 10:28:33|
|Subject: pgsql: Added new version of ecpg's parser test script which waswritten|