From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Heikki Linnakangas <hlinnakangas(at)vmware(dot)com> |
Cc: | Simon Riggs <simon(at)2ndQuadrant(dot)com>, Kyotaro HORIGUCHI <horiguchi(dot)kyotaro(at)lab(dot)ntt(dot)co(dot)jp>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: 9.2.3 crashes during archive recovery |
Date: | 2013-02-13 19:30:10 |
Message-ID: | 11350.1360783810@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Heikki Linnakangas <hlinnakangas(at)vmware(dot)com> writes:
> On 13.02.2013 21:21, Tom Lane wrote:
>> It would only be broken if someone interrupted a crash recovery
>> mid-flight and tried to establish a recovery stop point before the end
>> of WAL, no? Why don't we just forbid that case? This would either be
>> the same as, or a small extension of, the pg_control state vs existence
>> of recovery.conf error check that was just discussed.
> The problem is when you interrupt archive recovery (kill -9), and
> restart. After restart, the system needs to know how far the WAL was
> replayed before the crash, because it must not open for hot standby
> queries, or allow the database to be started up in master-mode, until
> it's replayed the WAL up to that same point again.
Well, archive recovery is a different scenario --- Simon was questioning
whether we need a minRecoveryPoint mechanism in crash recovery, or at
least that's what I thought he asked.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Heikki Linnakangas | 2013-02-13 19:33:44 | Re: 9.2.3 crashes during archive recovery |
Previous Message | Heikki Linnakangas | 2013-02-13 19:27:06 | Re: 9.2.3 crashes during archive recovery |