Re: Fwd: index corruption in PG 8.3.13

From: Greg Stark <gsstark(at)mit(dot)edu>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
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 17:52:34
Message-ID: AANLkTinFKsP_yv0vswBjW4c1Mx9fhwNUE13_HYLzPujv@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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.

> 2. Before the blocks are written to disk, system crash.
> 3. pg_resetxlog

Do you have any record of the VACUUM FULL committing? Do you know what
LSN its commit record is at?

--
greg

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jesper Krogh 2011-03-10 18:19:45 Re: Read uncommitted ever possible?
Previous Message Merlin Moncure 2011-03-10 17:22:23 Re: Read uncommitted ever possible?