Re: Resetting spilled txn statistics in pg_stat_replication

From: Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com>
To: Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>, masahiko(dot)sawada(at)2ndquadrant(dot)com
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Resetting spilled txn statistics in pg_stat_replication
Date: 2020-06-02 08:22:26
Message-ID: 316a6dc4-d2ce-0083-7042-ce4854ccb6b5@oss.nttdata.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2020/06/02 16:00, Kyotaro Horiguchi wrote:
> At Tue, 2 Jun 2020 15:17:36 +0900, Masahiko Sawada <masahiko(dot)sawada(at)2ndquadrant(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Fujii Masao 2020-06-02 08:35:48 Re: elog(DEBUG2 in SpinLocked section.
Previous Message Masahiko Sawada 2020-06-02 07:46:55 Re: More tests with USING INDEX replident and dropped indexes