Re: [7.0.2] INDEX' TUPLES != HEAP' ..
От | The Hermit Hacker |
---|---|
Тема | Re: [7.0.2] INDEX' TUPLES != HEAP' .. |
Дата | |
Msg-id | Pine.BSF.4.21.0007122045340.1325-100000@thelab.hub.org обсуждение исходный текст |
Ответ на | Re: [7.0.2] INDEX' TUPLES != HEAP' .. (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: [7.0.2] INDEX' TUPLES != HEAP' ..
|
Список | pgsql-hackers |
On Wed, 12 Jul 2000, Tom Lane wrote: > The Hermit Hacker <scrappy@hub.org> writes: > > On Wed, 12 Jul 2000, Tom Lane wrote: > >> The Hermit Hacker <scrappy@hub.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? zip ... only SELECTs right now ... no facility there to do updates, deletes or inserts ... > 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. last email about waiting was a different database ... will *that* affect this? :(
В списке pgsql-hackers по дате отправления: