Re: Resetting spilled txn statistics in pg_stat_replication - Mailing list pgsql-hackers

From Fujii Masao
Subject Re: Resetting spilled txn statistics in pg_stat_replication
Date
Msg-id 316a6dc4-d2ce-0083-7042-ce4854ccb6b5@oss.nttdata.com
Whole thread Raw
In response to Re: Resetting spilled txn statistics in pg_stat_replication  (Kyotaro Horiguchi <horikyota.ntt@gmail.com>)
Responses Re: Resetting spilled txn statistics in pg_stat_replication  (Masahiko Sawada <masahiko.sawada@2ndquadrant.com>)
Re: Resetting spilled txn statistics in pg_stat_replication  (Amit Kapila <amit.kapila16@gmail.com>)
List pgsql-hackers

On 2020/06/02 16:00, Kyotaro Horiguchi wrote:
> At Tue, 2 Jun 2020 15:17:36 +0900, Masahiko Sawada <masahiko.sawada@2ndquadrant.com> wrote in
>> Hi all,
>>
>> Tracking of spilled transactions has been introduced to PG13. These
>> new statistics values, spill_txns, spill_count, and spill_bytes, are
>> cumulative total values unlike other statistics values in
>> pg_stat_replication.

Basically I don't think it's good design to mix dynamic and collected
stats in one view. It might be better to separate them into different
new stats view. It's too late to add new stats view for v13, though....

Regards,

-- 
Fujii Masao
Advanced Computing Technology Center
Research and Development Headquarters
NTT DATA CORPORATION



pgsql-hackers by date:

Previous
From: Masahiko Sawada
Date:
Subject: Re: More tests with USING INDEX replident and dropped indexes
Next
From: Fujii Masao
Date:
Subject: Re: elog(DEBUG2 in SpinLocked section.