Re: pg_stat_statements produces multiple entries for a single query with track = 'top'

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