| From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
|---|---|
| To: | Heikki Linnakangas <hlinnakangas(at)vmware(dot)com> |
| Cc: | 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 18:25:30 |
| Message-ID: | CA+U5nMKgA4H8DX34_vvUwq98549EwKdxYdWzQG++PVQqYL6ydA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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?
It sounds like we need to look at something better for use during
archive recovery.
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Josh Berkus | 2013-02-13 18:34:19 | Re: Fractal tree indexing |
| Previous Message | Magnus Hagander | 2013-02-13 18:11:51 | Re: Alias hstore's ? to ~ so that it works with JDBC |