Re: Cluster name in ps output - Mailing list pgsql-hackers

From Stephen Frost
Subject Re: Cluster name in ps output
Date
Msg-id 20140505140135.GG2556@tamriel.snowman.net
Whole thread Raw
In response to Re: Cluster name in ps output  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Cluster name in ps output  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
* Tom Lane (tgl@sss.pgh.pa.us) wrote:
> How about dropping the brackets, and the cluster-name concept, and
> just doing
>
>      postgres: 5432 checkpointer process

-1 for my part, as I'd just end up with a bunch of those and no
distinction between the various processes.  In other words, without a
cluster distinction, it's useless.

Including the value of listen_addresses along w/ the port would make it
useful.  If we really don't want the cluster-name concept (which,
personally, I like quite a bit), how about including the listen_address
value if it isn't '*'?  I could see that also helping users who
installed from a distro and got '127.0.0.1' and don't understand why
they can't connect...

Of course, these are users who can use 'ps' but not 'netstat'.  Not sure
how big that set really is.
Thanks,
    Stephen

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Cluster name in ps output
Next
From: Robert Haas
Date:
Subject: Re: Minor improvement to fdwhandler.sgml