Re: Fwd: index corruption in PG 8.3.13 - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Fwd: index corruption in PG 8.3.13
Date
Msg-id AANLkTimmSyxhkBckE8H+YnqtHLgvqeQF4r5UhShS8ggw@mail.gmail.com
Whole thread Raw
In response to Re: Fwd: index corruption in PG 8.3.13  (Greg Stark <gsstark@mit.edu>)
Responses Re: Fwd: index corruption in PG 8.3.13
List pgsql-hackers
On Thu, Mar 10, 2011 at 12:52 PM, Greg Stark <gsstark@mit.edu> wrote:
> On Thu, Mar 10, 2011 at 1:45 PM, Robert Haas <robertmhaas@gmail.com> wrote:
>> 1. Somebody inserts a bunch of new tuples into the relation, causing
>> growth in the index.
>
> In case it's not obvious VACUUM FULL would do precisely that.

Oh, I didn't even think about that.  Yeah, that could be it, too.  So
maybe VACUUM FULL - crash before checkpoint - problem with recovery?

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company


pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: Read uncommitted ever possible?
Next
From: Jesper Krogh
Date:
Subject: Re: Read uncommitted ever possible?