diff options
author | Michael Paquier <michael@paquier.xyz> | 2022-11-08 10:50:09 +0900 |
---|---|---|
committer | Michael Paquier <michael@paquier.xyz> | 2022-11-08 10:50:09 +0900 |
commit | d7744d50a5394db8d973d1cfa034ed6640aec13c (patch) | |
tree | 4f6e0c025c2703890a2d64899ab44601063dad6c /src/backend/access/transam/xlog.c | |
parent | 1613de8bc34b4977d0186b56ef5a00ef8058a74a (diff) | |
download | postgresql-d7744d50a5394db8d973d1cfa034ed6640aec13c.tar.gz postgresql-d7744d50a5394db8d973d1cfa034ed6640aec13c.zip |
Fix initialization of pg_stat_get_lastscan()
A NULL result should be reported when a stats timestamp is set to 0, but
c037471 missed that, leading to a confusing timestamp value after for
example a DML on a freshly-created relation with no scans done on it
yet.
This impacted the following attributes for two system views:
- pg_stat_all_tables.last_idx_scan
- pg_stat_all_tables.last_seq_scan
- pg_stat_all_indexes.last_idx_scan
Reported-by: Robert Treat
Analyzed-by: Peter Eisentraut
Author: Dave Page
Discussion: https://postgr.es/m/CABV9wwPzMfSaz3EfKXXDxKmMprbxwF5r6WPuxqA=5mzRUqfTGg@mail.gmail.com
Diffstat (limited to 'src/backend/access/transam/xlog.c')
0 files changed, 0 insertions, 0 deletions