Request a Demo
Home   >   mailing lists

Re: pg_stat_statements produces multiple entries for a single query with track = 'top' - Mailing list pgsql-bugs

From Tom Lane
Subject Re: pg_stat_statements produces multiple entries for a single query with track = 'top'
Date
Msg-id 29410.1376181956@sss.pgh.pa.us
Whole thread Raw
In response to pg_stat_statements produces multiple entries for a single query with track = 'top'  (Peter Geoghegan <pg@heroku.com>)
Responses Re: pg_stat_statements produces multiple entries for a single query with track = 'top'
List pgsql-bugs
Tree view 
Peter Geoghegan <pg@heroku.com> writes:
> So with this single earthdistance query, there are multiple
> invocations of the executor, and thus multiple associated
> pg_stat_statements entries (one with 4 "calls").

Isn't this just the behavior we decided we wanted for SQL-language
functions?  At least, if we change pg_stat_statements so it doesn't
break out SQL-language functions, I'm sure somebody's gonna complain.

            regards, tom lane

pgsql-bugs by date:

Previous
From: Peter Geoghegan
Date:
Subject: pg_stat_statements produces multiple entries for a single query with track = 'top'
Next
From: Peter Geoghegan
Date:
Subject: Re: pg_stat_statements produces multiple entries for a single query with track = 'top'