From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Bruce Momjian <bruce(at)momjian(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 user level |
Date: | 2006-07-26 20:04:11 |
Message-ID: | 17604.1153944251@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
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.)
The question though is if we did that, would Slony actually use it?
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Darcy Buskermolen | 2006-07-26 20:41:09 | Re: [HACKERS] [PATCH] Provide 8-byte transaction IDs to user level |
Previous Message | Andreas Pflug | 2006-07-26 19:56:27 | Re: GUC with units, details |
From | Date | Subject | |
---|---|---|---|
Next Message | Darcy Buskermolen | 2006-07-26 20:41:09 | Re: [HACKERS] [PATCH] Provide 8-byte transaction IDs to user level |
Previous Message | Zdenek Kotala | 2006-07-26 19:51:56 | Re: Allow commenting of variables in postgresql.conf to - |