From: Jeroen T. Vermeulen <jtv@xs4all.nl>
To: Adriaan van Os <adriaan@microbizz.nl>
Cc: pgsql-interfaces@postgresql.org
Subject: Re: Progress of asynchronous queries
Date: Tue, 19 Sep 2006 10:03:04 +0700 (ICT)
Message-ID: <11882.203.121.164.162.1158634984.squirrel@webmail.xs4all.nl> (raw)
In-Reply-To: <450E5006.8020603@microbizz.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>
<450E5006.8020603@microbizz.nl>
On Mon, September 18, 2006 14:51, Adriaan van Os wrote:
> 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.
True, and dealing with cursors is extra work in libpq.
In the C++ API OTOH there is a class that lets you treat a cursor more or
less as a regular query result. It's set to be replaced with a more
modern version, but it's usable: chunks of result data are fetched on
demand, i.e. as you access them. If you had something like that, all
you'd have to do is issue your query as before, process your data as
before, and update your progress display after every n rows of processing.
You wouldn't really notice any of the complexity underneath.
Jeroen
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: jtv@xs4all.nl, adriaan@microbizz.nl
Subject: Re: Progress of asynchronous queries
In-Reply-To: <11882.203.121.164.162.1158634984.squirrel@webmail.xs4all.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