| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
| Cc: | Christoph Berg <myon(at)debian(dot)org>, Robert Haas <robertmhaas(at)gmail(dot)com>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Subject: | Re: Non-empty default log_line_prefix |
| Date: | 2016-10-12 15:40:55 |
| Message-ID: | 16348.1476286855@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> writes:
> That still doesn't address what to do about syslog and eventlog users.
> We would need either a separate prefix setting for those, or maybe
> something like %q that says, skip to here if using syslog. (I don't
> know eventlog, so I don't know if a common setting for syslog and
> eventlog would work.)
Meh. Those aren't default log output targets, so I don't think the
default prefix needs to cater for them. People who adjust one setting
can adjust the other too.
There would be some value in the complexity you're thinking of for
installations that log to multiple targets concurrently, but really,
who does that? Most production installations already begrudge
the I/O volume for a single log target.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Christoph Berg | 2016-10-12 15:58:40 | Re: Non-empty default log_line_prefix |
| Previous Message | Tom Lane | 2016-10-12 15:36:17 | Re: [COMMITTERS] pgsql: Extend framework from commit 53be0b1ad to report latch waits. |