| From: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
|---|---|
| To: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Hot standby, recovery infra |
| Date: | 2009-02-05 08:31:03 |
| Message-ID: | 498AA3C7.706@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Simon Riggs wrote:
> On Thu, 2009-02-05 at 09:28 +0200, Heikki Linnakangas wrote:
>
>>>> I've changed the way minRecoveryPoint is updated now anyway, so it no
>>>> longer happens every XLogFileRead().
>>> Care to elucidate?
>> I got rid of minSafeStartPoint, advancing minRecoveryPoint instead. And
>> it's advanced in XLogFlush instead of XLogFileRead. I'll post an updated
>> patch soon.
>
> Why do you think XLogFlush is called less frequently than XLogFileRead?
It's not, but we only need to update the control file when we're
"flushing" an LSN that's greater than current minRecoveryPoint. And when
we do update minRecoveryPoint, we can update it to the LSN of the last
record we've read from the archive.
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2009-02-05 08:59:00 | Re: Hot standby, recovery infra |
| Previous Message | Stephen R. van den Berg | 2009-02-05 08:11:40 | Re: Auto-updated fields |