Received: from maia.hub.org (maia-2.hub.org [200.46.204.251]) by mail.postgresql.org (Postfix) with ESMTP id CBA341337B39 for ; Mon, 28 Feb 2011 00:24:21 -0400 (AST) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.251]) (amavisd-maia, port 10024) with ESMTP id 33866-02 for ; Mon, 28 Feb 2011 04:24:14 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from exprod7og124.obsmtp.com (exprod7og124.obsmtp.com [64.18.2.26]) by mail.postgresql.org (Postfix) with ESMTP id BD1241337B2F for ; Mon, 28 Feb 2011 00:24:13 -0400 (AST) Received: from source ([209.85.213.51]) (using TLSv1) by exprod7ob124.postini.com ([64.18.6.12]) with SMTP ID DSNKTWsjbDclWXSdt31c3OVZSDUIRJHuPHqy@postini.com; Sun, 27 Feb 2011 20:24:13 PST Received: by ywg4 with SMTP id 4so1426314ywg.24 for ; Sun, 27 Feb 2011 20:24:12 -0800 (PST) Received: by 10.100.24.22 with SMTP id 22mr445962anx.263.1298867052200; Sun, 27 Feb 2011 20:24:12 -0800 (PST) Received: from [192.168.1.2] ([122.169.64.43]) by mx.google.com with ESMTPS id d15sm4393806ana.15.2011.02.27.20.24.09 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 27 Feb 2011 20:24:11 -0800 (PST) Subject: Re: ERROR: missing chunk number 0 for toast value 382548694 in pg_toast_847386 Mime-Version: 1.0 (Apple Message framework v1082) Content-Type: text/plain; charset=us-ascii From: Vibhor Kumar In-Reply-To: Date: Mon, 28 Feb 2011 09:54:47 +0530 Cc: "pgsql-general@postgresql.org" Content-Transfer-Encoding: quoted-printable Message-Id: References: <132BC6A6-0C40-46BD-8CF3-43F23BD9A749@enterprisedb.com> To: Michael Harris X-Mailer: Apple Mail (2.1082) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-4.2 tagged_above=-5 required=5 tests=BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3 X-Spam-Level: X-Archive-Number: 201102/936 X-Sequence-Number: 173202 On Feb 28, 2011, at 9:46 AM, Michael Harris wrote: > The main reason we have not gone down that path that after getting = this error we do not have any confidence in the integrity of the rest of = the database after performing the restore - maybe there are many more = tables with corruption in them. May be or may not be. Did you find anything suspicious in pg_log? Please share recovery.conf information. > We are mainly concerned that our backups are valid. The fault does not = seem to be present on the original database, only after restoring from = the base backup + PITR. Did you verify base backup (Restoring without PITR) ? Thanks & Regards, Vibhor Kumar vibhor.kumar@enterprisedb.com Blog:http://vibhork.blogspot.com