Gavin Wahl writes:
> Hello,
>
> I've read the documentation for two-phase commit and it sounds interesting,
> but
> I'm having trouble thinking of how to actually put it into production. How are
> people using it? Do you use a XA transaction manager or something custom
> built?
> How dos the re
On Wed, Jul 19, 2017 at 7:10 PM, Gavin Wahl wrote:
> I've read the documentation for two-phase commit and it sounds interesting,
> but
> I'm having trouble thinking of how to actually put it into production. How are
> people using it? Do you use a XA transaction manager or something custom
> bui
Hello,
I've read the documentation for two-phase commit and it sounds interesting, but
I'm having trouble thinking of how to actually put it into production. How are
people using it? Do you use a XA transaction manager or something custom built?
How dos the reconciliation work when a component cra
On Mon, Jul 23, 2007 at 12:29:06PM -0700, Jeff Davis wrote:
> The way you worded your reply would scare anyone away from using 2PC at
> all, and 2PC might be useful in Ben's case.
Well, I didn't intend to scare anyone away from it! Apologies.
A
--
Andrew Sullivan | [EMAIL PROTECTED]
The whole
On Mon, 2007-07-23 at 14:48 -0400, Andrew Sullivan wrote:
> Right. But there's a big difference between this case and many
> catastrophic problems, because it's entirely possible that the whole
> reason you were using 2PC was to increase reliability in the face of
> various disasters, including op
On Mon, Jul 23, 2007 at 11:59:39AM -0700, Ben wrote:
> Good point, but just to be clear, I was asking about 2PC because our app
> writes to two different databases, and the authors never considered that
> the second commit might fail.
Ok, so as long as you're willing to accept that "second commi
Good point, but just to be clear, I was asking about 2PC because our app
writes to two different databases, and the authors never considered that
the second commit might fail.
On Mon, 23 Jul 2007, Andrew Sullivan wrote:
On Fri, Jul 20, 2007 at 05:17:00PM -0700, Jeff Davis wrote:
On Fri, 2007
On Fri, Jul 20, 2007 at 05:17:00PM -0700, Jeff Davis wrote:
> On Fri, 2007-07-20 at 15:26 -0400, Andrew Sullivan wrote:
> > instance, recently it turned out that there was a way, using 2PC, to
> > lock everybody out of the database. The only remedy to that at the
> > moment is to blow away all the
On Fri, 2007-07-20 at 15:26 -0400, Andrew Sullivan wrote:
> On Thu, Jul 19, 2007 at 03:13:27PM -0700, Ben wrote:
> > What corner case reduces 2pc from "guaranteed" to "very high probability"?
> > Is the worry if somebody leaves transactions in a prepared state for
> > weeks, only to find that dea
On Thu, Jul 19, 2007 at 03:13:27PM -0700, Ben wrote:
> What corner case reduces 2pc from "guaranteed" to "very high probability"?
> Is the worry if somebody leaves transactions in a prepared state for
> weeks, only to find that deadlock issues has arrisen at final commit time?
That's not the wor
Ben <[EMAIL PROTECTED]> writes:
> Er, right I guess I should have asked if it's more likely to commit a
> running transaction than a prepared one and it sounds like the answer
> is "no". :)
Less likely, because PREPARE TRANSACTION executes all the COMMIT-time
actions that can cause "expe
Er, right I guess I should have asked if it's more likely to commit a
running transaction than a prepared one and it sounds like the answer
is "no". :)
On Thu, 19 Jul 2007, Tom Lane wrote:
Ben <[EMAIL PROTECTED]> writes:
I'm reading the description of PREPARE TRANSACTION, and I see t
On Thu, 2007-07-19 at 15:13 -0700, Ben wrote:
> I'm reading the description of PREPARE TRANSACTION, and I see this:
>
> "...its state is fully stored on disk, and there is a very high
> probability that it can be committed successfully..."
>
> What corner case reduces 2pc from "guaranteed" to "v
Ben <[EMAIL PROTECTED]> writes:
> I'm reading the description of PREPARE TRANSACTION, and I see this:
> "...its state is fully stored on disk, and there is a very high
> probability that it can be committed successfully..."
> What corner case reduces 2pc from "guaranteed" to "very high probabilit
I'm reading the description of PREPARE TRANSACTION, and I see this:
"...its state is fully stored on disk, and there is a very high
probability that it can be committed successfully..."
What corner case reduces 2pc from "guaranteed" to "very high probability"?
Is the worry if somebody leaves
>We still don't know if Postgresql can do it, do we?
no, we do not know ;-)
anybody there please?
amy
__
Get Your Private, Free Email at http://www.hotmail.com
16 matches
Mail list logo
