Re: vacuumdb is failing with NUMBER OF INDEX TUPLES NOT THE SAME AS HEAP

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Lonni Friedman <netllama(at)gmail(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: vacuumdb is failing with NUMBER OF INDEX TUPLES NOT THE SAME AS HEAP
Date: 2004-05-05 15:30:33
Message-ID: 2984.1083771033@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Lonni Friedman <netllama(at)gmail(dot)com> writes:
> All of a sudden last month (after about 3 years) I started getting
> this warning when vacuumdb was run:

> INFO: Index pg_largeobject_loid_pn_index: Pages 903; Tuples 323847:
> Deleted 0. CPU 0.04s/0.07u sec elapsed 0.10 sec.
> WARNING: Index pg_largeobject_loid_pn_index: NUMBER OF INDEX' TUPLES
> (323847) IS NOT THE SAME AS HEAP' (323802).
> Recreate the index.

Hmm. Is it always that same index, or have you seen this on other indexes?

I'm not aware of any known bug in 7.3.* that could lead to this sort of
error. Don't suppose you have any suggestions about how to reproduce
the problem?

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Vivek Khera 2004-05-05 15:37:25 Re: Is there a newer version of DBD::Pg?
Previous Message Sally Sally 2004-05-05 15:17:02 postgres mirroring (real-time)