| From: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
|---|---|
| To: | Maciek Sakrejda <msakrejda(at)truviso(dot)com> |
| Cc: | Peter Tap <ptrtap(at)yahoo(dot)com>, pgsql-jdbc(at)postgresql(dot)org |
| Subject: | Re: Transactional support across multiple machines... |
| Date: | 2010-11-17 18:47:13 |
| Message-ID: | 4CE42331.30109@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
On 17.11.2010 20:40, Maciek Sakrejda wrote:
> Prepared transactions:
> http://www.postgresql.org/docs/9.0/static/sql-prepare-transaction.html
Yeah, two-phase commit is the usual solution. But you shouldn't usually
try to implement that yourself, you should pick an existing Transaction
Manager. Java application servers usually include one, so if you're
using an application server, just configure your application to use XA
connections and let the app server handle the two-phase commit for you.
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Tap | 2010-11-17 18:55:21 | Re: Transactional support across multiple machines... |
| Previous Message | Maciek Sakrejda | 2010-11-17 18:40:57 | Re: Transactional support across multiple machines... |