BUG #18046: stats collection behaviour change is affecting the usability of information.

From: PG Bug reporting form <noreply(at)postgresql(dot)org>
To: pgsql-bugs(at)lists(dot)postgresql(dot)org
Cc: jobinau(at)gmail(dot)com
Subject: BUG #18046: stats collection behaviour change is affecting the usability of information.
Date: 2023-08-01 16:32:46
Message-ID: 18046-9263842a9ec688e0@postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

The following bug has been logged on the website:

Bug reference: 18046
Logged by: Jobin Augustine
Email address: jobinau(at)gmail(dot)com
PostgreSQL version: 15.3
Operating system: CentOS/RHEL
Description:

After stats collection changes in PG 15, The behaviour stats_reset
information is changed. which is adversely affecting the usability of data
presented in the view.
```
select stats_reset from pg_stat_database;
```
Before PG15, stats_reset was always populated so that the user knows the
cumulative values presented are of how many days.
But unfortunately, PG 15 keeps it null unless there is an explicit reset
(pg_stat_reset). The value goes again null if there is a reset due to a
crash.
So on a regular system, the User can't understand the cumulative values
presented in the view.

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Amit Kapila 2023-08-02 05:20:28 Re: DROP DATABASE deadlocks with logical replication worker in PG 15.1
Previous Message Zechman, Derek S 2023-08-01 16:29:37 RE: pg_hba.conf "authentication file token too long, skipping"