Skip site navigation (1) Skip section navigation (2)

Re: Leak repairs

From: "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk>
To: "Anoop Kumar" <anoopk(at)pervasive-postgres(dot)com>
Cc: <pgsql-odbc(at)postgresql(dot)org>
Subject: Re: Leak repairs
Date: 2005-07-19 07:13:25
Message-ID: E7F85A1B5FF8D44C8A1AF6885BC9A0E4AC931B@ratbert.vale-housing.co.uk (view raw or flat)
Thread:
Lists: pgsql-odbc
 

> -----Original Message-----
> From: Anoop Kumar [mailto:anoopk(at)pervasive-postgres(dot)com] 
> Sent: 19 July 2005 07:35
> To: Dave Page
> Cc: pgsql-odbc(at)postgresql(dot)org
> Subject: RE: [ODBC] Leak repairs
> 
> Hi Dave,
> 
> I have tested the patch from you, and it does make the perfmon graph
> less steep. I am applying the patch to CVS.


Great, thanks. Any joy tracking down the last little bit?

> Regarding the call to PGgetisnull: My mistake! I forgot to remove it,
> thanks for pointing it out.

No problem.

I think we should put out a second snapshot sometime, as soon as the
rest of this memory leak is fixed, and the Excel problem is sorted. Any
progress on that one?

Also we need to expose the libpq SSL option to the user, probably on the
main connection dialogue, and obviously as a connection string option.
At the same time, the protocol version options can be removed. I can
probably look at that if you are pushed for time - let me know what you
prefer.

Finally, the threading problem. After discussion with Bruce Momjian and
Magnus Hagander, we think that the --enable-thread-safety configure
option should be used on Windows as well as other platforms as it does
do more than just enable critical sections around non-thread safe API
calls. I am (as time allows!) working on fixing PostgreSQL to allow
this.

Regards, Dave

Responses

pgsql-odbc by date

Next:From: Marko RistolaDate: 2005-07-19 07:36:48
Subject: Re: Leak repairs
Previous:From: Anoop KumarDate: 2005-07-19 06:35:09
Subject: Re: Leak repairs

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group