From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
Cc: | Nikolay Samokhvalov <nikolay(at)samokhvalov(dot)com>, pgsql-bugs(at)lists(dot)postgresql(dot)org |
Subject: | Re: BUG #18094: max max_connections cannot be set |
Date: | 2023-09-08 13:57:05 |
Message-ID: | 1872108.1694181425@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
"David G. Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> writes:
> On Thu, Sep 7, 2023 at 9:25 PM Nikolay Samokhvalov <nikolay(at)samokhvalov(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Nikolay Samokhvalov | 2023-09-08 14:04:21 | Re: BUG #18094: max max_connections cannot be set |
Previous Message | Gokul Krishnan | 2023-09-08 10:21:42 | Re: BUG #18098: Console code page issue Postgresql 14.7 |