Re: Next steps on pg_stat_statements normalisation - Mailing list pgsql-hackers

From Simon Riggs
Subject Re: Next steps on pg_stat_statements normalisation
Date
Msg-id CA+U5nMJyanCwh86mT_05SDkUbcPiAWgJ+9xAY8+0tc9nmPg1gw@mail.gmail.com
Whole thread Raw
In response to Next steps on pg_stat_statements normalisation  (Peter Geoghegan <peter@2ndquadrant.com>)
Responses Re: Next steps on pg_stat_statements normalisation  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
On Sun, Jan 22, 2012 at 5:30 AM, Peter Geoghegan <peter@2ndquadrant.com> wrote:

> So, having received feedback from Tom and others in relation to this
> patch, I would like to state how I think I should go about addressing
> various concerns to ensure that a revision of the patch gets into the
> 9.2 release. As I've said time and again, I think that it is very
> important that we have this, sooner rather than later.

Nothing can be ensured completely, but I would add this is a very
important feature. Without it, large systems without prepared
statements are mostly untunable and therefore untuned, which is a bad
thing.

--
 Simon Riggs                   http://www.2ndQuadrant.com/
 PostgreSQL Development, 24x7 Support, Training & Services


pgsql-hackers by date:

Previous
From: Jeff Janes
Date:
Subject: Re: CLOG contention, part 2
Next
From: Greg Smith
Date:
Subject: Re: Publish checkpoint timing and sync files summary data to pg_stat_bgwriter