Skip site navigation (1) Skip section navigation (2)

Re: strange nbtree corruption report

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: strange nbtree corruption report
Date: 2011-11-29 01:40:01
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
Alvaro Herrera <alvherre(at)commandprompt(dot)com> writes:
> I wonder if it would be worthwhile to build some sort of tool to scan
> the heap and ensure that there are index entries for all heap items,
> just to test the hypothesis.  Not that this would enlighten on the
> source of the actual problem.

Seems like the hypothesis could be proven or disproven just by counting
the heap and index entries while the DB is otherwise idle.  It used to
be that VACUUM VERBOSE was sufficient for that sort of cross-check ...
but I'm not totally sure what push-ups are required nowadays to prevent
it from deciding that it's smarter than you are so it needn't scan the
whole table.  Is VACUUM FREEZE VERBOSE still trustworthy for this?

			regards, tom lane

In response to


pgsql-hackers by date

Next:From: Andres FreundDate: 2011-11-29 01:41:32
Subject: Re: Avoiding repeated snapshot computation
Previous:From: Andres FreundDate: 2011-11-29 01:38:39
Subject: Re: CommitFest 2011-11 Post-Tryptophan Progress Report

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group