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 ) id 1icUnl-0005og-RP for pgsql-bugs@arkaria.postgresql.org; Wed, 04 Dec 2019 13:34:45 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1icUnk-0005Px-ME for pgsql-bugs@arkaria.postgresql.org; Wed, 04 Dec 2019 13:34:44 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1icUnk-0005Pi-Ab for pgsql-bugs@lists.postgresql.org; Wed, 04 Dec 2019 13:34:44 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1icUnh-0000EA-SP for pgsql-bugs@lists.postgresql.org; Wed, 04 Dec 2019 13:34:43 +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 xB4DYYCa014094; Wed, 4 Dec 2019 08:34:34 -0500 From: Tom Lane To: MOHAN KUMAR DORAIRAJ cc: Mahendra Singh , Tomas Vondra , pgsql-bugs@lists.postgresql.org Subject: Re: BUG #16145: Not able to terminate active session In-reply-to: References: <16145-d617c77db801047b@postgresql.org> <20191203141147.lofq3gwn3u3vkkze@development> <20191203155458.jaauye67db32omk4@development> <20191203163818.vi4ocgg7mfo53fbz@development> <13041.1575465012@sss.pgh.pa.us> Comments: In-reply-to MOHAN KUMAR DORAIRAJ message dated "Wed, 04 Dec 2019 21:22:03 +0800" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <14092.1575466474.1@sss.pgh.pa.us> Date: Wed, 04 Dec 2019 08:34:34 -0500 Message-ID: <14093.1575466474@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk MOHAN KUMAR DORAIRAJ writes: > Is there any other alternative option available.? Well, why is it that your session is sitting waiting for input from the Oracle server? That doesn't seem like a condition that ought to be persistent, most of the time. Perhaps redesigning your queries against that foreign server would help. Also, I do recommend asking the Oracle FDW authors about this. It's possible that adding some CHECK_FOR_INTERRUPT calls in that FDW would ameliorate things. (I don't know where to file issues about oracle_fdw, but it's not this list.) regards, tom lane