On Sun, Sep 21, 2025 at 12:19 PM Jelte Fennema-Nio <[email protected]> wrote:
> On Sun, 21 Sept 2025 at 19:44, Tom Lane <[email protected]> wrote: > > Yeah, if it were 18-only we'd need a powwow about whether to break > > release freeze. But since it's been there since 17 and nobody > > noticed, I'm content to wait till after 18.0 to fix it. > > People definitely noticed[1], but I agree that there's no reason to > rush this fix out before the 18 release. > > Patch looks good, but obviously needs some tests. > > [1]: > https://www.postgresql.org/message-id/flat/CAMEv5_syU0ZopE-2Wr8A8QksqrCyYT2hW06Rgw4RSPdyJO-%3Dfw%40mail.gmail.com > > I'm presuming this report is also about the same underlying issue. https://www.postgresql.org/message-id/CAJDiXghdFcZ8%3Dnh4G69te7iRr3Q0uFyXxb3ZdG09_GTNZXwH0g%40mail.gmail.com It too has a patch included. David J.
