PostgreSQL JDBC bug with XA recovery? - Mailing list pgsql-jdbc

From Andrew Frolov
Subject PostgreSQL JDBC bug with XA recovery?
Date
Msg-id 512F6F9F.9000906@gmail.com
Whole thread Raw
List pgsql-jdbc
Hi!

I've encountered a problem with xa transaction recovery.

PGXAConnection.recover() functions returns all pending XA transactions.
But the problem is, that in general case we cannot recover this
transactions in current connection, PostgreSQL require us to connect to
target database before recovering. This behavior breaks the expectations
of transaction managers.  We literally can't perform recovery if we have
a lot of pending xa transactions in different databases in PostgreSQL
cluster.

Maybe it would be good to replace
SELECT gid FROM pg_prepared_xacts
by
SELECT gid FROM pg_prepared_xacts,where owner = current_user ?

I found an old thread with same question, but without an answer.
http://www.postgresql.org/message-id/CAPSK6ngYLaRAy_FGGQqknTPE9FUDCRn32UShxuncWEyD+swD=w@mail.gmail.com


pgsql-jdbc by date:

Previous
From: Андрей Фролов
Date:
Subject: Re: PostgreSQL JDBC bug with XA recovery?
Next
From: dmp
Date:
Subject: Re: Automatic transactions in SELECT