Re: 8.1 index corruption woes

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
Cc: Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: 8.1 index corruption woes
Date: 2008-07-08 00:39:47
Message-ID: 26401.1215477587@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Alvaro Herrera <alvherre(at)commandprompt(dot)com> writes:
> We've detected what I think is some sort of index corruption in 8.1.
> The server is running 8.1.11, so AFAICT the problem with truncated pages
> in vacuum is already patched and accounted for (i.e. we reindexed, and a
> bit later the problem presented itself again). There haven't been any
> relevant fixes after that AFAICT.

> What we see is that after a bit of updating the index, it starts having
> tuples that poing to heap entries which are marked unused.

Do you actually see any observed problem, or is this conclusion based
entirely on your pg_filedump analysis?

I suspect a problem with your analysis script, although a quick scan
of the code didn't find an issue.

Another point to keep in mind, if you are trying to analyze files
belonging to a live database, is that what you can see in the filesystem
may not be the "current" contents of every page. For typical access
patterns it'd be unsurprising for the visible index pages to lag behind
those of the heap, since they'd be "hotter" and tend to stay in shared
buffers longer.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message David E. Wheeler 2008-07-08 01:03:56 PATCH: CITEXT 2.0 v3
Previous Message imad 2008-07-08 00:38:05 Re: Data type OID numbers fixed?