From: Tom Lane <tgl@sss.pgh.pa.us>
To: "David G. Johnston" <david.g.johnston@gmail.com>
cc: Nikolay Samokhvalov <nikolay@samokhvalov.com>,
        pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18094: max max_connections cannot be set
In-reply-to: 
 <CAKFQuwaJ8d_1r-veqp6cnKYGypi+sSk9DScs-z6b-DM1WXR-DA@mail.gmail.com>
References: <18094-884970cc4c015d42@postgresql.org>
 <1716616.1694103921@sss.pgh.pa.us>
 <CANNMO+LUmkXtBR57on0a6qFtbJgjeoR56uan5Ru4BsW0TxbYjQ@mail.gmail.com>
 <CAKFQuwaJ8d_1r-veqp6cnKYGypi+sSk9DScs-z6b-DM1WXR-DA@mail.gmail.com>
Comments: In-reply-to "David G. Johnston" <david.g.johnston@gmail.com>
	message dated "Thu, 07 Sep 2023 21:55:31 -0700"
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-ID: <1872107.1694181425.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Fri, 08 Sep 2023 09:57:05 -0400
Message-ID: <1872108.1694181425@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/1872108.1694181425%40sss.pgh.pa.us>
Precedence: bulk

"David G. Johnston" <david.g.johnston@gmail.com> writes:
> On Thu, Sep 7, 2023 at 9:25=E2=80=AFPM Nikolay Samokhvalov <nikolay@samo=
khvalov.com>
> wrote:
>> nik=3D# select max_val from pg_settings where name =3D '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 unabl=
e
> 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