On Sun, Aug 10, 2025 at 12:37 PM Noah Misch <n...@leadboat.com> wrote: > Thanks. Given the current state of freeze for tomorrow's release wrap, the > decision is less obvious than usual. I'm seeing these options: > > 1. Remove the new assertion in v13-v18. > 2. Push your proposed fix. > 3. Change nothing. (This would be the choice if one is maximally concerned > about deviating from the freeze and unconcerned about --enable-cassert > builds of releases.) > > I am inclined to make today's change be (1).
Sounds right to me. -- Robert Haas EDB: http://www.enterprisedb.com