From: | Peter Geoghegan <peter(at)2ndquadrant(dot)com> |
---|---|
To: | Greg Smith <greg(at)2ndquadrant(dot)com> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Review of: pg_stat_statements with query tree normalization |
Date: | 2012-01-16 23:58:24 |
Message-ID: | CAEYLb_U1ihxcr8SiBHP31VEEAYX=MUdbTSSMqR5W-twQDG_VKQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 16 January 2012 23:43, Greg Smith <greg(at)2ndquadrant(dot)com> wrote:
> While Peter had a version of this that worked completely within the
> boundaries of an extension, no one was really happy with that. At a minimum
> the .length changes really need to land in 9.2 to enable this feature to
> work well. As Daniel noted, it's a lot of code changes, but not a lot of
> code complexity.
Right. As I've said in earlier threads, we're mostly just making the
YYLTYPE representation closer to that of the default, which has the
following fields: first_line, first_column, last_line and
last_column. I just want two fields. I think we've already paid most
of the price that this imposes, by using the @n feature in the first
place. Certainly, I couldn't isolate any additional overhead.
--
Peter Geoghegan http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training and Services
From | Date | Subject | |
---|---|---|---|
Next Message | Greg Smith | 2012-01-17 00:01:34 | Re: Why is CF 2011-11 still listed as "In Progress"? |
Previous Message | Tom Lane | 2012-01-16 23:53:34 | Re: Review of: pg_stat_statements with query tree normalization |