Re: [7.0.2] INDEX' TUPLES != HEAP' ..

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: The Hermit Hacker <scrappy(at)hub(dot)org>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: [7.0.2] INDEX' TUPLES != HEAP' ..
Date: 2000-07-12 23:29:58
Message-ID: 25681.963444598@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

The Hermit Hacker <scrappy(at)hub(dot)org> writes:
> On Wed, 12 Jul 2000, Tom Lane wrote:
>> The Hermit Hacker <scrappy(at)hub(dot)org> writes:
>>>> Odd .. why is heap reporting 5899, when count() only reports 2951?
>>
>> Open transactions preventing recently-dead tuples from being reaped?

> nope ... I've tried recreating the indices, no change ... and no change in
> number of tuples ...

That would fit right in: a newly-created index will only index the
tuples that are currently live. (OK, since an old transaction that
could still see the dead tuples couldn't see the index anyway.)

> actually, since this database is up, there would have
> been zero additions or deletions,

What about UPDATEs?

Given your other comment about a bunch of waiting backends, it sure
sounds like you've got some backend that's sitting on an old open
transaction.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message The Hermit Hacker 2000-07-12 23:46:18 Re: [7.0.2] INDEX' TUPLES != HEAP' ..
Previous Message Tim Perdue 2000-07-12 23:28:31 Some Improvement