| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
| Cc: | Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>, Christoph Berg <myon(at)debian(dot)org>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: PGCOLOR? (Re: pgsql: Unified logging system for command-line programs) |
| Date: | 2019-09-20 23:27:57 |
| Message-ID: | 7476.1569022077@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> writes:
> It looks like there is documentation for PG_COLORS in the release notes
> now, which seems like an odd place. Suggestions for a better place?
BTW, as far as that goes, it looks like PG_COLOR is documented separately
in each frontend program's "Environment" man page section. That's a bit
duplicative but I don't think we have a better answer right now. Seems
like you just need to add boilerplate text about PG_COLORS alongside
each of those.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2019-09-20 23:54:50 | pgsql: Update time zone data files to tzdata release 2019c. |
| Previous Message | Alvaro Herrera | 2019-09-20 23:23:03 | pgsql: Split out code into new getKeyJsonValueFromContainer() |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2019-09-21 00:09:31 | Re: Optimization of some jsonb functions |
| Previous Message | Tom Lane | 2019-09-20 23:24:13 | Re: Nondeterministic collations vs. text_pattern_ops |