On Thu, 28 Nov 2019 09:58:50 -0500, Tom Lane
wrote:
>Matthias Apitz writes:
>> When an ESQL/C written process issues a
>> EXEC SQL DISCONNECT [connection];
>> do the opened CURSOR(s) still survive?
>
>No. Cursors are purely session-local objects in Postgres.
>I'm a bit surprised to hear it migh
On Thu, 28 Nov 2019 07:27:15 +0100, Matthias Apitz
wrote:
>When an ESQL/C written process issues a
>
>EXEC SQL DISCONNECT [connection];
>
>do the opened CURSOR(s) still survive? We run into the problem that the
>father process issues DISCONNECT before forking children, the forked child
>CONNECTs
Matthias Apitz writes:
> When an ESQL/C written process issues a
> EXEC SQL DISCONNECT [connection];
> do the opened CURSOR(s) still survive?
No. Cursors are purely session-local objects in Postgres.
I'm a bit surprised to hear it might be different in Sybase.
regards, t
