Skip site navigation (1) Skip section navigation (2)

Re: silent_mode and LINUX_OOM_ADJ

From: Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>
To: Reinhard Max <max(at)suse(dot)de>
Cc: Magnus Hagander <magnus(at)hagander(dot)net>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, 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-28 07:40:17
Message-ID: 4E098561.7060402@enterprisedb.com (view raw or flat)
Thread:
Lists: pgsql-hackers
On 27.06.2011 12:38, Reinhard Max wrote:
> On Mon, 27 Jun 2011 at 12:10, Heikki Linnakangas wrote:
>
>> Max, you're the maintainer of the PostgreSQL SuSE RPMs, right?
>
> my first name is Reinhard, but aside from that, you are right. ;)

Sorry :-)

>> Can you comment on the above?
>
> I enabled it many years ago when (IIRC) it was needed in conjunction
> with "logging_collector = on" to get proper logging and especially log
> rotation. It might very well be that it is not needed anymore and
> suggestions for doing it better are welcome.

It seems to me you could just stop setting silent_mode. If you want to 
capture any early errors at startup into a log file, like silent_mode 
does to postmaster.log, you can redirect stdout and stderr in the 
startup script. pg_ctl start -l postmaster.log will do the same.

-- 
   Heikki Linnakangas
   EnterpriseDB   http://www.enterprisedb.com

In response to

Responses

pgsql-hackers by date

Next:From: Alexander KorotkovDate: 2011-06-28 07:47:43
Subject: Re: WIP: Fast GiST index build
Previous:From: Leonardo FrancalanciDate: 2011-06-28 07:30:38
Subject: Re: Your Postgresql 9.2 patch

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group