On Sun, Aug 31, 2025 at 2:51 AM Richard Guo <[email protected]> wrote: > On Sun, Aug 31, 2025 at 8:41 AM Richard Guo <[email protected]> wrote: > > On Sun, Aug 31, 2025 at 8:12 AM Alexander Korotkov <[email protected]> > > wrote: > > > The same patch with a bit revised comment and commit message. > > > FWIW, I reported this same issue and proposed the patch last week in > > Discussion: > > https://postgr.es/m/CAMbWs48x=gsgan_bvq+j0rlqyfni9w725emjpwuzv1rrmai...@mail.gmail.com > > I think it's better to push this patch sooner rather than later, as > multiple people have encountered the issue in different ways. I'll go > ahead and push 0001 from my patch set shortly.
I see. You're much farther than I'm. Please, go ahead pushing this. > I don't think we need > to backpatch it, since the issue only occurs after commit e2debb643. I think you're right. ------ Regards, Alexander Korotkov Supabase
