On 12.07.2024 01:01, Michael Paquier wrote:
Please let's move this point to its own thread and deal with it with
an independent patch. Hiding that in a thread that's already quite
long is not a good idea. This needs proper review, and a separate
thread with a good subject to describe the problem will attract a
better audience to deal with the problem you are seeing.
I was not paying much attention, until you've mentioned that this was
an issue with HEAD.
--
Michael
Sure, created a separate thread [1]. Please disregard the second patch in this thread. Duplicating the last version of the relevant patch here to avoid any confusion.
[1] https://www.postgresql.org/message-id/b72f2d89-820a-4fa2-9058-b155cf646f4f%40gmail.com
