| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | 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-07 16:07:53 |
| Message-ID: | CAKFQuwZv1Rz6gdkM77fA5TaPM3BoboFV0qxBLxV2DPqjJ0-nWQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Thu, Sep 7, 2023 at 9:03 AM PG Bug reporting form <noreply(at)postgresql(dot)org>
wrote:
> The following bug has been logged on the website:
>
> Bug reference: 18094
> Logged by: Nikolay Samokhvalov
> Email address: nikolay(at)samokhvalov(dot)com
> PostgreSQL version: 15.4
> Operating system: MacOS
> Description:
>
> (apologies for double posting, please disregard the previous message)
>
> Expectation for max max_connections is 262143 in PG14
>
I don't recall, nor find in the two official places such a thing could
reasonably be listed, there being a number documented as the limit for this.
Partially I suppose because the natural limit, whatever it may be, is
higher than any reasonable choice a DBA might supply.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2023-09-07 16:25:21 | Re: BUG #18094: max max_connections cannot be set |
| Previous Message | PG Bug reporting form | 2023-09-07 15:56:33 | BUG #18094: max max_connections cannot be set |