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 1icV89-0006ew-Rp for pgsql-bugs@arkaria.postgresql.org; Wed, 04 Dec 2019 13:55:49 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1icV88-00019Y-Ln for pgsql-bugs@arkaria.postgresql.org; Wed, 04 Dec 2019 13:55:48 +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 ) id 1icV88-00018x-DD for pgsql-bugs@lists.postgresql.org; Wed, 04 Dec 2019 13:55:48 +0000 Received: from mail-wr1-x443.google.com ([2a00:1450:4864:20::443]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1icV81-0007tF-DJ for pgsql-bugs@lists.postgresql.org; Wed, 04 Dec 2019 13:55:48 +0000 Received: by mail-wr1-x443.google.com with SMTP id y11so8699696wrt.6 for ; Wed, 04 Dec 2019 05:55:40 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=2ndquadrant-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to; bh=dSOBPgW/jjuEOWugiL8Tx+Sl090GIunSLjNgm5t9qtQ=; b=humj3b2dkHW3vFwj0h4fMfLFGxJf8HtU7l+JyRjc4+7qPGKRPTwqKTSlfEvexURLxM pFeAjuUR/YmIRxCNh8ZxaCVPNydjdu47vF8FXfVDIUvLnHDxFJ4PUuuOZeBuVt773Tm1 zwM8vbKqXu+g1rwqwl/O81ULmlki82X5UB3mD/A3OO3Xu/y/xT2hQc5NpLmcPer6CRBN czXsFe5jT8VEniy1kqRU5HkX0OraEzV5LoJvBEqflLY0xx2Xie15ygeqk4YqU8Xk2VZ3 xsa5GJkIcQAlBZsI1ZW0QX2wisIZUv9ll81IsIsixvoC1u3ZpZ0WHHNJ0o5ss+hEaYaA cRZA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=dSOBPgW/jjuEOWugiL8Tx+Sl090GIunSLjNgm5t9qtQ=; b=Z0vR73QKmvQXxsc6BaMnz+6f5tdvyURGT105D65Qa2O22kXAobv0RBPcoma8Qo4tYU Ar92gsbzA9QdoACA27i8Xg8jkEaVIdeXZ8IX5bmWAMsye1V7UoESVW6rp3NbVc9On5Sy /ZEp1oced0Vu9u2FyukPaMr2OVQVMrhMuXFRZcyuRoPlXdUb4U+b8SAM4oOJNDvXEMGv 2HHmR5BuqS5Np9t7Ma251Kg9Z5nrHDsK7Ceet/LqslIv+pGLnInHiXTT/8izLgdnCojs GVCYYcZJzjCRVvph3tADLXisOKmC8GA0dW+arcDTdMHQo5eSjsgp2m72BWJdiEunngVC 0zHw== X-Gm-Message-State: APjAAAUX+YQJ1Cg//qjkk4hOWLs+8rU2dThQfj6LkfJRIcz6qSaPTI3y LvZo00eOL55GSWmlKa3w7+GDgA== X-Google-Smtp-Source: APXvYqwzxxxI9j3XVUSQvyMp6j0PR3ka7ffTW8b1TYg1jU44RHzQKHojw98ESBDE70Iy3+hjoRJ/Xw== X-Received: by 2002:a5d:534b:: with SMTP id t11mr4279649wrv.120.1575467740428; Wed, 04 Dec 2019 05:55:40 -0800 (PST) Received: from localhost (static-84-42-175-93.net.upcbroadband.cz. [84.42.175.93]) by smtp.gmail.com with ESMTPSA id t81sm7183840wmg.6.2019.12.04.05.55.38 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 04 Dec 2019 05:55:38 -0800 (PST) Date: Wed, 4 Dec 2019 14:55:36 +0100 From: Tomas Vondra To: Tom Lane Cc: MOHAN KUMAR DORAIRAJ , Mahendra Singh , pgsql-bugs@lists.postgresql.org Subject: Re: BUG #16145: Not able to terminate active session Message-ID: <20191204135536.3drofgso4sut5enj@development> References: <20191203141147.lofq3gwn3u3vkkze@development> <20191203155458.jaauye67db32omk4@development> <20191203163818.vi4ocgg7mfo53fbz@development> <13041.1575465012@sss.pgh.pa.us> <14093.1575466474@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: <14093.1575466474@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On Wed, Dec 04, 2019 at 08:34:34AM -0500, Tom Lane wrote: >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. > Yeah, having some CHECK_FOR_INTERRUPT calls in the code might help (there's a single place with this macro, but it only happens after an error). The question is whether the OCIStmtExecute actually returns from time to time, of it if gets stuck. >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.) > I think the right place to file the issue is here: https://github.com/laurenz/oracle_fdw regards -- Tomas Vondra http://www.2ndQuadrant.com PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services