On Tue, 28 Jun 2011 at 10:40, Heikki Linnakangas wrote:
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
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 yea
Hi Heikki,
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. ;)
Can you comment on the above?
I enabled it many years ago when (IIRC) it was needed in conjun
On 27.06.2011 10:23, Magnus Hagander wrote:
On Fri, Jun 24, 2011 at 16:37, Alvaro Herrera
wrote:
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
On Fri, Jun 24, 2011 at 16:37, Alvaro Herrera
wrote:
> 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 post
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
