From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Christoph Berg <myon(at)debian(dot)org>, 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: Set log_line_prefix and application name in test drivers |
Date: | 2016-09-29 02:30:16 |
Message-ID: | 21d2719f-36ff-06d2-5856-25ed48b965c5@2ndquadrant.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 9/28/16 6:13 PM, Robert Haas wrote:
> Christoph/Debian:
> log_line_prefix = '%t [%p-%l] %q%u(at)%d '
> Peter:
> log_line_prefix = '%t [%p]: [%l] %qapp=%a '
I'm aware of two existing guidelines on log line formats: syslog and
pgbadger. Syslog output looks like this:
Sep 28 00:58:56 hostname syslogd[46]: some text here
pgbadger by default asks for this:
log_line_prefix = '%t [%p]: [%l-1] user=%u,db=%d,app=%a,client=%h '
I don't know why it wants that "-1" there, and I'm actually not sure
what the point of %l is in practice. Those are separate issues that are
having their own lively discussions at times. I could drop the [%l]
from my proposal if that causes concerns.
On balance, I think my proposal is more in line with existing
wide-spread conventions.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Paquier | 2016-09-29 02:32:09 | Re: Fix checkpoint skip logic on idle systems by tracking LSN progress |
Previous Message | Peter Eisentraut | 2016-09-29 02:10:47 | Re: Set log_line_prefix and application name in test drivers |