Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1VggqE-0007CQ-9k for pgsql-performance@arkaria.postgresql.org; Wed, 13 Nov 2013 20:15:10 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1VggqD-0001g9-L2 for pgsql-performance@arkaria.postgresql.org; Wed, 13 Nov 2013 20:15:09 +0000 Received: from makus.postgresql.org ([2001:4800:7903:4::125]) by malur.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1VggqC-0001fK-D0 for pgsql-performance@postgresql.org; Wed, 13 Nov 2013 20:15:08 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1Vggq9-0005LH-Ek for pgsql-performance@postgresql.org; Wed, 13 Nov 2013 20:15:07 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id rADKE9Zg023791; Wed, 13 Nov 2013 15:14:09 -0500 From: Tom Lane To: Josh Berkus cc: Kevin Grittner , Andres Freund , Andrew Dunstan , Jeff Janes , Amit Kapila , "pgsql-performance@postgresql.org" Subject: Re: Performance bug in prepared statement binding in 9.2? In-reply-to: <5283D433.3040406@agliodbs.com> References: <51FAA1B8.6040809@agliodbs.com> <522E69F1.8070203@dunslane.net> <20130910122036.GF1024477@alap2.anarazel.de> <522F146D.2070908@dunslane.net> <5230B801.90507@agliodbs.com> <20130911211253.GF1138556@alap2.anarazel.de> <523120E9.6020300@agliodbs.com> <24236.1383940000@sss.pgh.pa.us> <1384014645.82057.YahooMailNeo@web162903.mail.bf1.yahoo.com> <19685.1384307200@sss.pgh.pa.us> <5283D433.3040406@agliodbs.com> Comments: In-reply-to Josh Berkus message dated "Wed, 13 Nov 2013 11:34:11 -0800" Date: Wed, 13 Nov 2013 15:14:09 -0500 Message-ID: <23790.1384373649@sss.pgh.pa.us> X-Pg-Spam-Score: -1.9 (-) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-performance Precedence: bulk Sender: pgsql-performance-owner@postgresql.org Josh Berkus writes: >> What I'm hoping will happen next is that the complainants will hot-patch >> that and see if it fixes their problems. We can't really determine >> what to do without that information. > Unfortunately, the original reporter of this issue will not be available > for testing for 2-3 weeks, and I haven't been able to devise a synthetic > test which clearly shows the issue. Well, we had a synthetic test from the other complainant. What's at stake now is whether this is a good enough fix for real-world cases. I'm willing to wait ... regards, tom lane -- Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance