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

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: "ssurui" <ssurui(at)gmail(dot)com>,<pgsql-bugs(at)postgresql(dot)org>
Subject: Re: BUG #3680: memory leak when excuting a SQL "select count(id) from chinatelecom;"
Date: 2007-10-16 21:23:07
Message-ID: 4714E56A.EE98.0025.0@wicourts.gov
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

>>> On Tue, Oct 16, 2007 at 3:43 PM, in message
<200710162043(dot)l9GKhGeF091013(at)wwwmaster(dot)postgresql(dot)org>, "ssurui"
<ssurui(at)gmail(dot)com> wrote:

> use top command observe the available memory

top is not the best way to look at RAM usage. Try free or other tools.

> I find about 500MB memory is
> vanished after the SQL is executed.

Meaning that it is used by the OS cache? That would make sense,
given that you just read all the data pages for the table.

-Kevin

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message ssurui 2007-10-17 07:49:49 Re: BUG #3680: memory leak when excuting a SQL "select count(id) from chinatelecom; "
Previous Message Douglas Toltzman 2007-10-16 21:01:01 Re: BUG #3680: memory leak when excuting a SQL "select count(id) from chinatelecom; "