| From: | Heikki Linnakangas <hlinnaka(at)iki(dot)fi> |
|---|---|
| To: | Maxim Orlov <orlovmg(at)gmail(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, Yura Sokolov <y(dot)sokolov(at)postgrespro(dot)ru>, Evgeny Voropaev <evgeny(dot)voropaev(at)tantorlabs(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Andrey Borodin <x4mmm(at)yandex-team(dot)ru> |
| Subject: | Re: Add 64-bit XIDs into PostgreSQL 15 |
| Date: | 2026-02-27 14:30:37 |
| Message-ID: | 00b3c734-36ef-45b6-9d7e-340fd18e8d79@iki.fi |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 27/02/2026 16:21, Maxim Orlov wrote:
> I just wanted to share my work-in-progress on switching the clog to 64
> bits. So far, I've only dealt with the clog itself. Right now, support
> for the x86 platform is lacking. But the first two patches are
> refactorings and can be committed promptly.
>
> What are your thoughts on this?
This is not useful, until we have an epoch on heap pages, and can deal
with 64-bit XIDs in many other places too. But it *would* be useful to
have an epoch on heap pages without this patch. It eliminates the need
to dirty pages when freezing, when there are no dead tuples. So I'd
suggest starting with epochs on heap pages.
- Heikki
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Álvaro Herrera | 2026-02-27 14:47:58 | Re: Show comments in \dRp+, \dRs+, and \dX+ psql meta-commands |
| Previous Message | Maxim Orlov | 2026-02-27 14:21:48 | Re: Add 64-bit XIDs into PostgreSQL 15 |