| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
| Cc: | Heikki Linnakangas <hlinnakangas(at)vmware(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:03:22 |
| Message-ID: | 10652.1360782202@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Simon Riggs <simon(at)2ndQuadrant(dot)com> writes:
> On 13 February 2013 09:04, Heikki Linnakangas <hlinnakangas(at)vmware(dot)com> wrote:
>> To be precise, we'd need to update the control file on every XLogFlush(),
>> like we do during archive recovery. That would indeed be unacceptable from a
>> performance point of view. Updating the control file that often would also
>> be bad for robustness.
> If those arguments make sense, then why don't they apply to recovery as well?
In plain old crash recovery, don't the checks on whether to apply WAL
records based on LSN take care of this?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2013-02-13 19:12:48 | Re: 9.2.3 crashes during archive recovery |
| Previous Message | Josh Berkus | 2013-02-13 18:34:19 | Re: Fractal tree indexing |