Re: Cluster name in ps output

From: Andres Freund <andres(at)2ndquadrant(dot)com>
To: Thomas Munro <munro(at)ip9(dot)org>
Cc: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, Abhijit Menon-Sen <ams(at)2ndquadrant(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Stephen Frost <sfrost(at)snowman(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Cluster name in ps output
Date: 2014-06-29 12:25:44
Message-ID: 20140629122544.GK6450@awork2.anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2014-06-29 11:11:14 +0100, Thomas Munro wrote:
> On 29 June 2014 10:55, Andres Freund <andres(at)2ndquadrant(dot)com> wrote:
> > So, I'd looked at it with an eye towards committing it and found some
> > more things. I've now
> > * added the restriction that the cluster name can only be ASCII. It's
> > shown from several clusters with differing encodings, and it's shown
> > in process titles, so that seems wise.
> > * moved everything to the LOGGING_WHAT category
> > * added minimal documention to monitoring.sgml
> > * expanded the config.sgml entry to mention the restriction on the name.
> > * Changed the GUCs short description
>
> Thank you.
>
> > I also think, but haven't done so, we should add a double colon after
> > the cluster name, so it's not:
> >
> > postgres: server1 stats collector process
> > but
> > postgres: server1: stats collector process
>
> +1

Committed with the above changes. Thanks for the contribution!

Greetings,

Andres Freund

--
Andres Freund http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Abhijit Menon-Sen 2014-06-29 12:38:53 Re: Array of composite types returned from python
Previous Message Mohammad Alhashash 2014-06-29 12:03:10 Re: PATCH: Allow empty targets in unaccent dictionary