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

Re: BUG #6763: Severe memory leak with arrays and hstore

From: Craig Ringer <ringerc(at)ringerc(dot)id(dot)au>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: luben karavelov <karavelov(at)mail(dot)bg>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #6763: Severe memory leak with arrays and hstore
Date: 2012-07-27 05:52:29
Message-ID: 50122C9D.1070602@ringerc.id.au (view raw or flat)
Thread:
Lists: pgsql-bugs
On 07/27/2012 01:47 PM, Tom Lane wrote:
> Craig Ringer <ringerc(at)ringerc(dot)id(dot)au> writes:
>> OK, it's certainly leaking, but not in the same drastic way I was able
>> to reproduce manually a couple of times earlier. Self-contained test
>> case attached.
> Using HEAD with stock parameters, I don't see any significant change in
> allocated address space (VSZ): it sits right around 170MB.  The reported
> resident set size (RSS) starts from very little and rises to about
> 140MB, but I think that's just an artifact of the process touching more
> and more of the shared-buffers array as it runs.
Gah. I should know better than that. Sorry.

This makes me wonder if the "leak-like" pattern I saw earlier was just a 
similar growth in shared_buffers, and carried on more steeply rather 
than tapering off because I was working with a smaller data set.

--
Craig Ringer


In response to

pgsql-bugs by date

Next:From: Craig RingerDate: 2012-07-27 05:59:25
Subject: Re: BUG #6763: Severe memory leak with arrays and hstore
Previous:From: Tom LaneDate: 2012-07-27 05:47:05
Subject: Re: BUG #6763: Severe memory leak with arrays and hstore

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