Re: Setting oom_adj on linux?

Alex Hunsaker <badalex@gmail.com>

From: Alex Hunsaker <badalex@gmail.com>

To: Stephen Frost <sfrost@snowman.net>

Cc: Tom Lane <tgl@sss.pgh.pa.us>, Magnus Hagander <magnus@hagander.net>, Alvaro Herrera <alvherre@commandprompt.com>, Andrew Dunstan <andrew@dunslane.net>, PostgreSQL-development <pgsql-hackers@postgresql.org>

Date: 2010-01-09T03:46:10Z

Lists: pgsql-hackers

On Fri, Jan 8, 2010 at 15:24, Stephen Frost <sfrost@snowman.net> wrote:
> There were a few issues, as it turns out, the particularly annoying one
> was in the init script which caused upgrades to fail due to sshd not
> being restarted, bug report here:

Thanks for the pointers!

> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=473573

The changes I proposed to the example linux startup script wont suffer
from that.

> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=487325
>
> In the end, the problem was with errors being returned from attempts to
> modify oom_adj.  As long as we can just ignore those hopefully there
> won't be any issues.

Yep sounds good.

Thanks again!

Tom, sounds like you got busy with other stuff :) Should I submit a
new patch that uses open and O_WRONLY?