Re: Fwd: index corruption in PG 8.3.13

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Greg Stark <gsstark(at)mit(dot)edu>
Cc: Nikhil Sontakke <nikhil(dot)sontakke(at)enterprisedb(dot)com>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Fwd: index corruption in PG 8.3.13
Date: 2011-03-10 18:29:45
Message-ID: AANLkTimmSyxhkBckE8H+YnqtHLgvqeQF4r5UhShS8ggw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Mar 10, 2011 at 12:52 PM, Greg Stark <gsstark(at)mit(dot)edu> wrote:
> On Thu, Mar 10, 2011 at 1:45 PM, Robert Haas <robertmhaas(at)gmail(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jesper Krogh 2011-03-10 18:30:12 Re: Read uncommitted ever possible?
Previous Message Bruce Momjian 2011-03-10 18:25:19 Re: Read uncommitted ever possible?