On Wed, Aug 31, 2022 at 12:26:29PM -0400, Robert Haas wrote: > someone else to make the decision. But that's not how it works. The > RMT concept was invented precisely to solve problems like this one, > where the patch authors don't really want to revert it but other > people think it's pretty busted. If such problems were best addressed > by waiting for a long time to see whether anything changes, we > wouldn't need an RMT. That's exactly how we used to handle these kinds > of problems, and it sucked.
I saw the RMT/Jonathan stated August 28 as the cut-off date for a decision, which was later changed to September 1: > The RMT is still inclined to revert, but will give folks until Sep 1 0:00 > AoE[1] to reach consensus on if SQL/JSON can be included in v15. This matches > up to Andrew's availability timeline for a revert, and gives enough time to > get through the buildfarm prior to the Beta 4 release[2]. I guess you are saying that setting a cut-off was a bad idea, or that the cut-off was too close to the final release date. For me, I think there were three questions: 1. Were subtransactions acceptable, consensus no 2. Could trapping errors work for PG 15, consensus no 3. Could the feature be trimmed back for PG 15 to avoid these, consensus ? I don't think our community works well when there are three issues in play at once. -- Bruce Momjian <br...@momjian.us> https://momjian.us EDB https://enterprisedb.com Indecision is a decision. Inaction is an action. Mark Batterson