I agree with Cristóvão. Also, two-phase commit only makes sense in the
context of multiple database servers which are replicating to each other in
real time. Once postgresql has replication in place then they should
probably start considering two-phase commit; unless they decide to roll out
both at once of course. ;-)
I continue to be impressed with the progress of the postgresql development
team, and how stable the released versions are. Keep up the good work!
Wes Sheldahl
Cristóvão Dalla Costa <cbraga@bsi.com.br>@postgresql.org on 10/28/2002
06:02:24 PM
Sent by: pgsql-general-owner@postgresql.org
To: Robert Treat <xzilla@users.sourceforge.net>
cc: stephen@cass-ltd.co.uk, "pgsql-general@postgresql.org"
<pgsql-general@postgresql.org>
Subject: Re: [GENERAL] Two Phase Commit support
Robert Treat wrote:
> I'm not sure of the functionality your looking for, can you point me to
> a definition of "two phased commits"?
>
> Robert Treat
He's probably updating/inserting data on many pgsql servers at once,
two-phase commits are the best-known algorithm to do it safely:
<details snipped>
I don't think there's any way to do it in Pgsql. Once you committed the
data the first time, the only way to undo the changes is to send a batch
of queries to reverse them.
Cristóvão
>
>
> On Sat, 2002-10-26 at 06:53, Stephen J. Thompson wrote:
>
> >Hello all,
> >
> >Is it correct that postgresql can not support two phase commits? If
> not is
> >there any plans to do so? We are doing a large amount of development
> on EJB
> >servers and need to perform two phase commits between the database
> server and
> >the mom server.
> >
> >Regards,
> >
> >Stephen.
---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo@postgresql.org so that your
message can get through to the mailing list cleanly