Hi, On 2022-04-14 11:33:45 -0400, Robert Haas wrote: > On Thu, Apr 14, 2022 at 10:42 AM Tom Lane <t...@sss.pgh.pa.us> wrote: > > Robert Haas <robertmh...@gmail.com> writes: > > > On Wed, Apr 13, 2022 at 8:38 PM Andres Freund <and...@anarazel.de> wrote: > > >> FWIW, that'd just mean it's an old bug that wasn't easily noticeable > > >> before, not that it's the fault of 277692220. > > > > > I think you're still on the hook to do something about it for this > > > release. > > > > I think you're trying to shoot the messenger. As Andres says, > > 277692220 just exposes that there is some pre-existing bug here. > > It's probably related to 84f5c2908, so I was planning to take a > > look at it at some point, but there are a few other higher-priority > > bugs in the way. > > Well, if you're willing to look at it that's fine, but I just don't > agree that it's OK to just commit things that add failing assertions > and drive off into the sunset.
I'm not planning to ride into the sunset / ignore this issue. All I said is that it's imo not the right thing to say that that commit broke things in 15. And that not a semantics game, because it means that the fix needs to go back further than 277692220. Greetings, Andres Freund
