From: | "Ross J(dot) Reedstrom" <reedstrm(at)rice(dot)edu> |
---|---|
To: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: protocol change in 7.4 |
Date: | 2002-11-05 01:22:55 |
Message-ID: | 20021105012255.GA7156@wallace.ece.rice.edu |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, Nov 04, 2002 at 08:10:29PM -0500, Mike Mascari wrote:
> Actually, I was thinking along the lines of a true CREATE
> DATABASE LINK implementation, where multiple databases could
> participate in a distributed transaction. That would require the
> backend in which the main query is executing to act as the
> "coordinator" and each of the other participating databases to
> act as "cohorts". And would require a protocol change to support
> the PREPARE, COMMIT-VOTE/ABORT-VOTE reply, and an ACK message
> following the completion of the distributed COMMIT or ABORT.
Right, you need TPC in order for pgsql to participate in transactions
that span anything outside the DB proper. A DB link is one example,
or an external transaction manager that coordinates DB and filesystem
updates, for example. Zope could use this, to coordinate the DB with
it's internal object store.
Ross
From | Date | Subject | |
---|---|---|---|
Next Message | Satoshi Nagayasu | 2002-11-05 01:33:16 | Re: protocol change in 7.4 |
Previous Message | Satoshi Nagayasu | 2002-11-05 01:14:21 | Re: protocol change in 7.4 |