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

From: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
To: Kyotaro HORIGUCHI <horiguchi(dot)kyotaro(at)lab(dot)ntt(dot)co(dot)jp>
Cc: amit(dot)kapila16(at)gmail(dot)com, robertmhaas(at)gmail(dot)com, sk(at)zsrv(dot)org, vik(dot)fearing(at)2ndquadrant(dot)com, kommi(dot)haribabu(at)gmail(dot)com, peter(dot)eisentraut(at)2ndquadrant(dot)com, michael(at)paquier(dot)xyz, magnus(at)hagander(dot)net, masao(dot)fujii(at)gmail(dot)com, ashu(dot)coek88(at)gmail(dot)com, euler(at)timbira(dot)com(dot)br, pgsql-hackers(at)postgresql(dot)org, simon(at)2ndquadrant(dot)com, dpage(at)pgadmin(dot)org
Subject: Re: New function pg_stat_statements_reset_query() to reset statistics of a specific query
Date: 2018-12-19 11:14:59
Message-ID: 20181219111459.x7ti3ibr3t35pvtr@alvherre.pgsql
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2018-Dec-17, Kyotaro HORIGUCHI wrote:

> Although #1 seems cleaner to me, the fear of inadvertent removal
> of all queries with quite-common usage wins. So I vote for #4
> for now, supposing pg_stat_statements_reset(0, 0, 0) as
> all-clear.

Right -- also keeping in mind that 0 is the default value too, so the
old spelling of pg_stat_statements_reset() has the same behavior as
previously, ie., remove everything.

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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2018-12-19 11:15:18 Re: What to name the current heap after pluggable storage / what to rename?
Previous Message Peter Eisentraut 2018-12-19 11:02:38 Re: What to name the current heap after pluggable storage / what to rename?