On Wed, Feb 1, 2023 at 5:42 PM Melih Mutlu <m.melihmu...@gmail.com> wrote:
> > > Thanks for investigating this error. I think it's the same error as the one > Shi reported earlier. [1] > I couldn't reproduce it yet but will apply your tweaks and try again. > Looking into this. > > [1] > https://www.postgresql.org/message-id/OSZPR01MB631013C833C98E826B3CFCB9FDC69%40OSZPR01MB6310.jpnprd01.prod.outlook.com I tried Shi-san's testcase earlier but I too could not reproduce it, so I assumed that it is fixed in one of your patches already and thus thought that the current issue is a new one. thanks Shveta
