From: | Oliver Jowett <oliver(at)opencloud(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
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 03:56:59 |
Message-ID: | 42C4BF0B.3000002@opencloud.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
Oliver Jowett wrote:
> Tom Lane wrote:
>
>>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.
> I don't know if we can reasonably expect TMs not to hand out an
> identical XID to different RMs in the same global transaction.
Hm, I suppose we *can* assume that a TM won't hand out the same XID to
the same RM twice (except for the special case of TMJOIN), so we could
append a per-database suffix in the RM itself (e.g. JDBC driver) to
avoid conflicts within a database cluster.
-O
From | Date | Subject | |
---|---|---|---|
Next Message | Christopher Kings-Lynne | 2005-07-01 04:12:09 | Re: [ANNOUNCE] Language to use with SQL database - Number |
Previous Message | Marc G. Fournier | 2005-07-01 03:33:55 | Re: [ANNOUNCE] Language to use with SQL database - Number ONE computer |
From | Date | Subject | |
---|---|---|---|
Next Message | Neil Conway | 2005-07-01 05:14:15 | Re: ecpg: check for strdup() failure |
Previous Message | Oliver Jowett | 2005-07-01 03:18:52 | Re: 2PC transaction id |