Re: Support escape sequence for cluster_name in postgres_fdw.application_name

From: Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com>
To: "r(dot)takahashi_2(at)fujitsu(dot)com" <r(dot)takahashi_2(at)fujitsu(dot)com>, Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>
Cc: "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-02-07 14:03:56
Message-ID: 87a9be5a-ff59-47ff-ac7f-fad7891a46e3@oss.nttdata.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2022/01/28 14:07, r(dot)takahashi_2(at)fujitsu(dot)com wrote:
> I think %c of log_line_prefix (Session ID) is also useful for postgres_fdw.application_name.
> Therefore, how about adding both %c (Session ID) and %C (cluster_name)?

+1

Attached is the updated version of the patch. It adds those escape sequences %c and %C.

Regards,

--
Fujii Masao
Advanced Computing Technology Center
Research and Development Headquarters
NTT DATA CORPORATION

Attachment Content-Type Size
pgfdw_appname_cluster_name_v2.patch text/plain 1.9 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2022-02-07 14:53:13 Re: Removing more vacuumlazy.c special cases, relfrozenxid optimizations
Previous Message Julien Rouhaud 2022-02-07 10:29:47 Re: Database-level collation version tracking