Re: [PATCH] Refactor SLRU to always use long file names

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-04-08 10:09:38
Message-ID: CAJ7c6TN9Lo_EKSPpgrSJRDKW=NTh9K5k-ve1v7FMiz-0bQSxGg@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

> > 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.

Rebased.

--
Best regards,
Aleksander Alekseev

Attachment Content-Type Size
v9-0001-Always-use-long-SLRU-segment-file-names.patch text/x-patch 14.1 KB

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tomas Vondra 2026-04-08 10:20:53 Re: Adding REPACK [concurrently]
Previous Message Amit Langote 2026-04-08 09:58:23 Re: Eliminating SPI / SQL from some RI triggers - take 3