From: | "Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)com> |
---|---|
To: | "Alexy Khrabrov" <deliverable(at)gmail(dot)com> |
Cc: | pgsql-performance(at)postgresql(dot)org |
Subject: | Re: two memory-consuming postgres processes |
Date: | 2008-05-02 19:30:38 |
Message-ID: | dcc563d10805021230i5916561k3962a41e2afa894c@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
On Fri, May 2, 2008 at 1:24 PM, Alexy Khrabrov <deliverable(at)gmail(dot)com> wrote:
> Greetings -- I have an UPDATE query updating a 100 million row table, and
> allocate enough memory via shared_buffers=1500MB. However, I see two
> processes in top, the UPDATE process eating about 850 MB and the writer
> process eating about 750 MB. The box starts paging. Why is there the
> writer taking almost as much space as the UPDATE, and how can I shrink it?
Shared_buffers is NOT the main memory pool for all operations in
pgsql, it is simply the buffer pool used to hold data being operated
on.
Things like sorts etc. use other memory and can exhaust your machine.
However, I'd like to see the output of vmstat 1 or top while this is
happening.
How much memory does this machine have?
From | Date | Subject | |
---|---|---|---|
Next Message | Alexy Khrabrov | 2008-05-02 19:38:37 | Re: two memory-consuming postgres processes |
Previous Message | Alexy Khrabrov | 2008-05-02 19:24:35 | two memory-consuming postgres processes |