Pavan Deolasee <pavan.deola...@gmail.com> writes: > On Mon, Feb 6, 2017 at 5:44 AM, Andres Freund <and...@anarazel.de> wrote: >> +1. I don't think we serve our users by putting out a nontrivial bugfix >> hastily. Nor do I think we serve them in this instance by delaying the >> release to cover this fix; there's enough other fixes in the release >> imo.
> I'm bit a surprised with this position. The point is that there's a nontrivial chance of a hasty fix introducing worse problems than we fix. Given the lack of consensus about exactly how to fix this, I'm feeling like it's a good idea if whatever we come up with gets some time to age awhile in git before we ship it. Obviously, 2ndQ or EDB or any other distributor can choose to ship a patch in their own builds if they're sufficiently comfortable with the particular patch. That doesn't translate to there having to be a fix in the community's wraps this week. regards, tom lane -- Sent via pgsql-hackers mailing list (firstname.lastname@example.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers