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: 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-14 23:45:29
Message-ID: 11968.1329263129@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

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.

> 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).

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Andy Grimm 2012-02-15 05:09:12 Re: BUG #6412: psql & fe-connect truncate passwords
Previous Message calestyo 2012-02-14 21:09:24 BUG #6459: logging_collector=off but log_filename set inhibits logoutpu