Re: slave restarts with kill -9 coming from somewhere, or nowhere

From: Bert <biertie(at)gmail(dot)com>
To: "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org>
Subject: Re: slave restarts with kill -9 coming from somewhere, or nowhere
Date: 2013-04-04 06:39:10
Message-ID: CAFCtE1ndNOsy5oZzQS8X7mSoh5PbhtiOHKA2igcBj_KwtC_OZQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> Bert <biertie(at)gmail(dot)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

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message John Reeve 2013-04-04 18:34:27 upgrading postgresql84 package from rhel-x86_64-server-5 repo
Previous Message Tom Lane 2013-04-04 06:17:58 Re: slave restarts with kill -9 coming from somewhere, or nowhere