From: | "Bee(dot)Lists" <bee(dot)lists(at)gmail(dot)com> |
---|---|
To: | "Peter J(dot) Holzer" <hjp-pgsql(at)hjp(dot)at> |
Cc: | pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: Persistent Connections |
Date: | 2020-06-24 17:55:00 |
Message-ID: | D0683AB3-7C3A-403B-BDAD-6E45B9B99D59@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
> On Jun 24, 2020, at 6:47 AM, Peter J. Holzer <hjp-pgsql(at)hjp(dot)at> wrote:
>
> The default is 100. What was your reason for reducing it to such a low
> value?
“PostgreSQL 9 High Availability” recommended core count * 3.
>
>> I’ve installed pg_stat_activity and pg_stat_statements.
>>
>> I access this server through a web app,
>
> So that's probably a handful connections already.
Looks like 5 queries.
As a comparison I have 37 queries asking for last login of a single user. No errors.
(I increased the max_connections yesterday)
>> and another client on two machines.
>
> Maybe two or more (depending on what the non-specified client does).
I’m running crons on two machines, Postico, web apps on both machines.
>> I also send queries through SSH on the LAN.
>
> And maybe some more connections.
Yep.
> I can see that this could easily reach 12 connections.
Yep. But I can’t see all this going over 12 when connections close. Hence the confusion and issue.
At least it’s a good thing I’m finding it’s not the gem alone.
Cheers, Bee
From | Date | Subject | |
---|---|---|---|
Next Message | paul.malm | 2020-06-24 18:42:55 | SQL delete and update at the same time |
Previous Message | Bee.Lists | 2020-06-24 17:45:21 | Re: Persistent Connections |