Home > mailing lists

pg_stat_database update stats_reset only by pg_stat_reset - Mailing list pgsql-hackers

From	张连壮
Subject	pg_stat_database update stats_reset only by pg_stat_reset
Date	May 13, 2019 10:30:54
Msg-id	CALerpYrJbDZ258WxYkZPrYpLDom==25NHVSpXkkPW0MML2-wtA@mail.gmail.com Whole thread Raw
Responses	Re: pg_stat_database update stats_reset only by pg_stat_reset (张连壮 <lianzhuangzhang@gmail.com>)
List	pgsql-hackers

pg_stat_reset_single_table_counters/pg_stat_reset_single_function_counters only update pg_stat_database column stats_reset.

stat_reset shuld update when all the column is reset.

sample:

drop database if exists lzzhang_db;

create database lzzhang_db;

\c lzzhang_db

create table lzzhang_tab(id int);

insert into lzzhang_tab values(1);

select tup_fetched, stats_reset from pg_stat_database where datname='lzzhang_db';

select pg_sleep(1);

select pg_stat_reset_single_table_counters('lzzhang_tab'::regclass::oid);

select tup_fetched, stats_reset from pg_stat_database where datname='lzzhang_db';

result:

tup_fetched | stats_reset

-------------+-------------------------------

514 | 2019-05-12 03:22:55.702753+08

(1 row)

tup_fetched | stats_reset

-------------+-------------------------------

710 | 2019-05-12 03:22:56.729336+08

(1 row)

tup_fetched is not reset but stats_reset is reset.

From: Michael Paquier
Date: 13 May 2019, 10:14:27
Subject: Re: pglz performance

From: Andrew Gierth
Date: 13 May 2019, 10:42:56
Subject: Re: SQL-spec incompatibilities in similar_escape() and related stuff