Re: [HACKERS] [PATCH] Provide 8-byte transaction IDs to

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Marko Kreen <markokr(at)gmail(dot)com>, pgsql-patches(at)postgresql(dot)org, pgsql-hackers(at)postgresql(dot)org, Jan Wieck <JanWieck(at)Yahoo(dot)com>
Subject: Re: [HACKERS] [PATCH] Provide 8-byte transaction IDs to
Date: 2006-07-26 21:18:41
Message-ID: 200607262118.k6QLIfE29763@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

Tom Lane wrote:
> Bruce Momjian <bruce(at)momjian(dot)us> writes:
> > I am sure you worked hard on this, but I don't see the use case, nor
> > have I heard people in the community requesting such functionality.
> > Perhaps pgfoundry would be a better place for this.
>
> The part of this that would actually be useful to put in core is
> maintaining a 64-bit XID counter, ie, keep an additional counter that
> bumps every time XID wraps around. This cannot be done very well from
> outside core but it would be nearly trivial, and nearly free, to add
> inside. Everything else in the patch could be done just as well as an
> extension datatype.
>
> (I wouldn't do it like this though --- TransactionIdAdvance itself is
> the place to bump the secondary counter.)

Agreed.

--
Bruce Momjian bruce(at)momjian(dot)us
EnterpriseDB http://www.enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Darcy Buskermolen 2006-07-26 21:27:17 Re: [HACKERS] [PATCH] Provide 8-byte transaction IDs to user level
Previous Message Tom Lane 2006-07-26 21:18:33 Re: xlogdump behaviour translating dropped relations

Browse pgsql-patches by date

  From Date Subject
Next Message Darcy Buskermolen 2006-07-26 21:27:17 Re: [HACKERS] [PATCH] Provide 8-byte transaction IDs to user level
Previous Message Hannu Krosing 2006-07-26 21:16:33 Re: [HACKERS] [PATCH] Provide 8-byte transaction IDs to