I have uploaded everything that you should need here:
The zip file contains a readme.txt file that will explain everything.
Please note that if you want to see that the test program itself is not leaking, then change every occurrence of #if 1 that you find (there are 2 of them) to #if 0, and re-run the program. The memory consumption of the test program will stay constant.
My hypothesis is that we are doing the queries too fast for the OS to free up the memory, but that's just my hypothesis.
Please let me know what you find.
From: Craig Ringer [mailto:craig(at)postnewspapers(dot)com(dot)au]
Sent: Saturday, August 22, 2009 8:58 PM
To: WANGRUNGVICHAISRI, SHIVESH
Subject: Re: [BUGS] BUG #4996: postgres.exe memory consumption keeps going up
> Please launch Process Explorer and then your test program. Double-click
> on the postgres.exe backends to open info windows for them and do the
> same for the test program. Take a screenshot (windows-prtscrn) and save
> it. Let the test run a while and do the same thing occasionally to keep
> a record.
Auto Screen Recorder from:
might be handy for that, by the way.
In response to
pgsql-hackers by date
|Next:||From: Alvaro Herrera||Date: 2009-08-26 02:17:38|
|Subject: Re: TODO item: Allow more complex user/database default
|Previous:||From: Chander Ganesan||Date: 2009-08-26 00:44:17|
|Subject: Re: We should Axe /contrib/start-scripts|
pgsql-bugs by date
|Next:||From: Brian Ceccarelli||Date: 2009-08-26 01:38:31|
|Subject: Re: BUG #4999: select 'a' < 'A' is true, but should be false . . .|
|Previous:||From: Kevin Grittner||Date: 2009-08-25 21:29:41|
|Subject: Re: BUG #5011: Standby recovery unable to follow timeline change|