Re: ERROR: No one parent tuple was found - Mailing list pgsql-general

From Vivek Khera
Subject Re: ERROR: No one parent tuple was found
Date
Msg-id x7d6mhgp0c.fsf@onceler.kciLink.com
Whole thread Raw
In response to Re: ERROR: No one parent tuple was found  (Bruce Momjian <pgman@candle.pha.pa.us>)
List pgsql-general
>>>>> "BM" == Bruce Momjian <pgman@candle.pha.pa.us> writes:

BM> Uh, I know we fixed this in 7.3, but I don't remember the cause in 7.2.X.

BM> ---------------------------------------------------------------------------

BM> Renê Salomão wrote:
>> Hi list,
>>
>> After run "VACCUM FULL VERBOSE ANALYZE" the following message appears:
>> "ERROR:  No one parent tuple was found"...
>> What can be causing this problem?

When I asked this question a few months ago, I got an answer from Tom
Lane.  Basically, some transaction wasn't properly closed.  My
solution was dump/restore.  I think he proposed some other possible
fix, but I didn't bother with it.

As soon as RT gets up to snuff with 7.3, I'm moving up again... but
that dump/restore sure takes a looong time with 100+ million
records. ;-(


--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
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/

pgsql-general by date:

Previous
From: Vivek Khera
Date:
Subject: Re: DBD::Pg & DBD::PgPP Cpan question
Next
From: Vivek Khera
Date:
Subject: Re: all backends (pg7.2.3 / redhat 7.2) die due to unexpected signal 14 (SIGALRM)