Tom,
> > [ Shrug... ] I remain of the opinion that 2PC is a solution in search
> > of a problem, because it does not solve the single point of failure
> > issue (just moves same from the database to the 2PC controller).
> > But some people want it anyway, and they aren't going to be satisfied
> > that we are an "enterprise grade" database until we can check off this
> > particular bullet point. As long as the implementation doesn't impose
> > any significant costs when not being used (which AFAICS Heikki's method
> > doesn't), I think we gotta hold our noses and do it.
2PC is a key to supporting 3rd-party replication tools, like C-JDBC. And is
useful for some other use cases, like slow-WAN-based financial transactions.
We know you don't like it, Tom. ;-)
--
Josh Berkus
Aglio Database Solutions
San Francisco
