| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
| Cc: | 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 16:36:24 |
| Message-ID: | 16374.1281026184@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
Alvaro Herrera <alvherre(at)commandprompt(dot)com> writes:
> Excerpts from Tom Lane's message of jue ago 05 11:06:57 -0400 2010:
>> 1. Write the dirty buffers before dropping them. Kind of ugly from a
>> performance viewpoint, but simple and safe.
> I think "simple" is good, considering that this code is gone in 9.0 and
> HEAD. IMHO investing too much effort on this problem is not worth it.
Gone? Looks like it's still there to me.
> Perhaps it'd be good to come up with a better solution for HEAD:
Yeah, the panic-on-replay aspect is troublesome. I feel like we need a
rethink here. But I agree that solution #1 is the only one that feels
safe enough for backpatching.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2010-08-05 16:49:52 | Re: BUG #5602: Recovering from Hot-Standby file backup leads to the currupted indexes |
| Previous Message | Alvaro Herrera | 2010-08-05 16:28:20 | Re: BUG #5599: Vacuum fails due to index corruption issues |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2010-08-05 16:39:19 | Re: Concurrent MERGE |
| Previous Message | Tom Lane | 2010-08-05 16:33:47 | Re: Needs Suggestion |