Re: BUG #18094: max max_connections cannot be set

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: nikolay(at)samokhvalov(dot)com
Cc: pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #18094: max max_connections cannot be set
Date: 2023-09-07 16:25:21
Message-ID: 1716616.1694103921@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

PG Bug reporting form <noreply(at)postgresql(dot)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

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message PG Bug reporting form 2023-09-07 16:44:13 BUG #18095: Unintended non-SSL connection attempt by psql cli command after a failed password authentication
Previous Message David G. Johnston 2023-09-07 16:07:53 Re: BUG #18094: max max_connections cannot be set