Re: PostgreSQL and distributed transactions

From: Joshua Tolley <eggyknap(at)gmail(dot)com>
To: Dimitri Fontaine <dfontaine(at)hi-media(dot)com>
Cc: Jayadevan M <Jayadevan(dot)Maymala(at)ibsplc(dot)com>, pgsql-general(at)postgresql(dot)org
Subject: Re: PostgreSQL and distributed transactions
Date: 2010-08-01 04:16:57
Message-ID: 4c54f53b.1864730a.7de6.1453@mx.google.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Thu, Jul 29, 2010 at 11:42:14AM +0200, Dimitri Fontaine wrote:
> Jayadevan M <Jayadevan(dot)Maymala(at)ibsplc(dot)com> writes:
> > But the initial setup for the client is done by 'Admin' and in that
> > work-flow, we need distributed transactions. The transaction will start
> > from the 'Admin" server, do some inserts on the 'Client' server and then
> > either rollback or commit on both the servers. Is it possible to do this
> > with PostgreSQL? Any helpful links?
>
> See about 2 Phase Commit, but you will need a transaction manager I guess :
>
> http://www.postgresql.org/docs/current/static/sql-prepare-transaction.html
>

If I may be allowed to toot my own horn, may I suggest this as an example:
http://blog.endpoint.com/2010/07/distributed-transactions-and-two-phase.html

--
Joshua Tolley / eggyknap
End Point Corporation
http://www.endpoint.com

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message John Krasnay 2010-08-01 15:22:38 Disk full and WALs
Previous Message Merlin Moncure 2010-07-31 19:36:43 Re: select a list of column values directly into an array