Re: [PATCH] Refactor SLRU to always use long file names - Mailing list pgsql-hackers

From Aleksander Alekseev
Subject Re: [PATCH] Refactor SLRU to always use long file names
Date
Msg-id CAJ7c6TPPJoFzP4vF-Huiz6MA=7rsRc+kXyvz840PBrgV76ZDkQ@mail.gmail.com
Whole thread Raw
In response to Re: [PATCH] Refactor SLRU to always use long file names  (Aleksander Alekseev <aleksander@timescale.com>)
List 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



pgsql-hackers by date:

Previous
From: Masahiro Ikeda
Date:
Subject: Re: Doc: clarify the log message level of the VERBOSE option
Next
From: Aleksander Alekseev
Date:
Subject: Re: [PATCH] Refactor bytea_sortsupport()