| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Gurjeet Singh <gurjeet(at)singh(dot)im>, Andres Freund <andres(at)2ndquadrant(dot)com>, Peter Eisentraut <peter_e(at)gmx(dot)net>, PGSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: /proc/self/oom_adj is deprecated in newer Linux kernels |
| Date: | 2014-06-10 15:39:13 |
| Message-ID: | CA+TgmoaBTgtTi4SUVuZw=Z5kj59AQCCp-hJw5sLcbokDSRaF-A@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Jun 10, 2014 at 11:29 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> This patch gives the user a control to let the backend's likelyhood of
>> being killed be different/higher than that of the postmaster.
>
> If you think your users might want to give the postmaster OOM-exemption,
> why don't you just activate the existing code when you build? Resetting
> the OOM setting to zero is safe whether or not the startup script did
> anything to the postmaster's setting.
The whole scenario here is that the user *doesn't want to recompile*.
You seem to be trying to relitigate an argument that Gurjeet already
discussed in his original post and I already refuted once after that.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2014-06-10 15:40:25 | Re: /proc/self/oom_adj is deprecated in newer Linux kernels |
| Previous Message | Robert Haas | 2014-06-10 15:35:23 | Re: /proc/self/oom_adj is deprecated in newer Linux kernels |