pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
vacuum full fails: Parent tuple was not found[7.2]
2+ messages / 2 participants
[nested] [flat]

* vacuum full fails: Parent tuple was not found[7.2]
@ 2002-04-02 16:46  george young <gry@ll.mit.edu>
  0 siblings, 1 reply; 2+ messages in thread

From: george young @ 2002-04-02 16:46 UTC (permalink / raw)
  To: pgsql-sql

[Postgres 7.2, SuSE Linux 7.3 (2.4.10), Pentium-III, gcc-3.0.4]
vacuum full fails on pg_class:

  VACUUM FULL VERBOSE ANALYZE pg_class;
  NOTICE:  --Relation pg_class--
  NOTICE:  Pages 147: Changed 0, reaped 134, Empty 0, New 0; Tup 2559: Vac 0, Keep/VTL 666/222,   UnUsed 7051, MinLen 116, MaxLen 176; Re-using: Free/Avail. Space 833148/831052; EndEmpty/Avail.   Pages 0/116.
   CPU 0.00s/0.00u sec elapsed 0.00 sec.
  NOTICE:  Index pg_class_oid_index: Pages 45; Tuples 2559: Deleted 0.
   CPU 0.02s/0.00u sec elapsed 0.05 sec.
  NOTICE:  Index pg_class_relname_index: Pages 149; Tuples 2559: Deleted 0.
   CPU 0.04s/0.00u sec elapsed 0.11 sec.
  ERROR:  Parent tuple was not found

What does this mean, and how can I fix it?

Vacuum without the "full" directive works OK.

-- 
 I cannot think why the whole bed of the ocean is
 not one solid mass of oysters, so prolific they seem. Ah,
 I am wandering! Strange how the brain controls the brain!
	-- Sherlock Holmes in "The Dying Detective"



^ permalink  raw  reply  [nested|flat] 2+ messages in thread

* Re: vacuum full fails: Parent tuple was not found[7.2]
@ 2002-04-02 17:40  Tom Lane <tgl@sss.pgh.pa.us>
  parent: george young <gry@ll.mit.edu>
  0 siblings, 0 replies; 2+ messages in thread

From: Tom Lane @ 2002-04-02 17:40 UTC (permalink / raw)
  To: gry@ll.mit.edu; +Cc: pgsql-sql

george young <gry@ll.mit.edu> writes:
> [Postgres 7.2, SuSE Linux 7.3 (2.4.10), Pentium-III, gcc-3.0.4]
> vacuum full fails on pg_class:

>   VACUUM FULL VERBOSE ANALYZE pg_class;
>   NOTICE:  --Relation pg_class--
>   NOTICE:  Pages 147: Changed 0, reaped 134, Empty 0, New 0; Tup 2559: Vac 0, Keep/VTL 666/222,   UnUsed 7051, MinLen 116, MaxLen 176; Re-using: Free/Avail. Space 833148/831052; EndEmpty/Avail.   Pages 0/116.
>    CPU 0.00s/0.00u sec elapsed 0.00 sec.
>   NOTICE:  Index pg_class_oid_index: Pages 45; Tuples 2559: Deleted 0.
>    CPU 0.02s/0.00u sec elapsed 0.05 sec.
>   NOTICE:  Index pg_class_relname_index: Pages 149; Tuples 2559: Deleted 0.
>    CPU 0.04s/0.00u sec elapsed 0.11 sec.
>   ERROR:  Parent tuple was not found

> What does this mean, and how can I fix it?

This looks like a bug in VACUUM FULL's handling of chains of updated
tuples (ie, a series of updates of the same row that might all still
be visible to some open transaction(s)).  I am guessing that somewhere
in the background you have a backend sitting idle with an open BEGIN
block.  Closing that transaction will probably make the error disappear.

I have long suspected that the VACUUM chain logic still contains some
corner-case mistakes, but it's very difficult to come by test cases.
I am itching to look at your case with a debugger ... but unless your
installed postmaster was already compiled with debug symbols, there's
probably no hope of learning anything here.  Reinstalling a
debug-enabled executable would entail closing that open transaction,
which will make the symptom disappear.

If by chance you do have debug symbols in your installation, then
please DON'T close that open transaction.  Let's talk ...

			regards, tom lane



^ permalink  raw  reply  [nested|flat] 2+ messages in thread


end of thread, other threads:[~2002-04-02 17:40 UTC | newest]

Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2002-04-02 16:46 vacuum full fails: Parent tuple was not found[7.2] george young <gry@ll.mit.edu>
2002-04-02 17:40 ` Tom Lane <tgl@sss.pgh.pa.us>

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox