| From: | Alvaro Herrera <alvherre(at)surnet(dot)cl> |
|---|---|
| To: | Dave Cramer <pg(at)fastcrypt(dot)com> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: 2PC transaction id |
| Date: | 2005-06-30 22:46:35 |
| Message-ID: | 20050630224635.GB12397@surnet.cl |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
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 | Dave Cramer | 2005-06-30 22:59:19 | Re: 2PC transaction id |
| Previous Message | Dave Cramer | 2005-06-30 22:39:43 | 2PC transaction id |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dave Cramer | 2005-06-30 22:59:19 | Re: 2PC transaction id |
| Previous Message | Dave Cramer | 2005-06-30 22:39:43 | 2PC transaction id |