RE: Support escape sequence for cluster_name in postgres_fdw.application_name - Mailing list pgsql-hackers

From r.takahashi_2@fujitsu.com
Subject RE: Support escape sequence for cluster_name in postgres_fdw.application_name
Date
Msg-id OS0PR01MB5682DB788FD7EAD3BDBC36F182229@OS0PR01MB5682.jpnprd01.prod.outlook.com
Whole thread Raw
In response to Re: Support escape sequence for cluster_name in postgres_fdw.application_name  (Fujii Masao <masao.fujii@oss.nttdata.com>)
Responses Re: Support escape sequence for cluster_name in postgres_fdw.application_name
List pgsql-hackers
Hi,


Thank you for developing this feature.
I think adding escape sequence for cluster_name is useful too.

> 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.

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)?


Regards,
Ryohei Takahashi



pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: make MaxBackends available in _PG_init
Next
From: Kyotaro Horiguchi
Date:
Subject: Re: Add connection active, idle time to pg_stat_activity