Re: Did we really want to force an initdb in beta2? - Mailing list pgsql-hackers

From Florian Pflug
Subject Re: Did we really want to force an initdb in beta2?
Date
Msg-id B843940D-89FD-4439-9A97-58D89273537D@phlo.org
Whole thread Raw
In response to Re: Did we really want to force an initdb in beta2?  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Did we really want to force an initdb in beta2?  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Jun 3, 2010, at 19:00 , Tom Lane wrote:
> Heikki Linnakangas <heikki.linnakangas@enterprisedb.com> writes:
>> On 03/06/10 19:16, Tom Lane wrote:
>>> What exactly was the reason for this patch?  Could it be held over till
>>> 9.1?
>
>> Before the patch, when you shut down a standby server, you get this
>> message in the log on the next startup:
>
>> LOG:  database system was interrupted while in recovery at log time
>> 2010-06-02 14:48:28 EEST
>> HINT:  If this has occurred more than once some data might be corrupted
>> and you might need to choose an earlier recovery target.
>
>> The problem is that that hint is pretty alarming.
>
> Maybe we should just get rid of the hint.


FYI, Robert Haas suggested the same in the thread that lead to this patch being applied. The arguments against doing
thatis that a real crash during recovery *is* something to be quite alarmed about. 

best regards,
Florian Pflug



pgsql-hackers by date:

Previous
From: Simon Riggs
Date:
Subject: Re: Keepalive for max_standby_delay
Next
From: Alvaro Herrera
Date:
Subject: Re: Allow wal_keep_segments to keep all segments