From: | "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk> |
---|---|
To: | "Marko Ristola" <Marko(dot)Ristola(at)kolumbus(dot)fi>, "Rainer Bauer" <usenet(at)munnin(dot)com> |
Cc: | <pgsql-odbc(at)postgresql(dot)org> |
Subject: | Re: Snapshot 08.01.0006 available for testing |
Date: | 2005-11-03 22:57:17 |
Message-ID: | E7F85A1B5FF8D44C8A1AF6885BC9A0E4CC38FB@ratbert.vale-housing.co.uk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-odbc |
> -----Original Message-----
> From: pgsql-odbc-owner(at)postgresql(dot)org
> [mailto:pgsql-odbc-owner(at)postgresql(dot)org] On Behalf Of Marko Ristola
> Sent: 03 November 2005 19:22
> To: Rainer Bauer
> Cc: pgsql-odbc(at)postgresql(dot)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.
From | Date | Subject | |
---|---|---|---|
Next Message | Alessandro Pedroso | 2005-11-04 01:19:52 | Problems with MDAC and lo |
Previous Message | Marko Ristola | 2005-11-03 19:21:36 | Re: Snapshot 08.01.0006 available for testing |