Horton

Re: Support reset of Shared objects statistics in "pg_stat_reset" function

Dilip Kumar <dilipbalaut@gmail.com>

View thread View on postgr.es
From: Dilip Kumar <dilipbalaut@gmail.com>
To: Mahendra Singh Thalor <mahi6run@gmail.com>
Cc: Sadhuprasad Patro <b.sadhu@gmail.com>, Himanshu Upadhyaya <upadhyaya.himanshu@gmail.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2021-08-11T03:47:16Z
Lists: pgsql-hackers 
On Tue, Aug 10, 2021 at 10:49 PM Mahendra Singh Thalor
<mahi6run@gmail.com> wrote:

> I checked this and found that we already have one process "stats
> collector" and in v02 patch, we are sending requests to collect stats
> two times. I don't know how costly one call is but I feel that we can
> avoid the 2nd call by keeping handling of the shared tables into
> pgstat_recv_resetcounter.
>

I think let's not make the stat collector aware of what we want to
achieve, so the stat collector will only reset for what we have asked
for and let the caller or the signal sender decide what they want to
do.

-- 
Regards,
Dilip Kumar
EnterpriseDB: http://www.enterprisedb.com

Commits

  1. Enhance pg_stat_reset_single_table_counters function.