From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Bill Moran <wmoran(at)potentialtech(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Running out of memory the hard way ... |
Date: | 2017-02-09 14:15:13 |
Message-ID: | 5604.1486649713@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Bill Moran <wmoran(at)potentialtech(dot)com> writes:
> Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> Bill Moran wrote:
>>> What I feel is the best way to mitigate the situation, is to have some
>>> setting that limits the maximum RAM any backend can consume.
>> I've had some success using ulimit in the past,
> Hopefully having this in the list archives will make the search easier
> for the next person who has this issue. Does anyone know if there are
> any suggestions to this effect in the official documentation? If not,
> I'll try to make some time to submit a patch.
[ grepgrepgrep... ] There is not. There are several mentions of ulimit
in the docs, but all of them point towards removing unreasonably-tight
default limits, not towards intentionally adding a limit. I think
something in or near 18.4.2 "Resource Limits" might be appropriate.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Jehan-Guillaume de Rorthais | 2017-02-09 15:42:14 | Re: clarification about standby promotion |
Previous Message | Berend Tober | 2017-02-09 13:01:02 | Re: Server SSL key with passphrase |