| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Simon Riggs <simon(at)2ndQuadrant(dot)com>, "devrim(at)gunduz(dot)org" <devrim(at)gunduz(dot)org>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Re: [COMMITTERS] pgsql: Properly set relpersistence for fake relcache entries. |
| Date: | 2012-09-17 05:35:06 |
| Message-ID: | 7579.1347860106@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> On Sep 15, 2012, at 11:32 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> Right, but we do a shutdown checkpoint at the end of crash recovery.
> Yes, but that only writes the buffers that are dirty. It doesn't fix the lack of a BM_PERMANENT flag on a buffer that ought to have had one. So that page can now get modified AGAIN, after recovery, and not checkpointed.
Ugh. Yeah, we need to fix this ASAP. I've notified pgsql-packagers to
expect a release this week.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2012-09-17 06:44:42 | Re: Re: [COMMITTERS] pgsql: Properly set relpersistence for fake relcache entries. |
| Previous Message | Peter Eisentraut | 2012-09-17 02:28:13 | pgsql: PL/Python: Improve Python 3 regression test setup |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2012-09-17 06:44:42 | Re: Re: [COMMITTERS] pgsql: Properly set relpersistence for fake relcache entries. |
| Previous Message | Rural Hunter | 2012-09-17 05:07:20 | Re: [ADMIN] pg_upgrade from 9.1.3 to 9.2 failed |