From: Christoph Haller <ch@rodos.fzk.de>
To: pgsql-interfaces@postgresql.org
Cc: wwest@csc.com
Subject: Re: Interaction between Cursor and Transaction storage?
Date: Tue, 25 Mar 2003 15:00:50 +0100
Message-ID: <3E806111.5929A731@rodos.fzk.de> (raw)
>
> QUESTION 1:
>
> Should RO-APP be doing anything other than closing
> the Cursors, to tell the Engine to just 'cleanup' when
> RO-APP is about to close its fe-be session and exit?
NO.
>
> QUESTION 2:
>
> Will an attempt by the RW-APP to do a commit or rollback
> while the RO-APP is fetching through an open Cursor cause
> RW-APP to wait until RO-APP closes the Cursor?
NO.
>
> QUESTION 3:
>
> Will an attempt by the RO-APP to open a Cursor while
> the RW-APP is performing a commit or rollback cause
> RO-APP to wait until RW-APP finishes its commit/
> rollback?
NO.
>
The answers are given to my best knowledge. If you prefer to be
absolutely sure you should post your questions to the hackers list,
as you've received no reply on this list within three days.
Regards, Christoph
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-interfaces@postgresql.org
Cc: ch@rodos.fzk.de, wwest@csc.com
Subject: Re: Interaction between Cursor and Transaction storage?
In-Reply-To: <3E806111.5929A731@rodos.fzk.de>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox