Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1UyP1W-0002nM-Lx for pgsql-admin@arkaria.postgresql.org; Sun, 14 Jul 2013 16:19:46 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1UyP1V-0000q9-AU for pgsql-admin@arkaria.postgresql.org; Sun, 14 Jul 2013 16:19:45 +0000 Received: from makus.postgresql.org ([2001:4800:7903:4::125]) by malur.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1UyP1T-0000q0-4F for pgsql-admin@postgresql.org; Sun, 14 Jul 2013 16:19:43 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1UyP1M-0003RB-5s for pgsql-admin@postgresql.org; Sun, 14 Jul 2013 16:19:42 +0000 Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.5/8.14.5) with ESMTP id r6EGJYs3016425; Sun, 14 Jul 2013 12:19:34 -0400 (EDT) From: Tom Lane To: Vincent Lau cc: pgsql-admin Subject: Re: 0-byte 2PC File In-reply-to: References: Comments: In-reply-to Vincent Lau message dated "Sat, 13 Jul 2013 16:41:23 -0700" Date: Sun, 14 Jul 2013 12:19:34 -0400 Message-ID: <16424.1373818774@sss.pgh.pa.us> X-Pg-Spam-Score: 0.4 (/) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-admin Precedence: bulk Sender: pgsql-admin-owner@postgresql.org Vincent Lau writes: > We are running 8.4.13 on this particular database and recently we have been > getting empty two phase commit state files inside the pg_twophase > directory. These prepared transactions can't be rolled back due to the > empty state file. Here is an example of the error message. > ERROR: two-phase state file for transaction 121421120 is corrupt > The only way to get rid of this is to restart the database, which is just a > bandaid solution at this point. Is there a waiting transaction corresponding to that file? If not you could just manually remove the file, I think. Not that that isn't a band-aid, but it'd be less painful than a restart. Do you see any error messages logged at the time the transaction PREPARE is attempted? regards, tom lane -- Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin