Re: BUG #18094: max max_connections cannot be set

From: Nikolay Samokhvalov <nikolay(at)samokhvalov(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #18094: max max_connections cannot be set
Date: 2023-09-08 04:25:20
Message-ID: CANNMO+LUmkXtBR57on0a6qFtbJgjeoR56uan5Ru4BsW0TxbYjQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> 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 David G. Johnston 2023-09-08 04:55:31 Re: BUG #18094: max max_connections cannot be set
Previous Message PG Bug reporting form 2023-09-08 03:47:49 BUG #18097: Immutable expression not allowed in generated at