From: | Igor Neyman <ineyman(at)perceptron(dot)com> |
---|---|
To: | Wells Oliver <wells(dot)oliver(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Ron <ronljohnsonjr(at)gmail(dot)com>, "pgsql-admin(at)lists(dot)postgresql(dot)org" <pgsql-admin(at)lists(dot)postgresql(dot)org> |
Subject: | RE: Diagnosing a massive toast file |
Date: | 2019-08-05 18:31:45 |
Message-ID: | BN6PR1701MB1890A22C7037904467E7E491DADA0@BN6PR1701MB1890.namprd17.prod.outlook.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
From: Wells Oliver [mailto:wells(dot)oliver(at)gmail(dot)com]
Sent: Monday, August 05, 2019 1:43 PM
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Ron <ronljohnsonjr(at)gmail(dot)com>; pgsql-admin(at)lists(dot)postgresql(dot)org
Subject: Re: Diagnosing a massive toast file
Thanks, that was it exactly. PGAdmin session opened for a week. Argh. Gotta have some conversations with some folks.
Do you guys have any kind of regular monitoring in place to flag users who don't politely close their connections?
--
Wells Oliver
wells(dot)oliver(at)gmail(dot)com<mailto:wellsoliver(at)gmail(dot)com>
idle_in_transaction_session_timeout GUC is your friend.
Read on it in the docs.
Regards,
Igor Neyman
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2019-08-05 18:35:52 | Re: Diagnosing a massive toast file |
Previous Message | Avinash Kumar | 2019-08-05 17:48:28 | Re: Diagnosing a massive toast file |