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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Peter Geoghegan <pg(at)heroku(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: pg_stat_statements produces multiple entries for a single query with track = 'top'
Date: 2013-08-11 00:45:56
Message-ID: 29410.1376181956@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Peter Geoghegan <pg(at)heroku(dot)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

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Peter Geoghegan 2013-08-11 01:00:51 Re: pg_stat_statements produces multiple entries for a single query with track = 'top'
Previous Message Peter Geoghegan 2013-08-11 00:34:43 pg_stat_statements produces multiple entries for a single query with track = 'top'