From: | Li Japin <japinli(at)hotmail(dot)com> |
---|---|
To: | Adam Brusselback <adambrusselback(at)gmail(dot)com> |
Cc: | Michael Paquier <michael(at)paquier(dot)xyz>, "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Terminate the idle sessions |
Date: | 2020-06-11 13:57:24 |
Message-ID: | B7E5C3A6-A198-4878-8A5E-11DB7AEDEA74@hotmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Jun 10, 2020, at 10:27 PM, Adam Brusselback <adambrusselback(at)gmail(dot)com<mailto:adambrusselback(at)gmail(dot)com>> wrote:
My use case is, I have a primary application that connects to the DB, most users work through that (setting is useless for this scenario, app manages it's connections well enough). I also have a number of internal users who deal with data ingestion and connect to the DB directly to work, and those users sometimes leave query windows open for days accidentally. Generally not an issue, but would be nice to be able to time those connections out.
If there is no big impact, I think we might add it builtin.
Japin Li
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2020-06-11 14:00:51 | Re: Windows regress fails (latest HEAD) |
Previous Message | Peter Eisentraut | 2020-06-11 13:55:59 | Re: remove some STATUS_* symbols |