From: | Hans Sebastian <hnsbstn(at)gmail(dot)com> |
---|---|
To: | pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Old active connections? |
Date: | 2018-04-18 00:02:31 |
Message-ID: | CAMH0=P-VcGsBp+bHKr3j1BW=yqV7ff9b=_ZpO2+rqtVdmzBp1A@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
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.
Does anyone know the reasons they could be there? What could have caused
them being still active?
This has become an issue as we started getting "FATAL: remaining
connection slots are reserved for non-replication superuser connections"
Thanks,
-hans
From | Date | Subject | |
---|---|---|---|
Next Message | Adrian Klaver | 2018-04-18 00:08:41 | Re: Old active connections? |
Previous Message | Adrian Klaver | 2018-04-17 20:55:53 | Re: rehashing catalog cache id 14 for pg_opclass; 17 tups, 8 buckets |