| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | 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-08-11 01:36:55 |
| Message-ID: | 19d9f94a-b65d-b8f0-579c-0ee1959b1814@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 8/10/16 5:18 PM, Tom Lane wrote:
> Or in short: I don't want to be seeing one prefix format in some buildfarm
> logs and a different format in others.
Sure. My patch has
log_line_prefix = '%t [%p]: [%l] %qapp=%a '
which is modeled after the pgfouine recommendation, which is I believe a
wide-spread convention, and it also vaguely follows syslog customs.
The build farm client has
log_line_prefix = '%m [%c:%l] '
which is very similar, but the lack of the PID makes it unsuitable for
the purposes that I have set out, and there is no obvious place to put
additional information such as %a.
%m vs %t is obviously a minor issue that I will gladly adjust, but
besides that I prefer to stick with my version.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Lukas Fittl | 2016-08-11 01:47:39 | Re: Btree Index on PostgreSQL and Wiredtiger (MongoDB3.2) |
| Previous Message | Peter Geoghegan | 2016-08-11 01:05:19 | Re: Improved ICU patch - WAS: Implementing full UTF-8 support (aka supporting 0x00) |