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

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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Christoph Anton Mitterer <calestyo(at)scientia(dot)net>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #6459: logging_collector=off but log_filename set inhibits logoutpu
Date: 2012-02-20 05:26:37
Message-ID: 22832.1329715597@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-bugs
Christoph Anton Mitterer <calestyo(at)scientia(dot)net> writes:
> 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).

I wonder whether Debian's startup script is doing something that affects
this?  Because it's pretty hard to explain otherwise.

			regards, tom lane

In response to

Responses

pgsql-bugs by date

Next:From: Mark LangsdorfDate: 2012-02-20 14:51:12
Subject: Re: BUG #6462: rpmbuild fails during regression tests on SMP ARM machines
Previous:From: Christoph Anton MittererDate: 2012-02-20 02:59:53
Subject: Re: BUG #6459: logging_collector=off but log_filename set inhibits logoutpu

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