From: | Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | MOHAN KUMAR DORAIRAJ <mohankumar(dot)dorairaj(at)globalfoundries(dot)com>, Mahendra Singh <mahi6run(at)gmail(dot)com>, pgsql-bugs(at)lists(dot)postgresql(dot)org |
Subject: | Re: BUG #16145: Not able to terminate active session |
Date: | 2019-12-04 13:55:36 |
Message-ID: | 20191204135536.3drofgso4sut5enj@development |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On Wed, Dec 04, 2019 at 08:34:34AM -0500, Tom Lane wrote:
>MOHAN KUMAR DORAIRAJ <mohankumar(dot)dorairaj(at)globalfoundries(dot)com> 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
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2019-12-04 14:03:26 | Re: BUG #16147: postgresql 12.1 (from homebrew) - pg_restore -h localhost --jobs=2 crashes |
Previous Message | Alexey Bashtanov | 2019-12-04 13:51:32 | Re: pg_dump losing index column collations for unique and primary keys |