Re: [PATCH] Refactor SLRU to always use long file names
Aleksander Alekseev <aleksander@timescale.com>
From: Aleksander Alekseev <aleksander@timescale.com>
To: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Cc: Michael Paquier <michael@paquier.xyz>
Date: 2024-12-05T08:08:42Z
Lists: pgsql-hackers
Hi, > I guess we are going to need either a `pg_writecontoldata` tool or > `pg_controldata -w` flag. I wonder which option you find more > attractive, or maybe you have better ideas? For the record, Michael and I had a brief discussion about this offlist and decided to abandon the idea of adding TAP tests, relying only on buildfarm. Also I will check if we have a clear error message in case when a user forgot to run pg_upgrade and running new slru.c with old filenames. If the user doesn't get such an error message I will see if it's possible to add it somewhere in slru.c without introducing much performance overhead. Also I'm going to submit precise steps to test this migration manually for the reviewers convenience. -- Best regards, Aleksander Alekseev
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Widen MultiXactOffset to 64 bits
- bd8d9c9bdfa0 19 (unreleased) cited
-
Index SLRUs by 64-bit integers rather than by 32-bit integers
- 4ed8f0913bfd 17.0 cited