Re: Support escape sequence for cluster_name in postgres_fdw.application_name

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>
Cc: Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Support escape sequence for cluster_name in postgres_fdw.application_name
Date: 2022-01-28 14:10:01
Message-ID: CA+TgmobqH83_iGmpUgjHrZa9ANPKaC9FD_5NMghrMBWUnwF17A@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Jan 27, 2022 at 3:10 AM Kyotaro Horiguchi
<horikyota(dot)ntt(at)gmail(dot)com> wrote:
> Is the reason for 'C' in upper-case to avoid possible conflict with
> 'c' of log_line_prefix? I'm not sure that preventive measure is worth
> doing. Looking the escape-sequence spec alone, it seems to me rather
> strange that an upper-case letter is used in spite of its lower-case
> is not used yet.

It's good to be consistent, though.

--
Robert Haas
EDB: http://www.enterprisedb.com

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Bharath Rupireddy 2022-01-28 14:10:02 Remove extra includes of "access/xloginsert.h" when "access/xlog.h" is included
Previous Message Daniel Gustafsson 2022-01-28 14:08:09 Re: Support for NSS as a libpq TLS backend