RE: Memory leak in ODBC driver

From: "Hiroshi Inoue" <Inoue(at)tpf(dot)co(dot)jp>
To: <terry(at)greatbridge(dot)com>
Cc: <pgsql-bugs(at)postgresql(dot)org>
Subject: RE: Memory leak in ODBC driver
Date: 2001-03-10 03:37:10
Message-ID: EKEJJICOHDIEMGPNIFIJEECKDNAA.Inoue@tpf.co.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

> -----Original Message-----
> From: pgsql-bugs(at)postgresql(dot)org
>
> Terry Carlin (terry(at)greatbridge(dot)com) reports a bug with a severity of 2
> The lower the number the more severe it is.
>
> Short Description
> Memory leak in ODBC driver
>
> Long Description
> As part of Great Bridge QA testing, we run the AS3AP, TPC-C, and TPC-D
> benchmarks using 1 to 100 users. Our benchmarking tool is Benchmark
> Factory. It is a WinNT/Win2000 application. It uses ODBC to
> connect to PostgreSQL as there is no native driver for PostgreSQL
> yet. Benchmark Factory will run as many transactions as it can
> during a given timeframe.
>
> We have found that there is a memory leak in the PostgreSQL ODBC
> drivers. The system memory grows 100k to 300k every five seconds
> during the test. We are hitting from 500 to 1100 transactions per
> second. After we get through several hundred thousand
> transactions, we run out of swap space on the Win2000 box. The
> Win2000 box has about 1.2 gig of swap space.
>

I've just committed a change to CVS.
It would resolve the memory leak a little.

regards,
Hiroshi Inoue

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message pgsql-bugs 2001-03-10 14:37:04 PG 7.0.3SuSE7-1: /usr/include/pgsql/os.h points to nowhere
Previous Message pgsql-bugs 2001-03-09 15:41:16 Memory leak in ODBC driver