> On 29 Mar 2023, at 12:00, Alexander Lakhin <exclusion@gmail.com> wrote:
> That issue was reported already as bug #16329:
> https://www.postgresql.org/message-id/flat/16329-7a6aa9b6fa1118a1%40postgresql.org
>
> Maybe it's worth to register the fix proposed there for the next commitfest...
Summarizing that thread and registering the proposed patch for the next
commitfest seems like the right thing to do.
--
Daniel Gustafsson
