Re: BUG #18094: max max_connections cannot be set
От | Tom Lane |
---|---|
Тема | Re: BUG #18094: max max_connections cannot be set |
Дата | |
Msg-id | 1872108.1694181425@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: BUG #18094: max max_connections cannot be set ("David G. Johnston" <david.g.johnston@gmail.com>) |
Ответы |
Re: BUG #18094: max max_connections cannot be set
|
Список | 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 по дате отправления: