Received: from malur.postgresql.org ([217.196.149.56])
	by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256)
	(Exim 4.89)
	(envelope-from <pgsql-admin-owner+archive@lists.postgresql.org>)
	id 1huhqT-0005w6-62
	for pgsql-admin@arkaria.postgresql.org; Mon, 05 Aug 2019 18:36:33 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.89)
	(envelope-from <pgsql-admin-owner+archive@lists.postgresql.org>)
	id 1huhqS-0003FN-2k
	for pgsql-admin@arkaria.postgresql.org; Mon, 05 Aug 2019 18:36:32 +0000
Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29])
	by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256)
	(Exim 4.89)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1huhps-0006cb-NM
	for pgsql-admin@lists.postgresql.org; Mon, 05 Aug 2019 18:35:56 +0000
Received: from sss.pgh.pa.us ([66.207.139.130])
	by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256)
	(Exim 4.89)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1huhpq-0000ff-JS
	for pgsql-admin@lists.postgresql.org; Mon, 05 Aug 2019 18:35:56 +0000
Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1])
	by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id x75IZqiC030509;
	Mon, 5 Aug 2019 14:35:52 -0400
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Igor Neyman <ineyman@perceptron.com>
cc: Wells Oliver <wells.oliver@gmail.com>, Ron <ronljohnsonjr@gmail.com>,
        "pgsql-admin@lists.postgresql.org" <pgsql-admin@lists.postgresql.org>
Subject: Re: Diagnosing a massive toast file
In-reply-to: 
 <BN6PR1701MB1890A22C7037904467E7E491DADA0@BN6PR1701MB1890.namprd17.prod.outlook.com>
References: 
 <CAOC+FBUPopsKh5wV5VC-CHCnVirtTghhwNwEtSD2ZaCZbXwOFg@mail.gmail.com>
 <3da6ffe8-28ef-fb9a-e6e8-1f0d243cc8e9@gmail.com>
 <CAOC+FBX1arTzF+_hx2WMsnOoF95gnnMZtNNkPUG+OKAERpisJg@mail.gmail.com>
 <6018.1565023741@sss.pgh.pa.us>
 <CAOC+FBWsvJJawBNBdan1n2pbQYWdZLvCF=2nUZq2hK0OHryXfg@mail.gmail.com>
 <CAOC+FBXyYOE1+90qNDMJ_0W6F6pPxdKTEYP4HG2xHgT9KzbE=w@mail.gmail.com>
 <27376.1565025867@sss.pgh.pa.us>
 <CAOC+FBUmpiQtmwn_WNyE-jCZ57h7OebqgBGtpLYFwqBCdkoSaQ@mail.gmail.com>
 <BN6PR1701MB1890A22C7037904467E7E491DADA0@BN6PR1701MB1890.namprd17.prod.outlook.com>
Comments: In-reply-to Igor Neyman <ineyman@perceptron.com>
	message dated "Mon, 05 Aug 2019 18:31:45 -0000"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <30507.1565030152.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Mon, 05 Aug 2019 14:35:52 -0400
Message-ID: <30508.1565030152@sss.pgh.pa.us>
List-Id: <pgsql-admin.lists.postgresql.org>
List-Help: <https://lists.postgresql.org/manage/>
List-Subscribe: <https://lists.postgresql.org/manage/>
List-Post: <mailto:pgsql-admin@lists.postgresql.org>
List-Owner: <mailto:pgsql-admin-owner@lists.postgresql.org>
List-Archive: <https://www.postgresql.org/list/pgsql-admin>
Precedence: bulk

Igor Neyman <ineyman@perceptron.com> writes:
> From: Wells Oliver [mailto:wells.oliver@gmail.com]
>> Do you guys have any kind of regular monitoring in place to flag users =
who don't politely close their connections?

> idle_in_transaction_session_timeout GUC is your friend.

Good idea, though it's only been around since 9.6.

Also, if you just want to monitor rather than impose a hard limit,
I imagine you can get Nagios to watch for this.

			regards, tom lane