I looked into this problem extensively today, and here's what I found.
It's not PostgreSQL that is leaking memory; it's the fact that our
application is also using PostGIS 1.3.6.
We have modified the test program such that it clearly shows memory leak
when PostGIS is used.
Below is the email that we sent to PostGIS group along with the download
link of the new test program.
"We have an example program that should demonstrate a memory leak in
postgres.exe caused by PostGIS when used in a multi-threaded situation.
The link to the entire zip file is here:
OS: Windows XP 32-bit
So my claim that PostgreSQL was leaking memory was not true, and I do
However, I still insist that potentially the PostgreSQL community might
want to look into why making use of libpq causes the client program's
memory consumption to keep growing. This can be easily observed using
the earlier test program uploaded to here:
(Note to Craig: you have already have downloaded this file)
Thanks for all the help,
In response to
pgsql-hackers by date
|Next:||From: Rick Gigger||Date: 2009-08-26 23:51:58|
|Subject: Re: 8.5 release timetable, again|
|Previous:||From: Greg Stark||Date: 2009-08-26 23:51:30|
|Subject: Re: We should Axe /contrib/start-scripts|
pgsql-bugs by date
|Next:||From: Craig Ringer||Date: 2009-08-27 00:35:54|
|Subject: Re: BUG #4996: postgres.exe memory consumption keeps going
|Previous:||From: Greg Stark||Date: 2009-08-26 21:57:37|
|Subject: Re: BUG #5012: mailing list VERP addresses not sender-verifiable|