>>>>> "TL" == Tom Lane <tgl@sss.pgh.pa.us> writes:
TL> Dmitry Tkach <dmitry@openratings.com> writes:
>> ERROR: No one parent tuple was found
TL> Closing out other open transactions will probably make that go away.
TL> You should also consider updating to 7.2.3, if you're not there already.
TL> (IIRC, there is a partial fix in 7.2.3. 7.3 will fix all the causes we
TL> know about.)
Funny, I was just about to ask this question... I took down my DB
system (made it inaccessible to all external apps by the access list)
then ran vacuum full verbose analyze. This is what I got:
NOTICE: --Relation user_list--
NOTICE: Pages 644320: Changed 1273, reaped 627556, Empty 0, New 0; Tup 9668482: Vac 290, Keep/VTL 0/0, UnUsed
26051805,MinLen 100, MaxLen 528; Re-using: Free/Avail. Space 3645214756/3644567436; EndEmpty/Avail. Pages 0/630623.
CPU 56.31s/1.01u sec elapsed 178.60 sec.
NOTICE: Index user_list_pkey: Pages 51806; Tuples 9668482: Deleted 290.
CPU 5.08s/14.16u sec elapsed 118.28 sec.
ERROR: No one parent tuple was found
It looks like it did reap a bunch of pages, which is good, but the
error gives me the willies.
Curiously, last time I did this (July 4), I got the same error, so I
really doubt it is an open transaction, unless such a thing survives
db shutdown and restart ;-)
When 7.3 comes out, I'll do a dump/reload so the problem *should* go
away then... right now I'm at 7.2.1.
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Vivek Khera, Ph.D. Khera Communications, Inc.
Internet: khera@kciLink.com Rockville, MD +1-240-453-8497
AIM: vivekkhera Y!: vivek_khera http://www.khera.org/~vivek/