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

From David G. Johnston
Subject Re: BUG #18094: max max_connections cannot be set
Date
Msg-id CAKFQuwaJ8d_1r-veqp6cnKYGypi+sSk9DScs-z6b-DM1WXR-DA@mail.gmail.com
Whole thread Raw
In response to Re: BUG #18094: max max_connections cannot be set  (Nikolay Samokhvalov <nikolay@samokhvalov.com>)
Responses Re: BUG #18094: max max_connections cannot be set
List pgsql-bugs
On Thu, Sep 7, 2023 at 9:25 PM Nikolay Samokhvalov <nikolay@samokhvalov.com> wrote:
nik=# select max_val from pg_settings where name = 'max_connections';
 max_val
---------
 262143
(1 row)

-- here is why

Glossed right over that...yeah, quite a few settings seem to have a max_val of "unsigned numeric", I'd be curious whether they all have some non-datatype maximum recognized during runtime that pg_settings is unable to see.

David J.

pgsql-bugs by date:

Previous
From: Nikolay Samokhvalov
Date:
Subject: Re: BUG #18094: max max_connections cannot be set
Next
From: PG Bug reporting form
Date:
Subject: BUG #18098: Console code page issue Postgresql 14.7