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

From Tom Lane
Subject Re: BUG #18094: max max_connections cannot be set
Date
Msg-id 1872108.1694181425@sss.pgh.pa.us
Whole thread Raw
In response to Re: BUG #18094: max max_connections cannot be set  ("David G. Johnston" <david.g.johnston@gmail.com>)
Responses Re: BUG #18094: max max_connections cannot be set
List pgsql-bugs
"David G. Johnston" <david.g.johnston@gmail.com> writes:
> 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.

Yeah, there are for example plenty of entries with max_val of INT_MAX,
but that doesn't necessarily mean you can set them that high.  The
max_val is *a* constraint, it's not the *only* constraint.

            regards, tom lane



pgsql-bugs by date:

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