Re: BUG #4996: postgres.exe memory consumption keeps going up

From: "WANGRUNGVICHAISRI, SHIVESH" <sbw(at)appsig(dot)com>
To: <pgsql-bugs(at)postgresql(dot)org>
Cc: "Craig Ringer" <craig(at)postnewspapers(dot)com(dot)au>
Subject: Re: BUG #4996: postgres.exe memory consumption keeps going up
Date: 2009-08-26 01:25:50
Message-ID: 9D9EF0A21FC3914A9248DAE900EEF5FBFEC592@EXCHANGEVS01.appsig.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-hackers

Hi,

I have uploaded everything that you should need here:

http://www.filefactory.com/file/ah334c6/n/Pgsql_Leak_zip

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.

Thanks,

S.

-----Original Message-----
From: Craig Ringer [mailto:craig(at)postnewspapers(dot)com(dot)au]
Sent: Saturday, August 22, 2009 8:58 PM
To: WANGRUNGVICHAISRI, SHIVESH
Cc: pgsql-bugs(at)postgresql(dot)org
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:

http://wisdom-soft.com/products/screenhunter_free.htm

might be handy for that, by the way.

--
Craig Ringer

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Brian Ceccarelli 2009-08-26 01:38:31 Re: BUG #4999: select 'a' < 'A' is true, but should be false . . .
Previous Message Kevin Grittner 2009-08-25 21:29:41 Re: BUG #5011: Standby recovery unable to follow timeline change

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2009-08-26 02:17:38 Re: TODO item: Allow more complex user/database default GUC settings
Previous Message Chander Ganesan 2009-08-26 00:44:17 Re: We should Axe /contrib/start-scripts