From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
---|---|
To: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Peter Geoghegan <peter(at)2ndquadrant(dot)com> |
Subject: | Re: silent_mode and LINUX_OOM_ADJ |
Date: | 2011-06-24 14:37:24 |
Message-ID: | 1308926157-sup-7749@alvh.no-ip.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Excerpts from Heikki Linnakangas's message of vie jun 24 07:01:57 -0400 2011:
> While reviewing Peter Geoghegan's postmaster death patch, I noticed that
> if you turn on silent_mode, the LINUX_OOM_ADJ code in fork_process()
> runs when postmaster forks itself into background. That re-enables the
> OOM killer in postmaster, if you've disabled it in the startup script by
> adjusting /proc/self/oom_adj. That seems like a bug, albeit a pretty
> minor one.
>
> This may be a dumb question, but what is the purpose of silent_mode?
> Can't you just use nohup?
I think silent_mode is an artifact from when our daemon handling in
general was a lot more primitive (I bet there wasn't even pg_ctl then).
Maybe we could discuss removing it altogether.
--
Álvaro Herrera <alvherre(at)commandprompt(dot)com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2011-06-24 15:17:19 | Re: Re: starting to review the Extend NOT NULL representation to pg_constraint patch |
Previous Message | Florian Pflug | 2011-06-24 14:15:35 | Re: Another issue with invalid XML values |