pgsql: Fix inconsistency in determining the timestamp of the db statfil

From: Amit Kapila <akapila(at)postgresql(dot)org>
To: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: pgsql: Fix inconsistency in determining the timestamp of the db statfil
Date: 2020-09-12 02:38:39
Message-ID: E1kGvR1-0007iM-A3@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Fix inconsistency in determining the timestamp of the db statfile.

We use the timestamp of the global statfile if we are not able to
determine it for a particular database in case the entry for that database
doesn't exist. However, we were using it even when the statfile is
corrupt.

As there is no user reported issue and it is not clear if there is any
impact of this on actual application so decided not to backpatch.

Reported-by: Amit Kapila
Author: Amit Kapila
Reviewed-by: Sawada Masahiko, Magnus Hagander and Alvaro Herrera
Discussion: https://postgr.es/m/CAA4eK1J3oTJKyVq6v7K4d3jD+vtnruG9fHRib6UuWWsrwAR6Aw@mail.gmail.com

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/03c7f1f37a1f3bb69e348f915296af2289257e89

Modified Files
--------------
src/backend/postmaster/pgstat.c | 17 +++++++++++------
1 file changed, 11 insertions(+), 6 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Peter Eisentraut 2020-09-12 18:36:29 pgsql: doc: Don't hide the "Up" link when it is the same as "Home"
Previous Message Amit Kapila 2020-09-12 02:24:45 pgsql: Remove unused function declaration in logicalproto.h.