From: | "Bee(dot)Lists" <bee(dot)lists(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Submit Postgresql Novice <pgsql-novice(at)postgresql(dot)org> |
Subject: | Re: Connections Increasing Slowly |
Date: | 2020-06-23 17:25:11 |
Message-ID: | 6757F40E-9003-4A02-B126-F0E6893866FD@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-novice |
On Jun 22, 2020, at 10:07 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> Hmm. If the client thinks the server dropped the connection, but the
> server thinks the connection is still live, that smells strongly of
> network-level disconnects. Does the client let the connection sit idle
> for more than a minute or two at a time? If so I'd bet that some firewall
> in between is deciding that the connection is dead and dropping it.
> Again, setting the server's tcp_keepalives_* settings could help fix that,
> by ensuring that the network connection sees some traffic regularly.
>
> regards, tom lane
Hi Tom. Some more testing.
Turned off firewalld, same issue. Some notes:
I have one simple query that’s in my activity (currently active) that’s in there 5 times. It should have closed very quickly, yet there’s 5 instances idling. I have two other queries, that should have operated quickly, then closed, but they are idling.
tcp_keepalives* are around 3.
Any idea where to look now?
I’ve set my max_connections to 12 (4 cores * 3).
Cheers, Bee
From | Date | Subject | |
---|---|---|---|
Next Message | David G. Johnston | 2020-06-23 17:31:30 | Re: Connections Increasing Slowly |
Previous Message | David Harrigan | 2020-06-23 08:36:51 | Stored Procedure Multiple Result Sets |