Re: New function pg_stat_statements_reset_query() to reset statistics of a specific query

Alvaro Herrera <alvherre@2ndquadrant.com>

From: Alvaro Herrera <alvherre@2ndquadrant.com>
To: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Cc: Robert Haas <robertmhaas@gmail.com>, Amit Kapila <amit.kapila16@gmail.com>, Sergei Kornilov <sk@zsrv.org>, Vik Fearing <vik.fearing@2ndquadrant.com>, Haribabu Kommi <kommi.haribabu@gmail.com>, Michael Paquier <michael@paquier.xyz>, Magnus Hagander <magnus@hagander.net>, Fujii Masao <masao.fujii@gmail.com>, Ashutosh Sharma <ashu.coek88@gmail.com>, Euler Taveira de Oliveira <euler@timbira.com.br>, "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>, Simon Riggs <simon@2ndquadrant.com>, Dave Page <dpage@pgadmin.org>
Date: 2018-12-16T14:28:46Z
Lists: pgsql-hackers
On 2018-Dec-15, Peter Eisentraut wrote:

> An example:
> 
> select pg_stat_statements_reset(
> 10,
> (select min(oid) from pg_database where datname like 'test%'),
> 1234);
> 
> (This is obviously a weird example, but it illustrates the
> language-theoretic point.)

This is not at all weird.  Lack of clarity on this point is the reason
that spawned this whole sub-thread, because a reset was removing data
that was not about the query that was intended.

-- 
Álvaro Herrera                https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services


Commits

  1. Extend pg_stat_statements_reset to reset statistics specific to a

  2. Default monitoring roles