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

Re: BUG #6459: logging_collector=off but log_filename set inhibits logoutpu

From: Christoph Anton Mitterer <calestyo(at)scientia(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #6459: logging_collector=off but log_filename set inhibits logoutpu
Date: 2012-02-20 02:59:53
Message-ID: 1329706793.6199.79.camel@fermat.scientia.net (view raw or flat)
Thread:
Lists: pgsql-bugs
Hi.

On Tue, 2012-02-14 at 18:45 -0500, Tom Lane wrote:
> calestyo(at)scientia(dot)net writes:
> > http://www.postgresql.org/docs/9.1/static/runtime-config-logging.html
> > claims that log_filename is only used when logging_collector is enabled.
> 
> That is a true statement, as can easily be proven by looking at the
> source code: nothing except syslogger.c pays any attention to the
> Log_filename variable.
Well nevertheless,... if set, I get no stderr output at all (which
Debian uses per default as log source).


> > However it seems that if the later is off, but the former is set (to
> > anything), no log output goes to stderr as well.
> 
> That would depend on other settings that you haven't mentioned,
> particularly log_destination.  Keep in mind also that the active setting
> of logging_collector can't be changed without a postmaster restart
> (which is why it's a separate variable from log_destination).

log_destination is commented, thus default stderr should apply.
And of course I've restarted.


Cheers,
Chris.

btw: I'll be on vacation till 1st of March, so don't expect any soon
answers.

In response to

Responses

pgsql-bugs by date

Next:From: Tom LaneDate: 2012-02-20 05:26:37
Subject: Re: BUG #6459: logging_collector=off but log_filename set inhibits logoutpu
Previous:From: MauMauDate: 2012-02-19 22:32:19
Subject: [Bug fix] postmaster always crashes on a debug version of Windows

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