| From: | Aleksander Alekseev <aleksander(at)tigerdata(dot)com> |
|---|---|
| To: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Cc: | Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, Rustam ALLAKOV <rustamallakov(at)gmail(dot)com>, Michael Paquier <michael(at)paquier(dot)xyz> |
| Subject: | Re: [PATCH] Refactor SLRU to always use long file names |
| Date: | 2026-01-07 14:42:27 |
| Message-ID: | CAJ7c6TP_k+s6K2fdi4No-a7t+TZqkV7GUfbwQeDggfaWRj3zGA@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi Heikki,
> Since commit bd8d9c9bdf "Widen MultiXactOffset to 64 bits",
> "pg_multixact/members" should not be in that list anymore.
I missed this one. Fixed, thanks.
> Also, it seems misleading that a function called "check_*" doesn't
> merely check for things, but renames files.
Fair point. I renamed it to `ensure_long_slru_segment_filenames`.
> Could we copy/link them with the new long names to begin with?
That's an interesting idea.
What I personally don't like about it is the fact that a single
migration will affect the logic of every run of pg_upgrade, even in
the far future, for instances that don't need this migration.
Previously I showed [1] that the entire migration takes little time
(note that we had to migrate pg_multixact/members back then). So I
don't think this optimization is a good idea in the long run, unless
we reach a consensus on the opposite.
--
Best regards,
Aleksander Alekseev
| Attachment | Content-Type | Size |
|---|---|---|
| v8-0001-Always-use-long-SLRU-segment-file-names.patch | text/x-patch | 16.4 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2026-01-07 14:45:20 | Re: nbtree: Cache operator family OID in _bt_setup_array_cmp |
| Previous Message | Henson Choi | 2026-01-07 14:16:11 | Re: SQL Property Graph Queries (SQL/PGQ) |