Re: DROP DATABASE and prepared xacts - Mailing list pgsql-hackers

From Heikki Linnakangas
Subject Re: DROP DATABASE and prepared xacts
Date
Msg-id 45D0A861.70806@enterprisedb.com
Whole thread Raw
In response to Re: DROP DATABASE and prepared xacts  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: DROP DATABASE and prepared xacts  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Tom Lane wrote:
>> Actually, I think we should completely separate the namespaces of the 
>> global transaction identifiers, so that you could use the same gid in 
>> two different databases without a conflict.
> 
> Really?  They're supposed to be "global".

Well yeah, the TM should be assigning globally unique ids to every 
transaction. I don't trust all the TM implementations out there, and you 
could even have two different TMs stepping on each others toes, but then 
again I guess it's not really our problem as long as we give a nice 
error message.

The XA spec recommends assigning transaction ids using the naming rules 
specified for "OSI CCR atomic action identifiers". I don't know if it's 
widely used in practice.

--   Heikki Linnakangas  EnterpriseDB   http://www.enterprisedb.com


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: DROP DATABASE and prepared xacts
Next
From: Gregory Stark
Date:
Subject: Variable length varlena headers redux