Thread: ERROR: No one parent tuple was found

Hi,

I got error when running vacuum analyze:

discovery=> vacuum analyze;ERROR:  No one parent tuple was found
discovery=> 
discovery=> vacuum analyze hits;NOTICE:  CreatePortal: portal <vacuum> already existsERROR:  No one parent tuple was
found

postgres 6.5.3, Linux x86

Everything seems work fine. How dangerous this error ?
I got it for the first time since project was started about 6 months ago -
vacuuming runs in background every hour.


Hmm, now vacuum works. I just restart psql.
Oleg
_____________________________________________________________
Oleg Bartunov, sci.researcher, hostmaster of AstroNet,
Sternberg Astronomical Institute, Moscow University (Russia)
Internet: oleg@sai.msu.su, http://www.sai.msu.su/~megera/
phone: +007(095)939-16-83, +007(095)939-23-83

Oleg Bartunov <oleg@sai.msu.su> writes:
>  ERROR:  No one parent tuple was found
> Everything seems work fine. How dangerous this error ?

Not very.  This comes out of the VACUUM code that tries to deal with
maybe-not-quite-dead tuples (stuff that's been updated and the update
has committed, but there is at least one open transaction that's old
enough that it should see the pre-update tuple state if it decides to
look at the table).  You can ensure that none of that logic runs if you
simply perform the VACUUM with no other transactions open.

I think there are probably still bugs in that area in current
sources :-( ... it's not exercised enough.
        regards, tom lane