> On 26 Oct 2023, at 12:31, Maxim Yablokov <m.yablokov@postgrespro.ru> wrote:
>
> I believe that the attached patch should fix this problem. Please have a look.
Thanks, I'll await pushing and backpatching if Tom who committed it has
insights into whether it was missed or if it indeed serves a purpose. If not I
think it should be backpatched all the way since it exists for all supported
versions.
--
Daniel Gustafsson