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

Re: BUG #3680: memory leak when excuting a SQL "selectcount(id) from chinatelecom;"

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: "ssurui" <ssurui(at)mailst(dot)xjtu(dot)edu(dot)cn>,<pgsql-bugs(at)postgresql(dot)org>
Subject: Re: BUG #3680: memory leak when excuting a SQL "selectcount(id) from chinatelecom;"
Date: 2007-10-17 17:35:23
Message-ID: 4716018B.EE98.0025.0@wicourts.gov (view raw or flat)
Thread:
Lists: pgsql-bugs
>>> On Wed, Oct 17, 2007 at  2:49 AM, in message
<00e001c81092$4b5aca50$2300a8c0(at)ssuruieda>, "ssurui"
<ssurui(at)mailst(dot)xjtu(dot)edu(dot)cn> wrote: 
 
> After long time, the free memory is
> not increased, it still 300M memory vanished
 
I think the one thing everyone knows as a fact is that the memory did
not vanish.  Your latest message gives us a clue that what interests
you is why free (unused, idle, not giving you any benefit) memory
went down.  If that is the question, it is because PostgreSQL goes
through the OS file systems, so RAM which is serving no other purpose
will automatically be used to cache data.  If you need memory for
something else, the cache will be reduced to compensate.
 
-Kevin
 



In response to

pgsql-bugs by date

Next:From: ssuruiDate: 2007-10-18 01:04:05
Subject: Re: BUG #3680: memory leak when excuting a SQL "selectcount(id) from chinatelecom;"
Previous:From: Tom LaneDate: 2007-10-17 15:47:34
Subject: Re: BUG #3681: fillers are NULL in pgbench

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