X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id 6E9839FA4DE for ; Fri, 5 May 2006 14:49:45 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 84833-01 for ; Fri, 5 May 2006 14:49:40 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from svr4.postgresql.org (svr4.postgresql.org [66.98.251.159]) by postgresql.org (Postfix) with ESMTP id F24589FA3A3 for ; Fri, 5 May 2006 14:49:40 -0300 (ADT) Received: from main.rtv5.cz (r-rtv5-breclav.czechbone.net [212.96.178.50]) by svr4.postgresql.org (Postfix) with ESMTP id A92355B6DC8 for ; Fri, 5 May 2006 17:49:38 +0000 (GMT) Received: from v82.bvx.cz (v82.bvx.cz [212.96.165.82]) by main.rtv5.cz (8.12.5/8.12.5/Debian-1) with ESMTP id k45HskEY020706; Fri, 5 May 2006 19:54:46 +0200 From: MIlos Prudek To: Tom Lane Subject: Re: missing chunk number 0 for toast value ... Date: Fri, 5 May 2006 19:49:33 +0200 User-Agent: KMail/1.8.2 References: <200605032202.57825.prudek@bvx.cz> <25742.1146688817@sss.pgh.pa.us> In-Reply-To: <25742.1146688817@sss.pgh.pa.us> Cc: pgsql-admin@postgresql.org MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-2" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200605051949.33397.prudek@bvx.cz> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200605/58 X-Sequence-Number: 21590 > Find the row containing the busted toast reference, and delete that row > (or just UPDATE it with some new value for the toasted column). You can > home in on it with the usual sorts of search methods --- look in the PG > list archives for previous discussions of locating corrupted rows. Thanks Tom. I ended up restoring the table from the last dump (created by pg_dump) up to the point where corruption starts. Not the most surgical solution but justified for my use case. -- Milos Prudek