From: Tom Lane <tgl@sss.pgh.pa.us>
To: nikolay@samokhvalov.com
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18094: max max_connections cannot be set
Date: Thu, 07 Sep 2023 12:25:21 -0400
Message-ID: <1716616.1694103921@sss.pgh.pa.us> (raw)
In-Reply-To: <18094-884970cc4c015d42@postgresql.org>
References: <18094-884970cc4c015d42@postgresql.org>
PG Bug reporting form <noreply@postgresql.org> writes:
> Expectation for max max_connections is 262143 in PG14, but it cannot be
> achieved:
Why do you think that's the maximum?
If you are looking at MAX_BACKENDS, that is not a limit on
max_connections. It is a limit on max_connections +
autovacuum_max_workers + 1 + max_worker_processes + max_wal_senders;
cf check_max_connections.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: tgl@sss.pgh.pa.us, nikolay@samokhvalov.com, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18094: max max_connections cannot be set
In-Reply-To: <1716616.1694103921@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox