[pgpool-general: 9401] Re: Question about backend_application_name

Tatsuo Ishii ishii at postgresql.org
Thu Mar 27 08:55:56 JST 2025


> PgPool 4.5.4
> 
> Three node pgpool cluster:
> Node0 = Postgresql primary
> Node1 = Postgresql streaming replica
> Node2 = PgPool leader, where the VIP sits.
> 
> https://www.pgpool.net/docs/45/en/html/runtime-config-backend-settings.html
> 
> The docs consistently refer to setting backend_application_nameX to
> "serverX", so that's what I did:

"serverX" is just an example. You can use arbitrary name for
backend_application_nameX as long as:

a) It matches with the application name set in the primary_conninfo in
postgresql.conf.

b) No same application names are used in all primary_conninfo.

> But should it really be set to "walreceiver"?  Should both
> backend_application_name0 and backend_application_name1 be set to
> "walreceiver" even though it's only running on Node1?

I never tried it but probably yes. However I recommend in general to
set unique application names for each
backend_application_nameX. Someday you might want to add more replica.

> cdsmultip=# pgpool show backend_application_name2;
>  backend_application_name2
> ---------------------------
> 
> (1 row)

What's this? You said you only have one replica.

Best reagards,
--
Tatsuo Ishii
SRA OSS K.K.
English: http://www.sraoss.co.jp/index_en/
Japanese:http://www.sraoss.co.jp



More information about the pgpool-general mailing list