On Fri, 2010-03-12 at 12:07 -0500, Merlin Moncure wrote:
> of course. You can always explicitly open a transaction on the remote
> side over dblink, do work, and commit it at the last possible moment.
> Your transactions aren't perfectly synchronized...if you crash in the
> precise moment between committing the remote and the local you can get
> in trouble. The chances of this are extremely remote though.
If you want a better guarantee than that, consider using 2PC.
The problem with things that are "extremely remote" possibilities are
that they tend to be less remote than we expect ;)
Regards,
Jeff Davis
--
Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance
