Re: Declare/Fetch - Mailing list pgsql-odbc

From Dave Page
Subject Re: Declare/Fetch
Date
Msg-id E7F85A1B5FF8D44C8A1AF6885BC9A0E4CC3886@ratbert.vale-housing.co.uk
Whole thread Raw
In response to Declare/Fetch  (Johann Zuschlag <zuschlag2@online.de>)
Responses Re: Declare/Fetch
List pgsql-odbc

> -----Original Message-----
> From: Johann Zuschlag [mailto:zuschlag2@online.de]
> Sent: 02 November 2005 13:02
> To: Dave Page; anoopk@pervasive-postgres.com;
> pgsql-odbc@postgresql.org
> Subject: Declare/Fetch
>
> Hi Dave, hi Anoop,

Hi Johann,

Unfortunately Anoop et al. are out for a few days, so I'm desperately
trying to understand and fix this before 8.1 :-(

> In qresult.c you still find:
>
> 515    if (fetch_count < fetch_count)
>
> Declare/Fetch will not work without changing that, i.e. just
> fetch one line.
>
> 515    if (fetch_count < num_backend_rows)
> (Dave's proposal)
>
> seems to be a better choice.

Updated in my local copy (thanks) - unfortunately not a fix to the bug
reported by Marko.

I have narrowed it down some more though - it's not so much a colwise
issue, as a bind issue. You can see it with the following:

1) Set cache size to 2 and enable Declare/Fetch
2) Connect
3) SQLExecDirect "SELECT relname FROM pg_class"
4) Bind to column 1
5) SQLFetch
6) SQLFetch
7) SQLFetch *bang* :-)

I'm largely unfamiliar with this part of the code so any help would be
appreciated. FWIW, the bug seems to be libpq version specific - it's
certainly not in 07.xx.

Regards, dave

pgsql-odbc by date:

Previous
From: Johann Zuschlag
Date:
Subject: Declare/Fetch
Next
From: "Leendert Paul Diterwich"
Date:
Subject: ERROR [HY000] Out of memory while reading tuples.