Re: BUG #18094: max max_connections cannot be set - Mailing list pgsql-bugs

From Nikolay Samokhvalov
Subject Re: BUG #18094: max max_connections cannot be set
Date
Msg-id CANNMO+LUmkXtBR57on0a6qFtbJgjeoR56uan5Ru4BsW0TxbYjQ@mail.gmail.com
Whole thread Raw
In response to Re: BUG #18094: max max_connections cannot be set  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: BUG #18094: max max_connections cannot be set
List pgsql-bugs
nik=# select max_val from pg_settings where name = 'max_connections';
 max_val
---------
 262143
(1 row)

-- here is why

On Thu, Sep 7, 2023 at 09:25 Tom Lane <tgl@sss.pgh.pa.us> wrote:
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


pgsql-bugs by date:

Previous
From: PG Bug reporting form
Date:
Subject: BUG #18097: Immutable expression not allowed in generated at
Next
From: "David G. Johnston"
Date:
Subject: Re: BUG #18094: max max_connections cannot be set