Date: Wed, 19 Jun 2024 14:24:08 -0500
From: Nathan Bossart <nathandbossart@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-hackers@postgresql.org
Subject: Re: remove check hooks for GUCs that contribute to MaxBackends
Message-ID: <ZnMwWCnhmIEw31BW@nathan>
References: <ZnMr2k-Nk5vj7T7H@nathan>
 <148099.1718824456@sss.pgh.pa.us>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <148099.1718824456@sss.pgh.pa.us>
Archived-At: <https://www.postgresql.org/message-id/ZnMwWCnhmIEw31BW%40nathan>
Precedence: bulk

On Wed, Jun 19, 2024 at 03:14:16PM -0400, Tom Lane wrote:
> Nathan Bossart <nathandbossart@gmail.com> writes:
>> The attached patch removes these hooks and enhances the error message to
>> look like this:
> 
>> 	FATAL:  too many backends configured
>> 	DETAIL:  "max_connections" (262100) plus "autovacuum_max_workers" (3) plus "max_worker_processes" (8) plus "max_wal_senders" (10000) must be less than 262142.
> 
> BTW, I suggest writing it as "too many server processes configured",
> or perhaps "too many server processes required".  "Backend" is too
> much of an insider term.

Will do, thanks for reviewing.

-- 
nathan