On Mon, Aug 10, 2020 at 4:09 PM Magnus Hagander <magnus@hagander.net> wrote:
> Would it even solve the problem for them? pg_stat_statements collects aggregate stats and not a view of what's
happeningright now -- so it'd be mixing two different types of values. And it would get worse if the same thing is
executedmultiple times concurrently.
True. You could find that you have a queryId that had already been
evicted from the table.
I think it's better to look for a more direct solution to this problem.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
