Re: Stale comment in guc.h; publish listing of setting sources?
Michael Paquier <michael@paquier.xyz>
From: Michael Paquier <michael@paquier.xyz>
To: "David G. Johnston" <david.g.johnston@gmail.com>
Cc: pgsql-hackers@lists.postgresql.org
Date: 2025-09-10T23:48:47Z
Lists: pgsql-hackers
On Wed, Sep 10, 2025 at 01:02:46PM -0700, David G. Johnston wrote: > * NB: see GucSource_Names in guc.c if you change this. > > The constant was moved to guc_tables.c I would just remove the file reference. Knowing that GucSource_Names matters is enough to grep for it. Documenting its location does not matter. > Also, these seem like they should be documented for pg_settings.source > > Per recent complaint: > https://www.postgresql.org/message-id/04f101dc2288$121b2de0$365189a0$@msym.fr Yeah, why not. Listing all of them GucSource_Names directly in the docs may help if that clarifies things regarding some of the values. The last additions in the list were 9475db3a4eb5 and f480e2944985, if my grepping gets it right, pointing that this has a low risk of rotting when a new one is added to the code, and forgotten in the docs. -- Michael
Commits
-
Fix incorrect file reference in guc.h
- 93b6b4663362 16.11 landed
- f918916cdbed 17.7 landed
- e9682da59440 18.0 landed
- c88ce73eda2e 19 (unreleased) landed