From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Evan Rempel <erempel(at)uvic(dot)ca> |
Cc: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: 9.5 new setting "cluster name" and logging |
Date: | 2016-02-19 16:12:45 |
Message-ID: | 20160219161245.GE30326@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin pgsql-hackers |
On Fri, Feb 19, 2016 at 07:52:25AM -0800, Evan Rempel wrote:
> >>Allowing for the cluster_name to be referenced by an escape sequence
> >>would make manual and automated configuration management easier.
> >What if log_destination is set to csvlog? The same cluster_name is
> >output in every lines, and there is no way to disable it because
> >something like csv_line_prefix has not been supported yet?
> >
> >Regards,
> >
>
> I would think that in the case of using a csvlog that you would
> configure the log_line_prefix to not include the escape sequence of
> the cluster_name. The administrator would tune all of the logging
> components to work together, or am I missing something here?
csvlog isn't affected by log_line_prefix --- it outputs all fields every
time:
http://www.postgresql.org/docs/9.5/static/runtime-config-logging.html#RUNTIME-CONFIG-LOGGING-CSVLOG
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ As you are, so once was I. As I am, so you will be. +
+ Roman grave inscription +
From | Date | Subject | |
---|---|---|---|
Next Message | Evan Rempel | 2016-02-19 16:19:13 | Re: 9.5 new setting "cluster name" and logging |
Previous Message | Fujii Masao | 2016-02-19 16:10:03 | Re: 9.5 new setting "cluster name" and logging |
From | Date | Subject | |
---|---|---|---|
Next Message | Evan Rempel | 2016-02-19 16:19:13 | Re: 9.5 new setting "cluster name" and logging |
Previous Message | Fujii Masao | 2016-02-19 16:10:03 | Re: 9.5 new setting "cluster name" and logging |