Skip site navigation (1) Skip section navigation (2)

Re: ERROR: No one parent tuple was found

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Oleg Bartunov <oleg(at)sai(dot)msu(dot)su>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: ERROR: No one parent tuple was found
Date: 2000-04-05 00:05:41
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
Oleg Bartunov <oleg(at)sai(dot)msu(dot)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

In response to

pgsql-hackers by date

Next:From: Tatsuo IshiiDate: 2000-04-05 00:16:32
Subject: Re: Re: BSD/OS regression on 7.0
Previous:From: Hiroshi InoueDate: 2000-04-04 23:59:35
Subject: RE: CURSOR after hitting end

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group