pgsql: Fix enum value visibility for data_checksums

From: Daniel Gustafsson <dgustafsson(at)postgresql(dot)org>
To: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: pgsql: Fix enum value visibility for data_checksums
Date: 2026-09-14 13:34:14
Message-ID: E1x66p4-00000000I6R-2iss@gemulon.postgresql.org
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Fix enum value visibility for data_checksums

When the data_checksums GUC was changed into an enum the enum values
were all incorrectly marked as hidden, which made pg_settings report
an empty array. Fix by setting all as visible as they should be.

Found by Noah using AI assisted review with GPT. Backpatch to v19
where the GUC was changed in the online checksums feature.

Reported-by: Noah Misch <noah(at)leadboat(dot)com>
Discussion: https://postgr.es/m/E15AC050-C4B5-488D-BB2D-3C7AC9F89EA8@yesql.se
Backpatch-through: 19

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/3954d740c48750731d4a17766f3cb7b450856ed1

Modified Files
--------------
src/backend/utils/misc/guc_tables.c | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Nathan Bossart 2026-09-14 14:16:41 pgsql: Describe special values in more GUC descriptions.
Previous Message Alexander Korotkov 2026-09-14 11:50:05 pgsql: Fix timeout overflow in WAIT FOR LSN