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 17:56:41
Message-ID: 8238.1083779801@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:
> On Wed, 05 May 2004 12:31:21 -0400, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> Once the complaint starts appearing, I'd expect it to continue until you
>> reindex the index.

> That's exactly what happens. It consistantly errors until reindexed.
> Any suggestions? thanks.

You are seemingly triggering some sort of bug in the backend's
large-object code, causing extra index entries to be made ...
but I sure haven't the foggiest idea how that would happen.

Perhaps you could look at the parts of your application code that work
with large objects and see if you are doing anything "off the beaten
track" that might suggest a way to trigger the bug reproducibly.
I'm sure we could fix it if we could see it happening.

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message scott.marlowe 2004-05-05 17:58:09 Re: Load Balancing and Backup
Previous Message Lonni Friedman 2004-05-05 17:35:43 Re: vacuumdb is failing with NUMBER OF INDEX TUPLES NOT THE SAME AS HEAP