Re: Normalization of utility queries in pg_stat_statements

On Wed, Aug 16, 2023 at 05:11:47PM +0800, jian he wrote:
> SELECT calls, toplevel, rows, query FROM pg_stat_statements ORDER BY
> query COLLATE "C";
> returns:
> calls | toplevel | rows | query
> -------+----------+------+------------------------------------
> 1 | t | 0 | CALL ptest3($1)
> 2 | f | 2 | INSERT INTO cp_test VALUES ($2, x)
> 1 | t | 1 | SELECT pg_stat_statements_reset()
>
> here, the intermediate CALL part is optimized away. or should I expect
> CALL ptest1($1) also in pg_stat_statements?

I would have guessed that ptest1() being called as part of ptest3()
should show up in the report if you use track = all, as all the nested
queries of a function, even if it is pure SQL, ought to show up. Now
note that ptest1() not showing up is not a new behavior, ~15 does the
same thing by missing it.
--
Michael