Re: ERROR: No one parent tuple was found

From: Vivek Khera <khera(at)kcilink(dot)com>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: ERROR: No one parent tuple was found
Date: 2003-01-28 17:31:15
Message-ID: x7d6mhgp0c.fsf@onceler.kciLink.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

>>>>> "BM" == Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)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(at)kciLink(dot)com Rockville, MD +1-240-453-8497
AIM: vivekkhera Y!: vivek_khera http://www.khera.org/~vivek/

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Vivek Khera 2003-01-28 17:34:32 Re: all backends (pg7.2.3 / redhat 7.2) die due to unexpected signal 14 (SIGALRM)
Previous Message Charles Tassell 2003-01-28 17:27:59 Re: stopping access to a database