From: Tom Lane <tgl@sss.pgh.pa.us>
To: paddy carroll <paddy.carroll@gmail.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: persistent locks
Date: Fri, 20 Jan 2012 10:01:33 -0500
Message-ID: <8885.1327071693@sss.pgh.pa.us> (raw)
In-Reply-To: <5C0CD2F1-56F5-471D-9A5C-9C6CB041873C@gmail.com>
References: <5C0CD2F1-56F5-471D-9A5C-9C6CB041873C@gmail.com>
paddy carroll <paddy.carroll@gmail.com> 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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, paddy.carroll@gmail.com
Subject: Re: persistent locks
In-Reply-To: <8885.1327071693@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox