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 |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs pgsql-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());
From | Date | Subject | |
---|---|---|---|
Next Message | Radoslaw Zielinski | 2009-08-23 08:00:25 | Re: 8.4.0 data loss / HOT-related bug |
Previous Message | Craig Ringer | 2009-08-23 03:58:01 | Re: BUG #4996: postgres.exe memory consumption keeps going up |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2009-08-23 05:42:36 | Re: Slaying the HYPOTamus |
Previous Message | Greg Stark | 2009-08-23 04:39:52 | Re: Slaying the HYPOTamus |