On Wed, Mar 21, 2007 at 05:32:21PM -0400, Andrew Dunstan wrote:
>
> I was looking at the TODO list today and noticed that we don't seem to
> have an item for libpq cursor support. I see it's been discussed in the
> past ( e.g.
> http://archives.postgresql.org/pgsql-interfaces/2000-09/msg00082.php ).
> We have occasional reports of libpq apps blowing up on huge resultsets,
> so ISTM this would be a good thing to have on the list.
There are a few issues here. Right now, if you code your client
correctly, you can retreive partial resultsets before the query has
finished executing (sort of streaming). However, it is a bit clumsy.
If you get libpq to wrap each query with a DECLARE CURSOR, you'd have
to teach it what queries can and can't have it. It would be nicer to do
it at the protocol level, but I don't know if that's supported.
Have a nice day,
--
Martijn van Oosterhout <kleptog@svana.org> http://svana.org/kleptog/
> From each according to his ability. To each according to his ability to litigate.
