Re: syslog_line_prefix

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: Magnus Hagander <magnus(at)hagander(dot)net>
Cc: Itagaki Takahiro <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: syslog_line_prefix
Date: 2009-09-15 18:18:17
Message-ID: 20090915181817.GE3907@alvh.no-ip.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Magnus Hagander wrote:

> I'm not sure I like this as a GUC. We're going to end up with a lot of
> different GUCs, and everytime we add a new log destination (admittedly
> not often, of course), that increases even further. And GUCs really
> don't provide the level of flexibility you'd really like to have. I've
> been thinking (long-term) in the direction of a separate config file,
> since that could contain an arbitrary number of lines, with "rules" on
> them (somewhat like pg_hba.conf maybe).

I tend to agree with this idea, but I'm not sure about rejecting the
current patch because of it.

FWIW one of the things that this "rules of logging config" system should
support is configuring each type of server process differently, for
example set min_log_level to debug2 for autovacuum only, etc.

--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2009-09-15 18:19:42 Re: Timestamp to time_t
Previous Message Andrew Gierth 2009-09-15 18:13:23 Re: revised hstore patch