Skip site navigation (1) Skip section navigation (2)

Re: 2PC transaction id

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 (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-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"
>
>


In response to

pgsql-hackers by date

Next:From: Oliver JowettDate: 2005-06-30 23:37:52
Subject: Re: 2PC transaction id
Previous:From: Alvaro HerreraDate: 2005-06-30 22:46:35
Subject: Re: 2PC transaction id

pgsql-patches by date

Next:From: Oliver JowettDate: 2005-06-30 23:37:52
Subject: Re: 2PC transaction id
Previous:From: Alvaro HerreraDate: 2005-06-30 22:46:35
Subject: Re: 2PC transaction id

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group