Re: [PATCH] Use new oom_score_adj without a new compile-time constant - Mailing list pgsql-hackers

From Robert Haas
Subject Re: [PATCH] Use new oom_score_adj without a new compile-time constant
Date
Msg-id CA+TgmobmhdNqUjZh7CrNLTAok-A6vemMxZJZg_c_wuoM0SxGxA@mail.gmail.com
Whole thread Raw
In response to Re: [PATCH] Use new oom_score_adj without a new compile-time constant  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Mon, Oct 24, 2011 at 1:17 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Robert Haas <robertmhaas@gmail.com> writes:
>>> [ oom_score_adj business ]
>
>> Did we do anything about this?  Anyone else have an opinion on what
>> ought to be done?
>
> I held off doing anything because it didn't seem like we had consensus.
> OTOH, it may well be that it's not important enough to demand real
> consensus, and he who does the work gets to make the choices.

Half a loaf is better than none.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company


pgsql-hackers by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Re: Separating bgwriter and checkpointer
Next
From: Heikki Linnakangas
Date:
Subject: Re: Inserting heap tuples in bulk in COPY