| From: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Hitesh Bhambhani <hitesh(dot)bhambhani(at)asg(dot)com>, pgsql-bugs <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: BUG #5599: Vacuum fails due to index corruption issues |
| Date: | 2010-08-05 20:08:36 |
| Message-ID: | 4C5B1A44.1080504@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
On 05/08/10 21:28, Alvaro Herrera wrote:
> Excerpts from Tom Lane's message of jue ago 05 14:01:15 -0400 2010:
>> Maybe write-the-buffers-first is a sufficient longterm solution.
>
> Yeah, perhaps it is, though it's a pity that a single platform problem
> is going to slow down everyone else.
How about performing the truncate as usual, but if it fails, fill the
truncated portion with zeros instead? Zeroed pages should be handled
gracefully, and this would be a very non-invasive fix. Now if the
write() to zero the pages fails too, I guess we'll have to panic, but
that's not much different from flushing the dirty pages first.
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2010-08-05 20:29:26 | Re: BUG #5599: Vacuum fails due to index corruption issues |
| Previous Message | Tom Lane | 2010-08-05 19:59:31 | Re: Re: BUG #5602: Recovering from Hot-Standby file backup leads to the currupted indexes |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2010-08-05 20:29:26 | Re: BUG #5599: Vacuum fails due to index corruption issues |
| Previous Message | Kevin Grittner | 2010-08-05 20:07:01 | Re: Concurrent MERGE |