Re: BUG #5599: Vacuum fails due to index corruption issues - Mailing list pgsql-bugs

From Alvaro Herrera
Subject Re: BUG #5599: Vacuum fails due to index corruption issues
Date
Msg-id 1281032780-sup-1394@alvh.no-ip.org
Whole thread Raw
In response to Re: BUG #5599: Vacuum fails due to index corruption issues  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: BUG #5599: Vacuum fails due to index corruption issues
Re: BUG #5599: Vacuum fails due to index corruption issues
List pgsql-bugs
Excerpts from Tom Lane's message of jue ago 05 14:01:15 -0400 2010:

> You're right, I misremembered.  That code is just plain gone in 9.0:
> http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/nbtree/nbtree.c.diff?r1=1.174;r2=1.175;f=h
>
> Still, we have a live issue with heap truncation during plain VACUUM.
> However, the scope of the problem seems a lot less than I was thinking.

The scope is further reduced by the fact that this only seems to happen
on Windows, and then only when the antivirus is messing around with the
files.

> 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.

--
Álvaro Herrera <alvherre@commandprompt.com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: [HACKERS] Drop one-argument string_agg? (was Re: string_agg delimiter having no effect with order by)
Next
From: Peter Eisentraut
Date:
Subject: Re: [HACKERS] Drop one-argument string_agg? (was Re: string_agg delimiter having no effect with order by)