X-Original-To: pgsql-admin@postgresql.org
Received: from localhost (postgresql.org [64.49.215.8])
	by postgresql.org (Postfix) with ESMTP
	id 1519C476290; Wed,  5 Feb 2003 10:48:04 -0500 (EST)
Received: from sss.pgh.pa.us (unknown [192.204.191.242])
	by postgresql.org (Postfix) with ESMTP
	id 9B7224764A7; Wed,  5 Feb 2003 10:23:32 -0500 (EST)
Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1])
	by sss.pgh.pa.us (8.12.6/8.12.6) with ESMTP id h15FNI5u026069;
	Wed, 5 Feb 2003 10:23:19 -0500 (EST)
To: marcelo.tada@nube.com.br
Cc: PostgreSQL <pgsql-sql@postgresql.org>, pgsql-admin@postgresql.org
Subject: Re: Problem with VACUUM 
In-reply-to: <3E4101C4.3070607@nube.com.br> 
References: <3E4101C4.3070607@nube.com.br>
Comments: In-reply-to Marcelo Pereira Tada <marcelo.tada@nube.com.br>
	message dated "Wed, 05 Feb 2003 12:21:24 +0000"
Date: Wed, 05 Feb 2003 10:23:18 -0500
Message-ID: <26068.1044458598@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
X-Virus-Scanned: by AMaViS new-20020517
X-Archive-Number: 200302/60
X-Sequence-Number: 7258

Marcelo Pereira Tada <marcelo.tada@nube.com.br> writes:
>> NOTICE:  Child itemid in update-chain marked as unused - can't continue repair_frag
>> ERROR:  No one parent tuple was found

Try updating to 7.2.4; that should fix this.

			regards, tom lane