Re: postgres writer process growing up too much

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Richard Huxton <dev(at)archonet(dot)com>
Cc: Heiner Vega <hvegat(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org
Subject: Re: postgres writer process growing up too much
Date: 2007-12-14 23:12:00
Message-ID: 14888.1197673920@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Richard Huxton <dev(at)archonet(dot)com> writes:
> Heiner Vega wrote:
>> I've been monitoring my postgres processes and I noticed that the resident
>> memory
>> size of the writer process is growing up too much.

> Notice the "SHR"=shared value. That's 155MB virtual memory, 140MB of it
> resident of which 139MB is shared with other processes. So - nothing to
> worry about.

The reason the SHR number grows over time is that the system only counts
a page of shared memory against the process after the process has first
touched it. Once the bgwriter has touched every page of shared buffers,
the number will stop changing.

If there were actually a memory leak, the VIRT number would be growing
... but it's not.

>> My postgres version is 8.1.3

If I were you, I'd be considerably more worried about the fact that
you are running an old release with a pile of known bugs.

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2007-12-15 00:19:43 Re: Julian Day 0 question
Previous Message Tom Lane 2007-12-14 22:43:22 Re: settings for 8.2.5 on Mac OS X 10.4.11