Skip site navigation (1) Skip section navigation (2)

Re: 2PC transaction id

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Oliver Jowett <oliver(at)opencloud(dot)com>
Cc: Dave Cramer <pg(at)fastcrypt(dot)com>,PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>,Heikki Linnakangas <hlinnaka(at)iki(dot)fi>
Subject: Re: 2PC transaction id
Date: 2005-07-01 02:51:44
Message-ID: 23857.1120186304@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-patches
Oliver Jowett <oliver(at)opencloud(dot)com> writes:
> Ok, so how do we get XA working when a single global transaction
> involves two databases on the same cluster?

It's the TM's responsibility to deal with that.  I would expect it to
hand out transaction IDs that consist of a common prefix and a
per-database suffix, if it does not know which resources it's dealing
with might share a common GID namespace.

There's a reason that the XA spec has such a ridiculously large
requirement for the length of a GID name, and it is that this is the
TM's problem not ours.

			regards, tom lane

In response to

Responses

pgsql-hackers by date

Next:From: Euler Taveira de OliveiraDate: 2005-07-01 02:53:34
Subject: Re: Open items
Previous:From: Oliver JowettDate: 2005-07-01 02:44:54
Subject: Re: 2PC transaction id

pgsql-patches by date

Next:From: Oliver JowettDate: 2005-07-01 03:18:52
Subject: Re: 2PC transaction id
Previous:From: Oliver JowettDate: 2005-07-01 02:44:54
Subject: Re: 2PC transaction id

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group