Re: Snapshot 08.01.0006 available for testing - Mailing list pgsql-odbc

From Dave Page
Subject Re: Snapshot 08.01.0006 available for testing
Date
Msg-id E7F85A1B5FF8D44C8A1AF6885BC9A0E4CC38FB@ratbert.vale-housing.co.uk
Whole thread Raw
In response to Snapshot 08.01.0006 available for testing  ("Dave Page" <dpage@vale-housing.co.uk>)
List pgsql-odbc

> -----Original Message-----
> From: pgsql-odbc-owner@postgresql.org
> [mailto:pgsql-odbc-owner@postgresql.org] On Behalf Of Marko Ristola
> Sent: 03 November 2005 19:22
> To: Rainer Bauer
> Cc: pgsql-odbc@postgresql.org
> Subject: Re: [ODBC] Snapshot 08.01.0006 available for testing
>
> Problem:
> QR_Constructor is used for every new backend fetch.
> Original qres result will be forgotten in
> statement.c: 939 - 3 = 936

Yes - I originally tried to kill the qres, but that clobbered something
and crashed, so I just killed the tuplelist for the time being.

> Unfortunately QR_Destructor would close the cursor,
> which is bad for Declare/Fetch.

Well, on further testing, killing off QR->cursor, and then calling
QR_Destructor seems to work just fine. With cache sizes from 2 to 1000,
I'm seeing constant average memory usage. I did see a couple of crashes
with cache sizes of 100, but when I tried to investigate further, I
found I couldn't reproduce them at all, and have run successfully ever
since.

Changes committed to CVS.

Regards, Dave.

pgsql-odbc by date:

Previous
From: Marko Ristola
Date:
Subject: Re: Snapshot 08.01.0006 available for testing
Next
From: Leendert Paul Diterwich
Date:
Subject: postgresql odbc driver 7.3+ Visual Studio .Net