From: | Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com> |
---|---|
To: | Masahiro Ikeda <ikedamsh(at)oss(dot)nttdata(dot)com>, torikoshia <torikoshia(at)oss(dot)nttdata(dot)com> |
Cc: | pgsql-hackers(at)postgresql(dot)org, andres(at)anarazel(dot)de, Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com> |
Subject: | Re: wal stats questions |
Date: | 2021-04-22 13:42:14 |
Message-ID: | 61993b3d-c609-7b32-fed2-1ec651c3bf4a@oss.nttdata.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 2021/04/21 18:31, Masahiro Ikeda wrote:
>> BTW, is it better to change PgStat_Counter from int64 to uint64 because> there aren't any counters with negative number?
On second thought, it's ok even if the counters like wal_records get overflowed.
Because they are always used to calculate the diff between the previous and
current counters. Even when the current counters are overflowed and
the previous ones are not, WalUsageAccumDiff() seems to return the right
diff of them. If this understanding is right, I'd withdraw my comment and
it's ok to use "long" type for those counters. Thought?
Regards,
--
Fujii Masao
Advanced Computing Technology Center
Research and Development Headquarters
NTT DATA CORPORATION
From | Date | Subject | |
---|---|---|---|
Next Message | Justin Pryzby | 2021-04-22 14:06:51 | Re: TRUNCATE on foreign table |
Previous Message | Tom Lane | 2021-04-22 13:29:46 | Re: INT64_FORMAT in translatable strings |