On 27 March 2012 20:26, Tom Lane <t...@sss.pgh.pa.us> wrote: > I've committed the core-backend parts of this, just to get them out of > the way. Have yet to look at the pg_stat_statements code itself.
Thanks. I'm glad that we have that out of the way. > I ended up choosing not to apply that bit. I remain of the opinion that > this behavior is fundamentally inconsistent with the general rules for > assigning parse locations to analyzed constructs, and I see no reason to > propagate that inconsistency further than we absolutely have to. Fair enough. -- Peter Geoghegan http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training and Services -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
