pg.ddx.io pgsql-interfaces@postgresql.org mailing list archive
help / color / mirror / Atom feedODBC Memory leak
2+ messages / 2 participants
[nested] [flat]
* ODBC Memory leak
@ 1999-04-13 08:57 Denis Sbragion <sbragion@milan.crosswinds.net>
1999-04-15 22:54 ` Re: [INTERFACES] ODBC Memory leak Byron Nikolaidis <byronn@insightdist.com>
0 siblings, 1 reply; 2+ messages in thread
From: Denis Sbragion @ 1999-04-13 08:57 UTC (permalink / raw)
To: pgsql-interfaces
Hello,
It looks like the postgres ODBC (6.40.0005) leaks a lot of memory. Under a
heavy usage test the memory occupation increase up to 2 Mb every 30
seconds, until everything crashes. To be sure I did exactly the same test
using the MS SQL Server ODBC driver. This driver showed no memory leakage
at all. Anybody can confirm this?
Bye!
P.S. During this tests PostgreSQL+PgsqlODBC performed almost as fast as MS
SQL Server. Good job guys.
Sbragion Denis
InfoTecna
Tel, Fax: +39 039 2324054
URL: http://infotecna.home.dhs.org
^ permalink raw reply [nested|flat] 2+ messages in thread
* Re: [INTERFACES] ODBC Memory leak
1999-04-13 08:57 ODBC Memory leak Denis Sbragion <sbragion@milan.crosswinds.net>
@ 1999-04-15 22:54 ` Byron Nikolaidis <byronn@insightdist.com>
0 siblings, 0 replies; 2+ messages in thread
From: Byron Nikolaidis @ 1999-04-15 22:54 UTC (permalink / raw)
To: Denis Sbragion <sbragion@milan.crosswinds.net>; +Cc: pgsql-interfaces
Denis Sbragion wrote:
> Hello,
>
> It looks like the postgres ODBC (6.40.0005) leaks a lot of memory. Under a
> heavy usage test the memory occupation increase up to 2 Mb every 30
> seconds, until everything crashes. To be sure I did exactly the same test
> using the MS SQL Server ODBC driver. This driver showed no memory leakage
> at all. Anybody can confirm this?
>
Whoa! Well, nothing in the core driver has been changed in the version 0005
release, certainly nothing related to memory usage/allocation. In fact,
nothing has been changed along these lines since like version 6.30.0250 or
something.
Something to keep in mind though, if the driver is *NOT* using the "Use
Declare/Fetch option", then the driver will attempt to store the entire query
results in its memory. Is it possible your usage test would have done a huge
query or something like that? The Use Declare/Fetch option only allocates a
cache of 100 rows (by default) and never goes over that so huge queries
wouldn't bother it.
If there is a memory problem like this in the driver, I would like to know
more about your test so I can track it down. If so, you might try changing
some options (such as the Declare/Fetch) and see if it changes anything.
Byron
^ permalink raw reply [nested|flat] 2+ messages in thread
end of thread, other threads:[~1999-04-15 22:54 UTC | newest]
Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
1999-04-13 08:57 ODBC Memory leak Denis Sbragion <sbragion@milan.crosswinds.net>
1999-04-15 22:54 ` Byron Nikolaidis <byronn@insightdist.com>
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox