Received: from maia.hub.org (maia-4.hub.org [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id 106E163359D for ; Thu, 6 May 2010 17:30:04 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 64455-09 for ; Thu, 6 May 2010 20:29:56 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by mail.postgresql.org (Postfix) with SMTP id CFF54633584 for ; Thu, 6 May 2010 17:29:55 -0300 (ADT) Received: (qmail invoked by alias); 06 May 2010 20:29:50 -0000 Received: from 95-88-223-90-dynip.superkabel.de (EHLO [192.168.178.22]) [95.88.223.90] by mail.gmx.net (mp007) with SMTP; 06 May 2010 22:29:50 +0200 X-Authenticated: #955937 X-Provags-ID: V01U2FsdGVkX1/YRZYnNRTYCee9of7As/eoN3i/KpsTDz+GawTI9C ASQgm9VRe0z6Md Message-ID: <4BE326B5.7020008@gmx.de> Date: Thu, 06 May 2010 22:29:41 +0200 From: Jan-Peter Seifert User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; de; rv:1.9.1.8) Gecko/20100227 Thunderbird/3.0.3 MIME-Version: 1.0 To: =?ISO-8859-1?Q?C=E9dric_Villemain?= CC: pgsql-admin@postgresql.org Subject: Re: out of memory ... References: <20100503111556.18910@gmx.net> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.9 tagged_above=-10 required=5 tests=BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001 X-Spam-Level: X-Archive-Number: 201005/86 X-Sequence-Number: 34559 Hello, >> ------------ >> LOG: database system was interrupted; last known up at 2010-03-26 11:22:36 CET >> LOG: database system was not properly shut down; automatic recovery in progress >> LOG: record with zero length at 1F/D2454CD0 >> ------------ >> >> The data still seemed to be okay - all the other transactions made before seem to be in the database. >> >> Is it okay to continue using the database(s) or is there a risk of hidden data corruption (fsync is on)? > > okay to continue if your filesystem didn't have issues (if postgres > start, then it is ok from its side) Sounds good. Thank you very much for your reply. Peter