Re: warning about oom_adj with PG 9.4 logger

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Sinclair, Ian D (Ian)" <isinclair(at)avaya(dot)com>
Cc: "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: warning about oom_adj with PG 9.4 logger
Date: 2016-12-07 23:07:02
Message-ID: 1159.1481152022@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

"Sinclair, Ian D (Ian)" <isinclair(at)avaya(dot)com> writes:
> While loading 9.4 in my system I got a warning that oom_adj is deprecated, which seems to have come from the postgres logger task. I found emails in the archives that this error was fixed in 9.3.3.1 but did the same thing get missed in the logger code? Is it fixed later? I'm working on an upgrade to 9.6.

PG 9.4 won't try to touch oom_adj unless it's built with a compile flag
to tell it to do so. Apparently, whereever you got your PG build from
was not on the same page as your kernel about which OOM API is preferred
or deprecated. It's probably just cosmetic anyway, so I'd say ignore it.

9.5 and up have a better design for this, in which the behavior is
determined on the fly rather than being hard-wired at build time.

regards, tom lane

In response to

Browse pgsql-general by date

  From Date Subject
Next Message metaresolve 2016-12-07 23:13:34 Problems Importing table to pgadmin
Previous Message Jorge Torralba 2016-12-07 22:50:30 Re: ERROR invalid page header in block xxx of relation base/xxxxx/xxxxx/