| 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 |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Euler Taveira de Oliveira | 2005-07-01 02:53:34 | Re: Open items |
| Previous Message | Oliver Jowett | 2005-07-01 02:44:54 | Re: 2PC transaction id |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Oliver Jowett | 2005-07-01 03:18:52 | Re: 2PC transaction id |
| Previous Message | Oliver Jowett | 2005-07-01 02:44:54 | Re: 2PC transaction id |