From: | Maxim Orlov <orlovmg(at)gmail(dot)com> |
---|---|
To: | Evgeny Voropaev <evgeny(dot)voropaev(at)tantorlabs(dot)com> |
Cc: | y(dot)sokolov(at)postgrespro(dot)ru, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Add 64-bit XIDs into PostgreSQL 15 |
Date: | 2025-07-02 15:38:07 |
Message-ID: | CACG=eza1343rteW-CjmaKYGGavcTmiAMrhXfQFVXHrmHKNPq2g@mail.gmail.com |
Views: | Whole Thread | Raw Message | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, 1 Jul 2025 at 14:08, Evgeny Voropaev <evgeny(dot)voropaev(at)tantorlabs(dot)com>
wrote:
>
> And that difference in the HEAP_XMAX_COMMITED is the inconsistency, even
> when it is in garbage on a page. And, probably, it is not the only
> example of the problem.
>
I can't imagine that this action would cause any real issues. If you
know of any real problems, please tell me. Although I'm not
particularly against the idea of zeroing tuples, I don't see much
point in it, to be honest. But to ensure everyone's peace of mind,
I've made yet another commit that accomplishes this.
--
Best regards,
Maxim Orlov.
Attachment | Content-Type | Size |
---|---|---|
v64.zip | application/zip | 248.2 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Arseniy Mukhin | 2025-07-02 15:43:50 | Re: Cross-type index comparison support in contrib/btree_gin |
Previous Message | Tom Lane | 2025-07-02 15:36:01 | Re: Allow the "operand" input of width_bucket() to be NaN |