From: | Euler Taveira <euler(at)timbira(dot)com(dot)br> |
---|---|
To: | Michael Paquier <michael(at)paquier(dot)xyz> |
Cc: | Tatsuo Ishii <ishii(at)sraoss(dot)co(dot)jp>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Adding Unix domain socket path and port to pg_stat_get_wal_senders() |
Date: | 2019-04-12 14:55:26 |
Message-ID: | CAHE3wgj0dE5fWjehQ3z4E5_oPkmTKHrbLS8VGR5piFVXUaQwJg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Em sex, 12 de abr de 2019 às 01:39, Michael Paquier
<michael(at)paquier(dot)xyz> escreveu:
>
> On Thu, Apr 11, 2019 at 10:19:01PM -0300, Euler Taveira wrote:
> > application_name. I'm not sure if it solves your complain but Peter
> > committed a patch [1] for v12 that distinguishes replicas in the same
> > host via cluster_name.
>
> Let's be honest, this is just a workaround.
>
The question is: what is the problem we want to solve? Ishii-san asked
for a socket path. If we have already figured out the replica (via
application_name), use the replica PID to find the socket path. A new
column as suggested by Tom could show the desired info. Is it *really*
useful? I mean, how many setups have master and replica in the same
server? For a socket connection, directory is important and that
information I can get from unix_socket_directories parameter (I've
never seen a setup with multiple socket directories).
--
Euler Taveira Timbira -
http://www.timbira.com.br/
PostgreSQL: Consultoria, Desenvolvimento, Suporte 24x7 e Treinamento
From | Date | Subject | |
---|---|---|---|
Next Message | Fred .Flintstone | 2019-04-12 14:56:58 | Re: PostgreSQL pollutes the file system |
Previous Message | Tatsuo Ishii | 2019-04-12 14:38:52 | Re: Adding Unix domain socket path and port to pg_stat_get_wal_senders() |