Re: slave restarts with kill -9 coming from somewhere, or nowhere - Mailing list pgsql-admin

From Bert
Subject Re: slave restarts with kill -9 coming from somewhere, or nowhere
Date
Msg-id CAFCtE1ndNOsy5oZzQS8X7mSoh5PbhtiOHKA2igcBj_KwtC_OZQ@mail.gmail.com
Whole thread Raw
In response to Re: slave restarts with kill -9 coming from somewhere, or nowhere  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-admin
aha, ok. This was a setting pg_tune sugested. But I can understand how that is a bad idea.

wkr,
Bert


On Thu, Apr 4, 2013 at 8:17 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
Bert <biertie@gmail.com> writes:
> These are my memory settings:
> work_mem = 4GB

> How is it possible that one connection (query) uses all the ram? And how
> can I avoid it?

Uh ... don't do the above.  work_mem is the allowed memory consumption
per query step, ie per hash or sort operation.  A complex query can
easily use multiples of work_mem.

                        regards, tom lane



--
Bert Desmet
0477/305361

pgsql-admin by date:

Previous
From: Tom Lane
Date:
Subject: Re: slave restarts with kill -9 coming from somewhere, or nowhere
Next
From: John Reeve
Date:
Subject: upgrading postgresql84 package from rhel-x86_64-server-5 repo