From: Adriaan van Os <adriaan@microbizz.nl>
To: pgsql-interfaces@postgresql.org
Subject: Re: Progress of asynchronous queries
Date: Mon, 18 Sep 2006 09:51:34 +0200
Message-ID: <450E5006.8020603@microbizz.nl> (raw)
In-Reply-To: <16217.125.24.243.247.1158490996.squirrel@webmail.xs4all.nl>
References: <450A6A87.2030808@microbizz.nl>
<450AA301.9020408@microbizz.nl>
<6009.125.24.242.104.1158397058.squirrel@webmail.xs4all.nl>
<450D21E9.7060807@microbizz.nl>
<16217.125.24.243.247.1158490996.squirrel@webmail.xs4all.nl>
Jeroen T. Vermeulen wrote:
> On Sun, September 17, 2006 17:22, Adriaan van Os wrote:
>
>>> But you'd be doing this in a transaction anyway: you can't declare a
>>> cursor without starting a transaction first.Yes, you could deliberately
>>> declare "WITH HOLD" and keep using your cursor after commiting or
>>> aborting
>>> the transaction. But even then, so far as I know, the cursor presents a
>>> snapshot view of its result set so you get an effective isolation level
>>> of
>>> "serializable" even then.
>> No, carefully read
>> <http://www.postgresql.org/docs/8.1/static/transaction-iso.html;.
>
> I'm familiar with the document, thank you, but if you're not prepared to
> give any detail beyond "no" then I remain unconvinced. What part exactly
> do you disagree with? That cursors can't be declared without beginning a
> transaction first? That cursors present a snapshot view of their result
> set? That that amounts to an effective isolation level of "serializable?"
I now read that Postgres only supports FOR READ ONLY cursors. So, yes, for those cursors you are
right and my remark doesn't apply.
Still, the issue I raised was about tracing the progress of a SQL command in general, not about the
specific case of using a cursor instead.
Regards,
Adriaan van Os
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: adriaan@microbizz.nl
Subject: Re: Progress of asynchronous queries
In-Reply-To: <450E5006.8020603@microbizz.nl>
* 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