Re: PostgreSQL XAResource & GlassFish 3.1.2.2

From: Kevin Grittner <kgrittn(at)ymail(dot)com>
To: Bryan Varner <bvarner(at)polarislabs(dot)com>
Cc: Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>, "pgsql-jdbc(at)postgresql(dot)org" <pgsql-jdbc(at)postgresql(dot)org>
Subject: Re: PostgreSQL XAResource & GlassFish 3.1.2.2
Date: 2013-02-13 22:05:46
Message-ID: 1360793146.49585.YahooMailNeo@web162902.mail.bf1.yahoo.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-jdbc

Bryan Varner <bvarner(at)polarislabs(dot)com> wrote:

> Why would each XAConnection need it's own pool?

Because one PostgreSQL connection can't interleave transactions,
and you can't commit or roll back a prepared transaction in a
connection which has a transaction open.  I thought you wanted to
be able to do such things.  They could be done if one XAConnection
could map to more than one PostgreSQL connection.

--
Kevin Grittner
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

Browse pgsql-jdbc by date

  From Date Subject
Next Message Bryan Varner 2013-02-13 22:20:14 Re: PostgreSQL XAResource & GlassFish 3.1.2.2
Previous Message Bryan Varner 2013-02-13 21:29:12 Re: PostgreSQL XAResource & GlassFish 3.1.2.2