| From: | Oygun Josef <josef(dot)oygun(at)scania(dot)com> |
|---|---|
| To: | "pgadmin-support(at)postgresql(dot)org" <pgadmin-support(at)postgresql(dot)org>, "pgadmin-support(at)lists(dot)postgresql(dot)org" <pgadmin-support(at)lists(dot)postgresql(dot)org>, "pgsql-jdbc(at)postgresql(dot)org" <pgsql-jdbc(at)postgresql(dot)org>, "pgsql-sql(at)postgresql(dot)org" <pgsql-sql(at)postgresql(dot)org>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Idle connections / sessions |
| Date: | 2018-12-12 09:37:30 |
| Message-ID: | HE1PR0402MB3625F9C2E5735459D63DA27C93A70@HE1PR0402MB3625.eurprd04.prod.outlook.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgadmin-support pgsql-general pgsql-jdbc pgsql-sql |
Hi,
Is it possible to terminate idle connections/sessions automatically through a timeout in AWS or do I need to run a periodical cron job for this?
Postgres version: 9.6.6
Instance: db.t2.micro
RAM : 1GB
We are running a microservice architecture using docker with kubernetes and I can see that every pod on every node that has connected to the DB still has a idle connection as long as the node is still active even.
It is both PGAdmin and the PostgreSQL JDBC Driver that leaves open idle connections.
Josef Oygun
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Kellerer | 2018-12-12 09:55:22 | Re: Idle connections / sessions |
| Previous Message | Khushboo Vashi | 2018-12-12 08:55:44 | Re: Minor bug in pgAdmin |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Kellerer | 2018-12-12 09:55:22 | Re: Idle connections / sessions |
| Previous Message | Mike Lissner | 2018-12-12 08:15:08 | Re: Errors with schema migration and logical replication — expected? |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Kellerer | 2018-12-12 09:55:22 | Re: Idle connections / sessions |
| Previous Message | Sehrope Sarkuni | 2018-12-11 16:04:20 | [pgjdbc/pgjdbc] 9b45e7: refactor: Clean up loading of reading of keydata f... |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | agharta82@gmail.com | 2018-12-12 09:49:46 | Re: Group by column alias where same-column-name already exists |
| Previous Message | Voillequin, Jean-Marc | 2018-12-11 16:51:47 | RE: Group by column alias where same-column-name already exists |