Re: [ADMIN] 9.5 new setting "cluster name" and logging

From: Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: Evan Rempel <erempel(at)uvic(dot)ca>, pgsql-admin(at)postgresql(dot)org, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [ADMIN] 9.5 new setting "cluster name" and logging
Date: 2016-10-17 21:56:03
Message-ID: CAEepm=3qzm=iROikNJFdjyZD3AJPEr3m_RFcmazBjZrzAVNoHw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin pgsql-hackers

On Tue, Feb 9, 2016 at 3:24 AM, Andres Freund <andres(at)anarazel(dot)de> wrote:
> Hi,
>
> (x-posting to -hackers, more relevant audience)
>
> On 2016-01-29 22:19:45 -0800, Evan Rempel wrote:
>> Now that there is a setting to give a cluster a "name", it would be nice to
>> have an escape sequence in the log_line_prefix setting that could reference
>> the cluster_name.
>
> I've argued[1][2] for this when cluster_name was introduced, but back
> then I seemed to have been the only one arguing for it. Josh later
> jumped that train.
>
> Given that we now had a number of people wishing for this, can we maybe
> reconsider?

+1

I missed the part of this conversation that took place on -admin. I
agree with Evan Rempel's post over there[1] that it's useful for
syslog users, and that it's not ideal to have to hijack syslog_ident
or explicitly copy the name into log_line_prefix.

[1] https://www.postgresql.org/message-id/56C64017.7050303%40uvic.ca

--
Thomas Munro
http://www.enterprisedb.com

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Stephen Frost 2016-10-17 22:24:05 Re: [ADMIN] 9.5 new setting "cluster name" and logging
Previous Message Poul Kristensen 2016-10-17 18:35:29 Re: PostgresSQL 9.5 and systemd autorestart but without replication.

Browse pgsql-hackers by date

  From Date Subject
Next Message Yury Zhuravlev 2016-10-17 22:03:34 Re: Add PGDLLEXPORT to PG_FUNCTION_INFO_V1
Previous Message Yury Zhuravlev 2016-10-17 21:39:30 Re: Add PGDLLEXPORT to PG_FUNCTION_INFO_V1