From: | Thomas Munro <munro(at)ip9(dot)org> |
---|---|
To: | Andres Freund <andres(at)2ndquadrant(dot)com> |
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 10:11:14 |
Message-ID: | CADLWmXWSEovY73Yh=qcD2-jjo1Y=-a=a4NJRKVHwko1zdJ3URg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
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
Best regards,
Thomas Munro
From | Date | Subject | |
---|---|---|---|
Next Message | David Rowley | 2014-06-29 10:48:49 | Re: Allowing NOT IN to use ANTI joins |
Previous Message | Andres Freund | 2014-06-29 09:55:11 | Re: Cluster name in ps output |