| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Stephen Frost <sfrost(at)snowman(dot)net> |
| Cc: | Andres Freund <andres(at)anarazel(dot)de>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, Alexander Korotkov <a(dot)korotkov(at)postgrespro(dot)ru>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Usage of epoch in txid_current |
| Date: | 2017-12-05 18:55:36 |
| Message-ID: | 14670.1512500136@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Stephen Frost <sfrost(at)snowman(dot)net> writes:
> * Andres Freund (andres(at)anarazel(dot)de) wrote:
>> I kinda wonder if we shouldn't just track nextXid as a 64bit integer
>> internally, instead of bothering with tracking the epoch
>> separately. Then we can "just" truncate it in the cases where it's
>> stored in space constrained places etc.
> This sounds reasonable to me, at least, but I've not been in these
> depths much.
+1 ... I think the reason it's like that is simply that nobody's revisited
the XID generator since we decided to require 64-bit integer support.
We'd need this for support of true 64-bit XIDs, too, though I'm unsure
whether that project is going anywhere anytime soon. In any case it
seems like a separable subset of that work.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Munro | 2017-12-05 19:25:18 | Re: dsa_allocate could not find 4 free pages |
| Previous Message | Tom Lane | 2017-12-05 18:50:11 | Re: Bitmap scan is undercosted? - boolean correlation |