From: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
---|---|
To: | Michael Paquier <michael(at)paquier(dot)xyz> |
Cc: | Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: PG_COLOR not mentioned in docs of vacuumlo, oid2name and pgbench |
Date: | 2020-03-04 09:12:23 |
Message-ID: | E640D609-E62B-40D8-8148-62219F3EA993@yesql.se |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> On 4 Mar 2020, at 08:54, Michael Paquier <michael(at)paquier(dot)xyz> wrote:
> All the tools mentioned in $subject have been switched recently to use
> the central logging infrastructure, which means that they have gained
> coloring output. However we (mostly I) forgot to update the docs.
+1 on updating the docs with PG_COLOR for these.
> Attached is a patch to fix this issue. Please let me know if there
> are comments and/or objections.
+ color in diagnostics messages. Possible values are
+ <literal>always</literal>, <literal>auto</literal>,
+ <literal>never</literal>.
Not being a native english speaker, I might have it backwards, but I find lists
of values in a sentence like this to be easier to read when the final value is
separated by a conjunction like:
<item 1>, <item 2>, .. , <item n-1> and <item n>
cheers ./daniel
From | Date | Subject | |
---|---|---|---|
Next Message | Daniel Gustafsson | 2020-03-04 09:14:37 | Re: PG14 target version? |
Previous Message | Dilip Kumar | 2020-03-04 09:10:20 | Re: PATCH: logical_work_mem and logical streaming of large in-progress transactions |