On Mon, May 11, 2020 at 12:56 AM Tom Lane <t...@sss.pgh.pa.us> wrote: > > I think we should definitely get this fixed for pg13 ... > > -1 for shoving in such a thing so late in the cycle. We've survived > without it for years, we can do so for a few months more.
I agree, but also, we should start thinking about when to branch. I, too, have patches that aren't critical enough to justify pushing them post-freeze, but which are still good improvements that I'd like to get into the tree. I'm queueing them right now to avoid the risk of destabilizing things, but that generates more work, for me and for other people, if their patches force me to rebase or the other way around. I know there's always a concern with removing the focus on release N too soon, but the open issues list is 3 items long right now, and 2 of those look like preexisting issues, not new problems in v13. Meanwhile, we have 20+ active committers. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
