Skip site navigation (1) Skip section navigation (2)

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

From: Greg Stark <gsstark(at)mit(dot)edu>
To: Craig Ringer <craig(at)postnewspapers(dot)com(dot)au>
Cc: Shivesh Wangrungvichaisri <sbw(at)appsig(dot)com>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #4996: postgres.exe memory consumption keeps going up
Date: 2009-08-23 04:42:23
Message-ID: 407d949e0908222142l22368c60g7d56f7865e6aaa2f@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-bugspgsql-hackers
On Sun, Aug 23, 2009 at 4:48 AM, Craig
Ringer<craig(at)postnewspapers(dot)com(dot)au> wrote:
> Interestingly, though, the test program does appear to be leaking - at
> least, the peak working set slowly climbs. It's all private working set. Not
> sure why yet since the memory use looks like it _should_ be constant.

How does the return value of str() get cleaned up here?

                PGresult* res=PQexec(conn,insert.str().c_str());



-- 
greg
http://mit.edu/~gsstark/resume.pdf

In response to

Responses

pgsql-hackers by date

Next:From: Tom LaneDate: 2009-08-23 05:42:36
Subject: Re: Slaying the HYPOTamus
Previous:From: Greg StarkDate: 2009-08-23 04:39:52
Subject: Re: Slaying the HYPOTamus

pgsql-bugs by date

Next:From: Radoslaw ZielinskiDate: 2009-08-23 08:00:25
Subject: Re: 8.4.0 data loss / HOT-related bug
Previous:From: Craig RingerDate: 2009-08-23 03:58:01
Subject: Re: BUG #4996: postgres.exe memory consumption keeps going up

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group