pgsql: Fix incorrect pg_stat_io output on 32-bit machines.

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: pgsql: Fix incorrect pg_stat_io output on 32-bit machines.
Date: 2024-09-06 15:58:30
Message-ID: E1smbLx-000QPF-UO@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Fix incorrect pg_stat_io output on 32-bit machines.

pg_stat_get_io() applied TimestampTzGetDatum twice to the
stat_reset_timestamp value. On 64-bit builds that's harmless because
TimestampTzGetDatum is a no-op, but on 32-bit builds it results in
displaying garbage in the stats_reset column of the pg_stat_io view.

Bug dates to commit a9c70b46d which introduced pg_stat_io, so
back-patch to v16 where that came in.

Bertrand Drouvot

Discussion: https://postgr.es/m/Ztrd+XcPTz1zorkg@ip-10-97-1-34.eu-west-3.compute.internal

Branch
------
REL_17_STABLE

Details
-------
https://git.postgresql.org/pg/commitdiff/e69030cb5178347d499bbc549213e950064564fa

Modified Files
--------------
src/backend/utils/adt/pgstatfuncs.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Jeff Davis 2024-09-06 20:48:27 pgsql: Remove lc_ctype_is_c().
Previous Message Peter Eisentraut 2024-09-06 09:40:00 pgsql: Remove useless unconstify