| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| Cc: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Re: 9.3: more problems with "Could not open file "pg_multixact/members/xxxx" |
| Date: | 2014-07-17 16:27:51 |
| Message-ID: | CA+TgmoZr0XXh66RggwjiaoG+f_UDoxtfjedWsUV+gf80uv2KgA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Jul 16, 2014 at 12:46 AM, Alvaro Herrera
<alvherre(at)2ndquadrant(dot)com> wrote:
> (Maybe I'm just too tired and I'm failing to fully understand the torn
> page protection. I thought I understood how it worked, but now I'm not
> sure -- I mean I don't see how it can possibly have any value at all.
> Surely if the disk writes the first 512-byte sector of the page and then
> forgets the updates to the next 15 sectors, the page will appear as not
> needing the full page image to be restored ...)
We always restore full page images, regardless of the page LSN.
Otherwise, we'd have exactly the problem you describe.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2014-07-17 18:11:54 | Re: [v9.5] Custom Plan API |
| Previous Message | Robert Haas | 2014-07-17 16:17:44 | Re: gaussian distribution pgbench |