Re: BUG #18343: Incorrect description in postgresql.conf for max_parallel_workers_per_gather
Christopher Kline <kline.christopher@gmail.com>
From: Christopher Kline <kline.christopher@gmail.com>
To: "David G. Johnston" <david.g.johnston@gmail.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, pgsql-bugs@lists.postgresql.org
Date: 2024-02-15T20:29:06Z
Lists: pgsql-bugs
Agreed. On Thu, Feb 15, 2024 at 2:42 PM David G. Johnston < david.g.johnston@gmail.com> wrote: > On Thu, Feb 15, 2024 at 10:31 AM Tom Lane <tgl@sss.pgh.pa.us> wrote: > >> Christopher Kline <kline.christopher@gmail.com> writes: >> > Thank you all for the clarification. I like David Johnston's suggestion >> of >> > # capped at max_parallel_workers >> > That clearly defines the constraint. >> >> I was thinking perhaps "# limited by max_parallel_workers" >> or something like that. "Capped at" isn't phraseology we >> use elsewhere. >> >> > "limited by" is indeed better IMO as well. > > David J. >
Commits
-
Doc: improve a couple of comments in postgresql.conf.sample.
- ed1b0ade703a 15.7 landed
- 88cbdcafdb74 12.19 landed
- 6686e9676c8f 14.12 landed
- 5c9f2f9398b4 17.0 landed
- 1a6dcfecab9f 16.3 landed
- 150ac3695f31 13.15 landed