Received: from magus.postgresql.org (magus.postgresql.org [87.238.57.229]) by mail.postgresql.org (Postfix) with ESMTP id 3E0BAA01094 for ; Wed, 30 Nov 2011 10:40:59 -0400 (AST) Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1RVlLF-0001Pj-7t for pgsql-admin@postgresql.org; Wed, 30 Nov 2011 14:40:58 +0000 Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.2/8.14.2) with ESMTP id pAUEehpY009416; Wed, 30 Nov 2011 09:40:43 -0500 (EST) To: Lukasz Brodziak cc: Scott Marlowe , pgsql-admin@postgresql.org Subject: Re: Database is in recovery mode. In-reply-to: References: Comments: In-reply-to Lukasz Brodziak message dated "Wed, 30 Nov 2011 08:40:47 +0100" Date: Wed, 30 Nov 2011 09:40:43 -0500 Message-ID: <9415.1322664043@sss.pgh.pa.us> From: Tom Lane X-Pg-Spam-Score: -3.1 (---) X-Archive-Number: 201111/159 X-Sequence-Number: 38753 Lukasz Brodziak writes: > I have isolated the corrupted row of data and isolated column which > constains bad data. Unfortunately I can't do anything with the row. I have > an older backup of the db which contains correct row. Is there a way I can > restore only the given row or replace it in the file ( I also located the > row on the page). You haven't shown us exactly how it's failing, but depending on what sort of corruption this is, you might be able to delete the damaged row with DELETE FROM table WHERE ctid = '...'; regards, tom lane