| From: | Dave Cramer <pg(at)fastcrypt(dot)com> |
|---|---|
| To: | Oliver Jowett <oliver(at)opencloud(dot)com> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: 2PC transaction id |
| Date: | 2005-06-30 23:47:39 |
| Message-ID: | D701313E-CFF8-4FAE-A699-D107EF6308D9@fastcrypt.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
I'm thinking of the situation where one transaction occurs on more
than one backend, and there is
more than one transaction manager.
Dave
On 30-Jun-05, at 7:37 PM, Oliver Jowett wrote:
> Dave Cramer wrote:
>
>> Do the transaction id's used in 2PC need to be unique across all
>> sessions?
>>
>
> They are global IDs, yes.
>
>
>> Do we provide a mechanism for this ?
>>
>> If not shouldn't we provide a way to create a unique transaction id ?
>>
>
> Well, in XA the XIDs are assigned by the TM, the individual resources
> (e.g. a postgresql backend) just get *given* an XID to use.
>
> -O
>
> ---------------------------(end of
> broadcast)---------------------------
> TIP 1: subscribe and unsubscribe commands go to
> majordomo(at)postgresql(dot)org
>
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Stark | 2005-06-30 23:50:18 | Re: [HACKERS] Dbsize backend integration |
| Previous Message | Oliver Jowett | 2005-06-30 23:37:52 | Re: 2PC transaction id |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Stark | 2005-06-30 23:50:18 | Re: [HACKERS] Dbsize backend integration |
| Previous Message | Oliver Jowett | 2005-06-30 23:37:52 | Re: 2PC transaction id |