Received: from maia.hub.org (maia-5.hub.org [200.46.204.29]) by mail.postgresql.org (Postfix) with ESMTP id CB54A632FCC for ; Mon, 3 May 2010 08:16:14 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.29]) (amavisd-maia, port 10024) with ESMTP id 56653-06 for ; Mon, 3 May 2010 11:16:03 +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 EF94A632A92 for ; Mon, 3 May 2010 08:16:02 -0300 (ADT) Received: (qmail 17897 invoked by uid 0); 3 May 2010 11:16:00 -0000 Received: from 192.124.237.7 by www050.gmx.net with HTTP; Mon, 03 May 2010 13:15:56 +0200 (CEST) Content-Type: text/plain; charset="iso-8859-1" Date: Mon, 03 May 2010 13:15:56 +0200 From: "Jan-Peter Seifert" Message-ID: <20100503111556.18910@gmx.net> MIME-Version: 1.0 Subject: out of memory ... To: pgsql-admin@postgresql.org X-Authenticated: #955937 X-Flags: 0001 X-Mailer: WWW-Mail 6100 (Global Message Exchange) X-Priority: 3 X-Provags-ID: V01U2FsdGVkX1/CraJxOzTC+TUU0U+VAjbYiEkH/K3hSmXW/WMGS7 YPfocY0DH2PEz76Yb3EU6aMCdu2JV1DVrhbQ== Content-Transfer-Encoding: 8bit X-GMX-UID: DdmreFcyODB6Rkv3fWRMSzk9Ji9SWhLK X-FuHaFi: 0.56000000000000005 X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.811 tagged_above=-10 required=5 tests=BAYES_50=0.8, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, T_TO_NO_BRKTS_FREEMAIL=0.01 X-Spam-Level: X-Archive-Number: 201005/16 X-Sequence-Number: 34489 Hello, how fatal is it for the server/data if a server runs out of memory? Happened on a Windows server some time ago. A transaction got too large. In the log it began with: ------------ TopMemoryContext: 37171728 total in 4046 blocks; 67640 free (4060 chunks); 37104088 used TopTransactionContext: 24576 total in 2 blocks; 18848 free (17 chunks); 5728 used CurTransactionContext: 8192 total in 1 blocks; 8176 free (1 chunks); 16 used ... ------------ Although all other clients had been closed no new connection was possible to terminate the session responsible for the out of memory problem. I guess it's because this transaction had been started by a superuser ... ------------ In the end the server was shut down via the service manager. On the next start of the server the log contained the following lines: ------------ 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)? Could you tell me, please? Thank you very much, Peter -- GRATIS für alle GMX-Mitglieder: Die maxdome Movie-FLAT! Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01