From: | Florian Pflug <fgp(at)phlo(dot)org> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Did we really want to force an initdb in beta2? |
Date: | 2010-06-03 18:06:54 |
Message-ID: | B843940D-89FD-4439-9A97-58D89273537D@phlo.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Jun 3, 2010, at 19:00 , Tom Lane wrote:
> Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)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 that is that a real crash during recovery *is* something to be quite alarmed about.
best regards,
Florian Pflug
From | Date | Subject | |
---|---|---|---|
Next Message | Dan Colish | 2010-06-03 19:02:01 | SET CONSTRAINTS todo |
Previous Message | Simon Riggs | 2010-06-03 17:46:31 | Re: Keepalive for max_standby_delay |