From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
---|---|
To: | Hans Sebastian <hnsbstn(at)gmail(dot)com>, pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: Old active connections? |
Date: | 2018-04-18 00:08:41 |
Message-ID: | 9e5e6abd-e7d0-17fe-06d3-edea494fe7d0@aklaver.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 04/17/2018 05:02 PM, Hans Sebastian wrote:
> Hello group,
>
> We run postgresql 10.3 for a python django app with gunicorn on nginx
> with django version 1.9.5.
>
> Recently, we started noticing there are many active connections from the
> django app server that are more than 1 week old still showing in
> pg_stat_activity.
>
> Even though the django server has been stopped (all processes killed),
> the active connections still persist. All of these connections are
> UPDATE queries that look pretty normal.
Are sure they are coming from Django?
>
> Does anyone know the reasons they could be there? What could have caused
> them being still active?
Can we see the data from pg_stat_activity for those queries?
>
> This has become an issue as we started getting "FATAL: remaining
> connection slots are reserved for non-replication superuser connections"
>
> Thanks,
> -hans
>
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | David G. Johnston | 2018-04-18 00:11:10 | Re: Old active connections? |
Previous Message | Hans Sebastian | 2018-04-18 00:02:31 | Old active connections? |