Uncommented GUC in postgresql.conf.sample

From: Daniel Gustafsson <daniel(at)yesql(dot)se>
To: Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Uncommented GUC in postgresql.conf.sample
Date: 2025-11-14 14:06:44
Message-ID: 19727040-3EE4-4719-AF4F-2548544113D7@yesql.se
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

When looking at the nearby suggestion to add deprecation comment for md5 in the
.conf.sample, I happened to notice that autovacuum_worker_slots isn't commented
out it the sample file.

AFAIK all GUCs in the sample file should be set to their defaults and left
commented out. The attached does that for autovacuum_worker_slots and adds a
trivial test to test_misc to catch it (and modifies the existing test which
would've caught it). Or is there a case for leaving uncommented?

--
Daniel Gustafsson

Attachment Content-Type Size
v1-0001-Make-sure-all-GUCs-in-.conf.sample-are-commented-.patch application/octet-stream 2.3 KB

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message David G. Johnston 2025-11-14 14:25:54 Re: Document NULL
Previous Message Andres Freund 2025-11-14 14:01:06 Re: BUG #19095: Test if function exit() is used fail when linked static