| From: | Li Japin <japinli(at)hotmail(dot)com> |
|---|---|
| To: | Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com> |
| Cc: | "bharath(dot)rupireddyforpostgres(at)gmail(dot)com" <bharath(dot)rupireddyforpostgres(at)gmail(dot)com>, "pgsql-hackers(at)lists(dot)postgresql(dot)org" <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Terminate the idle sessions |
| Date: | 2020-08-18 02:12:51 |
| Message-ID: | ABEB9E5C-4753-4611-B1C1-5482C362F50D@hotmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Aug 18, 2020, at 9:19 AM, Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com<mailto:horikyota(dot)ntt(at)gmail(dot)com>> wrote:
The same already happens for idle_in_transaction_session_timeout and
we can use "ALTER ROLE/DATABASE SET" to dislable or loosen them, it's
a bit cumbersome, though. I don't think we should (at least
implicitly) disable those timeouts ad-hockerly for postgres_fdw.
+1.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2020-08-18 02:14:06 | Re: doc examples for pghandler |
| Previous Message | Kyotaro Horiguchi | 2020-08-18 01:19:44 | Re: Terminate the idle sessions |