From: Jeff Davis <pgsql@j-davis.com>
To: Merlin Moncure <mmoncure@gmail.com>
Cc: elias ghanem <e.ghanem@acteos.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Is DBLINK transactional
Date: Fri, 12 Mar 2010 13:54:17 -0800
Message-ID: <1268430857.32299.11.camel@monkey-cat.sm.truviso.com> (raw)
In-Reply-To: <b42b73151003120907n1f977887y6132a564af9260b3@mail.gmail.com>
References: <201003121524.o2CFOD26012586@relay-ext.ornis.com>
<b42b73151003120907n1f977887y6132a564af9260b3@mail.gmail.com>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: pgsql@j-davis.com, mmoncure@gmail.com, e.ghanem@acteos.com
Subject: Re: Is DBLINK transactional
In-Reply-To: <1268430857.32299.11.camel@monkey-cat.sm.truviso.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox