From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Ondrej Chaloupka <ochaloup(at)redhat(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org, pgsql-bugs(at)postgresql(dot)org, Pavel Raiskup <praiskup(at)redhat(dot)com>, Tom Jenkinson <tom(dot)jenkinson(at)redhat(dot)com> |
Subject: | Re: [BUGS] Incorrect response code after XA recovery |
Date: | 2013-07-29 13:50:24 |
Message-ID: | 25825.1375105824@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs pgsql-general pgsql-jdbc |
Ondrej Chaloupka <ochaloup(at)redhat(dot)com> writes:
> The OTS specification requires both bottom up and top down recovery to be triggered by the recovering resource. This causes that two rollback calls are done against the DB. DB receives rollback call and does the rollback. Then for the second time it returns the exceptional code. As the DB already rollbacked the transaction and forgot about it the DB returns error that no such transaction exists. But this seems to be against OTS specification.
It's not likely that we would consider changing the behavior of ROLLBACK
PREPARED. The alternatives we would have are (1) silently accept a
ROLLBACK against a non-existent transaction ID, or (2) remember every
rolled-back ID forever. Neither seems sane in the least.
It seems to me that this is something client-side code, probably the XA
manager, would need to deal with. The XA manager already has to track
uncommitted 2-phase transactions, and would furthermore have the best
idea of when it would be safe to forget about a rolled-back ID.
Right offhand it appears to me that that Red Hat bug is filed against
the correct component, and you need to push them harder to fix their
bug/shortcoming rather than claim it's our problem.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Euclid Nikiforov | 2013-07-29 13:55:13 | Re: BUG #8334: Merge Join drops records |
Previous Message | Ondrej Chaloupka | 2013-07-29 13:33:44 | Incorrect response code after XA recovery |
From | Date | Subject | |
---|---|---|---|
Next Message | Javier de la Torre | 2013-07-29 14:08:01 | Re: Event trigger information accessibility on plpgsql |
Previous Message | Adrian Klaver | 2013-07-29 13:45:11 | Re: to_char with locale decimal separator |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Jenkinson | 2013-07-29 14:19:34 | Re: Incorrect response code after XA recovery |
Previous Message | Dave Cramer | 2013-07-29 13:46:48 | Re: DatabaseMetaData getImportedKeys() order |