Re: Postgres 8.3.1 RowExclusiveLock With JDBC XA

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Urciolo, Kevin" <Kevin(dot)Urciolo(at)ngc(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Postgres 8.3.1 RowExclusiveLock With JDBC XA
Date: 2008-09-09 01:30:29
Message-ID: 11484.1220923829@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

"Urciolo, Kevin" <Kevin(dot)Urciolo(at)ngc(dot)com> writes:
> I am having a problem where row exclusive locks are causing applications
> and vacuums to hang. I shutdown all applications, but the locks remain.
> I stop and start postgres, but the locks are still there. A pid is not
> listed. This problem started showing up after switching to the XA
> datasource with the Postgres JDBC driver. Is this causing problems?

The null PID fields indicate that these locks are being held by
uncommitted prepared transactions, so the pg_prepared_xacts view might
give you useful info. I concur that this suggests an XA problem.
You might have better luck asking about that in the pgsql-jdbc list.

regards, tom lane

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Merlin Moncure 2008-09-09 01:49:23 Re: A challenge for the SQL gurus out there...
Previous Message joe speigle 2008-09-09 01:25:24 Re: ERROR: cache lookup failed for relation