Received: from makus.postgresql.org (makus.postgresql.org [98.129.198.125]) by mail.postgresql.org (Postfix) with ESMTP id 1008461AFBB for ; Fri, 20 Jan 2012 11:01:48 -0400 (AST) Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1RoFyN-0005Nb-IF for pgsql-admin@postgresql.org; Fri, 20 Jan 2012 15:01:47 +0000 Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.2/8.14.2) with ESMTP id q0KF1XVH008886; Fri, 20 Jan 2012 10:01:33 -0500 (EST) To: paddy carroll cc: pgsql-admin@postgresql.org Subject: Re: persistent locks In-reply-to: <5C0CD2F1-56F5-471D-9A5C-9C6CB041873C@gmail.com> References: <5C0CD2F1-56F5-471D-9A5C-9C6CB041873C@gmail.com> Comments: In-reply-to paddy carroll message dated "Fri, 20 Jan 2012 13:08:16 +0000" Date: Fri, 20 Jan 2012 10:01:33 -0500 Message-ID: <8885.1327071693@sss.pgh.pa.us> From: Tom Lane X-Pg-Spam-Score: -1.9 (-) X-Archive-Number: 201201/113 X-Sequence-Number: 39025 paddy carroll writes: > 3) For 8.3.7 the locks persist a database shutdown and startup cycle - I have had to trash and rebuild the database in question. > 4) For 8.3.7 I have demonstrated that I can remedy the problem by stopping the database, deleting the contents of pg_twophase and pg_subtrans and restarting the database Egad. Please read about prepared transactions and how to commit them or roll them back; or else fix your applications to not use them. regards, tom lane