Support for distributed transactions in 8.2.5

From: "Brian Oki (boki)" <boki(at)cisco(dot)com>
To: <pgsql-general(at)postgresql(dot)org>
Cc: "Brian Oki (boki)" <boki(at)cisco(dot)com>
Subject: Support for distributed transactions in 8.2.5
Date: 2007-10-11 15:35:43
Message-ID: 5FDF17E5F815DD429DBA1B1C2159DC0344E539@xmb-sjc-239.amer.cisco.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Hi,

I've read through the relevant documentation on distributed transactions
for PostgreSQL 8.2.5 but it leaves me with more questions than answers.
It is unclear to me how SQL statements can be executed at remote nodes
from a single coordinator and then use distributed two-phase commit (via
'prepare transaction tid' and 'commit prepared'). I worked at Oracle in
the distributed database group and could do things like the following
using PL/SQL, where we insert the same row into the same table on three
different nodes, including the local one:
insert into foo ....
insert into foo(at)node2(dot)acme(dot)com <BLOCKED::mailto:foo(at)node2(dot)acme(dot)com>
....
insert into foo(at)node3(dot)acme(dot)com <mailto:foo(at)node3(dot)acme(dot)com> ....
COMMIT
This sequence will insert a row into all three tables and do the
distributed atomic commitment.

My question is this: How does PostgreSQL 8.2.5 execute DML statements
(insert, update, delete, select) on remote nodes as part of the same
transaction? Where is the syntax specified? Or, is there a different
model supported? It's sort of like the synchronous multi-master
replication mentioned in Chapter 24. I'm looking for an integrated
solution.

Brian Oki, Ph.D.
Cisco Systems, Inc.

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Karsten Hilbert 2007-10-11 15:41:34 Re: XMIN semantic at peril ?
Previous Message Karsten Hilbert 2007-10-11 15:30:55 Re: XMIN semantic at peril ?