Re: postgres writer process growing up too much

From: "Heiner Vega" <hvegat(at)gmail(dot)com>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: postgres writer process growing up too much
Date: 2007-12-17 17:29:49
Message-ID: 3cc49c940712170929g6cd2a852i849d2485ea30b6ba@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Thanks to you guys for your help... I appreciate it a lot.

Now, I still have my SHR and RES growing up. How can I know the number at
which those values should stop?

On Dec 14, 2007 5:12 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> 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
>

--
Heiner Vega Thames

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Colin Wetherbee 2007-12-17 17:49:46 Re: Efficiency vs. code bloat for SELECT wrappers
Previous Message Tom Lane 2007-12-17 17:24:04 Re: mssql migration and boolean to integer problems