Received: from localhost (pluto.hub.org [200.46.204.4]) by postgresql.org (Postfix) with ESMTP id 1A1EC9FA3AB for ; Fri, 3 Nov 2006 00:30:20 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.4]) (amavisd-new, port 10024) with ESMTP id 13151-02 for ; Fri, 3 Nov 2006 00:30:18 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey- Received: from foggy.rox.net (foggy.rox.net [213.214.0.41]) by postgresql.org (Postfix) with ESMTP id 462D09FA219 for ; Fri, 3 Nov 2006 00:30:18 -0400 (AST) Received: from localhost ([127.0.0.1]) by foggy.rox.net with esmtp (Exim 4.62) (envelope-from ) id 1Gfqh6-00010g-Kr for pgsql-hackers@postgresql.org; Fri, 03 Nov 2006 05:30:16 +0100 Received: from luna.rox.net ([212.63.65.43] helo=webmail.rockenstein.de) by foggy.rox.net with smtp (Exim 4.62) (envelope-from ) id 1Gfqh5-00010L-P1 for pgsql-hackers@postgresql.org; Fri, 03 Nov 2006 05:30:15 +0100 Message-ID: Date: Fri, 03 Nov 2006 05:30:16 +0100 From: "Joachim Wieland" Subject: "recovering prepared transaction" after server restart message To: pgsql-hackers@postgresql.org Reply-to: X-Mailer: Hastymail 0.5 MIME-Version: 1.0 Content-type: text/plain; charset=iso-8859-1 X-Envelope-From: X-Scanned-By: rockenstein AG X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=1.306 tagged_above=0 required=5 tests=AWL, BAYES_50, FORGED_RCVD_HELO, INVALID_MSGID, MSGID_NO_HOST X-Spam-Level: * X-Archive-Number: 200611/93 X-Sequence-Number: 93555 There have been several reports that people could not vacuum any more or observed strange locks even after server restart. The reason was that they still had uncommitted prepared transactions around. I wonder if it could help to change the log level from ereport(LOG, (errmsg("recovering prepared transaction %u", xid))); to WARNING maybe in order to make that message more striking within the normal startup messages. Joachim