| From: | Dave Cramer <pg(at)fastcrypt(dot)com> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)surnet(dot)cl> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: 2PC transaction id |
| Date: | 2005-06-30 22:59:19 |
| Message-ID: | 42CA297A-CF36-4779-A7DA-B019B296798F@fastcrypt.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
In reality all it takes is a sequence, however if it were system
generated it would be simpler
Dave
On 30-Jun-05, at 6:46 PM, Alvaro Herrera wrote:
> On Thu, Jun 30, 2005 at 06:39:43PM -0400, Dave Cramer wrote:
>
>> Do the transaction id's used in 2PC need to be unique across all
>> sessions?
>>
>
> Yes.
>
>
>> Do we provide a mechanism for this ?
>>
>
> Huh, the constraint is enforced by the server, but the ID is generated
> by the client.
>
>
>> If not shouldn't we provide a way to create a unique transaction id ?
>>
>
> Maybe a new function would suffice.
>
> --
> Alvaro Herrera (<alvherre[a]surnet.cl>)
> "Use it up, wear it out, make it do, or do without"
>
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Oliver Jowett | 2005-06-30 23:37:52 | Re: 2PC transaction id |
| Previous Message | Alvaro Herrera | 2005-06-30 22:46:35 | Re: 2PC transaction id |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Oliver Jowett | 2005-06-30 23:37:52 | Re: 2PC transaction id |
| Previous Message | Alvaro Herrera | 2005-06-30 22:46:35 | Re: 2PC transaction id |