| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Nikolay Samokhvalov <nikolay(at)samokhvalov(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #18094: max max_connections cannot be set |
| Date: | 2023-09-08 04:55:31 |
| Message-ID: | CAKFQuwaJ8d_1r-veqp6cnKYGypi+sSk9DScs-z6b-DM1WXR-DA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
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.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | PG Bug reporting form | 2023-09-08 06:28:13 | BUG #18098: Console code page issue Postgresql 14.7 |
| Previous Message | Nikolay Samokhvalov | 2023-09-08 04:25:20 | Re: BUG #18094: max max_connections cannot be set |