Hi Tom,
A little bit of information in the linked bugzilla report is that the
exception being returned has an XA error code of XAER_RMERR "An error
occurred in rolling back the transaction branch. The resource manager is
free to forget about the branch when returning this error so long as all
Hi Tom,
On Mon 29 Jul 2013 15:46:12 BST, Tom Lane wrote:
Tom Jenkinson writes:
A little bit of information in the linked bugzilla report is that the
exception being returned has an XA error code of XAER_RMERR "An error
occurred in rolling back the transaction branch. The resource manager is
fr
Tom Jenkinson writes:
> A little bit of information in the linked bugzilla report is that the
> exception being returned has an XA error code of XAER_RMERR "An error
> occurred in rolling back the transaction branch. The resource manager is
> free to forget about the branch when returning this
Tom Jenkinson writes:
> On Mon 29 Jul 2013 15:46:12 BST, Tom Lane wrote:
>> No idea, but in any case that's outside Postgres' purview. It's barely
>> possible that the Postgres JDBC driver has something to do with that,
>> but it sounds more like the XA manager's turf.
> I am not sure what you m
Ondrej Chaloupka 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
