On Fri, Mar 3, 2017 at 9:50 PM, Masahiko Sawada <sawada.m...@gmail.com> wrote: > Yes, it's taking a time to update logic and measurement but it's > coming along. Also I'm working on changing deadlock detection. Will > post new patch and measurement result.
I think that we should push this patch out to v11. I think there are too many issues here to address in the limited time we have remaining this cycle, and I believe that if we try to get them all solved in the next few weeks we're likely to end up getting backed into some choices by time pressure that we may later regret bitterly. Since I created the deadlock issues that this patch is facing, I'm willing to try to help solve them, but I think it's going to require considerable and delicate surgery, and I don't think doing that under time pressure is a good idea. >From a fairness point of view, a patch that's not in reviewable shape on March 1st should really be pushed out, and we're several days past that. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
