| From: | Andrew Frolov <andrewfrolov(at)gmail(dot)com> |
|---|---|
| To: | pgsql-jdbc(at)postgresql(dot)org |
| Cc: | heikki(dot)linnakangas(at)iki(dot)fi |
| Subject: | PostgreSQL JDBC bug with XA recovery? |
| Date: | 2013-02-28 14:54:23 |
| Message-ID: | 512F6F9F.9000906@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2013-02-28 15:23:03 | Re: PostgreSQL JDBC bug with XA recovery? |
| Previous Message | Dave Cramer | 2013-02-27 20:13:14 | Re: ENUM type via JDBC using connect string ... |