From: | Peter Geoghegan <peter(at)2ndquadrant(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Daniel Farina <daniel(at)heroku(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Review of: pg_stat_statements with query tree normalization |
Date: | 2012-01-17 00:57:55 |
Message-ID: | CAEYLb_Uf0eEWkyVK2ht8NW7xq7MTTokFKWWKdX7sbj5kc3dXQg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 16 January 2012 23:53, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Well, short of seeing an acceptable patch for the larger thing, I don't
> want to accept a patch to add that field to Const, because I think it's
> a kluge. I'm still feeling that there must be a better way ...
What does an acceptable patch look like? Does your objection largely
hinge on the fact that the serialisation is performed after the
re-writing stage rather on the raw parse tree, or is it something
else?
Despite my full plate this commitfest, I am determined that this
feature be available in 9.2, as I believe that it is very important.
Instrumentation of queries is something that it just isn't possible to
do well right now, with each of the available third party solutions or
pg_stat_statements. That really needs to change.
--
Peter Geoghegan http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training and Services
From | Date | Subject | |
---|---|---|---|
Next Message | Daniel Farina | 2012-01-17 01:06:02 | Re: Review of: pg_stat_statements with query tree normalization |
Previous Message | Daniel Farina | 2012-01-17 00:56:11 | Should we add crc32 in libpgport? |