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

From Fujii Masao
Subject Re: Cluster name in ps output
Date
Msg-id CAHGQGwFgDSG0a3B4CWvjxwy-yw60tV3q-E0xpahnWs29hNgj4g@mail.gmail.com
Whole thread Raw
In response to Re: Cluster name in ps output  (Andres Freund <andres@2ndquadrant.com>)
List pgsql-hackers
On Sun, Jun 29, 2014 at 9:25 PM, Andres Freund <andres@2ndquadrant.com> wrote:
> On 2014-06-29 11:11:14 +0100, Thomas Munro wrote:
>> On 29 June 2014 10:55, Andres Freund <andres@2ndquadrant.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!

+        build). Only printable ASCII characters may be used in the
+        <varname>application_name</varname> value. Other characters will be

application_name should be cluster_name?

Regards,

-- 
Fujii Masao



pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: Deferring some AtStart* allocations?
Next
From: Kyotaro HORIGUCHI
Date:
Subject: Re: pg_resetxlog to clear backup start/end locations.