| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Roman Konoval <rkonoval(at)gmail(dot)com> |
| Cc: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: Memory leak during delete with sequential scan |
| Date: | 2014-09-12 13:30:47 |
| Message-ID: | 29657.1410528647@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Roman Konoval <rkonoval(at)gmail(dot)com> writes:
> On Fri, Sep 12, 2014 at 5:17 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> In Linux systems you should generally be looking at RES minus SHR
>> not just RES to determine a process' private memory.
> By private memory here I mean the sum of Private_Dirty and Private_Clean
> values for every memory segment in /proc/<pid>/smaps.
Hm. I'm not terribly familiar with that API, but the notion that it
*ever* counts shared memory as "Private" sounds pretty bogus from here.
I'd suggest filing a bug against whichever kernel you're using.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Roman Konoval | 2014-09-12 13:42:54 | Re: Memory leak during delete with sequential scan |
| Previous Message | Roman Konoval | 2014-09-12 09:15:26 | Re: Memory leak during delete with sequential scan |