Received: from localhost (unknown [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id 28CC4633056 for ; Mon, 23 Feb 2009 14:18:28 -0400 (AST) Received: from mail.postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 90910-08 for ; Mon, 23 Feb 2009 14:18:25 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from mail2.saga.it (host85-166-static.47-88-b.business.telecomitalia.it [88.47.166.85]) by mail.postgresql.org (Postfix) with ESMTP id CC0B763303C for ; Mon, 23 Feb 2009 14:18:24 -0400 (AST) Received: from [10.77.1.47] ([10.77.1.47]) by srvmailbs.bs.local (Lotus Domino Release 6.5.4) with ESMTP id 2009022319181829-10216 ; Mon, 23 Feb 2009 19:18:18 +0100 Message-ID: <49A2E86A.60409@saga.it> Date: Mon, 23 Feb 2009 19:18:18 +0100 From: Nicola Mauri User-Agent: Thunderbird 2.0.0.19 (Windows/20081209) MIME-Version: 1.0 To: Scott Marlowe CC: pgsql-admin@postgresql.org Subject: Re: Crash with data corruption under Windows References: <499EBEF0.1010408@saga.it> <49A2D39F.7060203@saga.it> In-Reply-To: X-MIMETrack: Itemize by SMTP Server on saga_bs1/saga(Release 6.5.4|March 27, 2005) at 23/02/2009 19.18.18, Serialize by Router on Front_Bs/saga at 02/23/2009 07:19:30 PM, Serialize complete at 02/23/2009 07:19:30 PM Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=ISO-8859-1; format=flowed X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests=none X-Spam-Level: X-Archive-Number: 200902/197 X-Sequence-Number: 31418 -------- Messaggio Originale -------- Oggetto: Re: [ADMIN] Crash with data corruption under Windows Da: Scott Marlowe > On Mon, Feb 23, 2009 at 9:49 AM, Nicola Mauri wrote: > >> -------- Messaggio Originale -------- >> Oggetto: Re: [ADMIN] Crash with data corruption under Windows >> Da: Scott Marlowe >> >>> Usually when I see the permission denied thing there's anti-virus >>> software hard locking pgsql files in the middle of the day. >>> >>> >> Have you experienced data loss too in that case? >> (however, we already excluded pgsql directories from anti-virus scanning). >> > > I've not, but I rarely run postgresql under windows. When we do it's > on a laptop for personal use / demo use. All our servers run Linux. > However, on this list, when I've seen this happen, it has been known > to result in data loss. > > Note that once your database is corrupted, no amount of fixing can > make it safe to keep using. you need to get a good reliable dump from > it, reinitdb and reload your data. So not trust a database that's > gotten corrupted and seems mostly fixed. It's a timebomb. > > Hi Scott, we had to recreate the cluster and reload data from a dump, because we were unable to read any table (some critical indexes was broken). However we would like to try to recovery the most recent data from the corrupted datafiles (as a help for manual insertion). Is there any method to extract raw data from the pgsql table files? regards, Nicola