Re: postgresql.conf.sample ordering for IO, worker related GUCs
Andres Freund <andres@anarazel.de>
From: Andres Freund <andres@anarazel.de>
To: pgsql-hackers@lists.postgresql.org, Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-hackers@postgresql.org
Date: 2025-01-31T02:24:05Z
Lists: pgsql-hackers
Hi On January 30, 2025 8:55:36 PM EST, Tom Lane <tgl@sss.pgh.pa.us> wrote: >Andres Freund <andres@anarazel.de> writes: >> While working on polishing the AIO patchset, I was trying to figure out where >> to fit the new GUCs. So far I had a new "top-level" #--- style section named >> "WIP AIO GUC docs" which I suspect you all won't let me get away with. >> There is an existing (sub-)section which already has a few related GUCs and >> could fit AIO related ones. > >I think the normal theory for postgresql.conf.sample is that it should >match the organization of config.sgml. What are you planning there? Pretty much the same. I.e. I'm thinking that the worker stuff should be it's own subsection and that the existing IO parameters should be moved to either a new subsection or a new top level section. But I'm wondering how others think it should be structured... Andres -- Sent from my Android device with K-9 Mail. Please excuse my brevity.
Commits
-
config: Rename "Asynchronous Behavior" to "I/O"
- 4dd09a1d415d 18.0 landed
-
config: Split "Worker Processes" out of "Asynchronous Behavior"
- 740766d37cdf 18.0 landed