Re: Detecting uncommitted changes - Mailing list pgsql-general

From Tom Lane
Subject Re: Detecting uncommitted changes
Date
Msg-id 17932.1325032914@sss.pgh.pa.us
Whole thread Raw
In response to Re: Detecting uncommitted changes  (Thomas Kellerer <spam_eater@gmx.net>)
Responses Re: Detecting uncommitted changes
List pgsql-general
Thomas Kellerer <spam_eater@gmx.net> writes:
> Tom Lane wrote on 27.12.2011 20:22:
>> More specifically, look to see if the current transaction has assigned
>> itself a transaction ID.  I think the easiest place to see this is in
>> pg_locks --- it will be holding exclusive lock on a TransactionId object
>> if so.

> Thanks for the answer. I came up with the following statement:

> select count(*)
> from pg_locks
> where pid = pg_backend_pid()
> and locktype in ('transactionid')

> does that look right to you?

No.  You forgot the exclusive-lock condition.

            regards, tom lane

pgsql-general by date:

Previous
From: Merlin Moncure
Date:
Subject: Re: Kindly Please Help Me
Next
From: Greg Donald
Date:
Subject: PostgreSQL 9.1 pg_dump setval() sets wrong value