From: Fabien COELHO <coelho@cri.ensmp.fr>
To: Bruce Momjian <bruce@momjian.us>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Alvaro Herrera <alvherre@2ndquadrant.com>
Cc: PostgreSQL-development <pgsql-hackers@postgresql.org>
Subject: Re: PG 13 release notes, first draft
Date: Wed, 13 May 2020 07:18:38 +0200 (CEST)
Message-ID: <alpine.DEB.2.22.394.2005130707170.3283649@pseudo> (raw)
In-Reply-To: <20200512211543.GB4666@momjian.us>
References: <20200512001744.GH4666@momjian.us>
<20200512003456.GA29166@alvherre.pgsql>
<20200512005714.GN4666@momjian.us>
<11843.1589250233@sss.pgh.pa.us>
<20200512025910.GX4666@momjian.us>
<alpine.DEB.2.22.394.2005120943030.2831675@pseudo>
<20200512211543.GB4666@momjian.us>
Hello Bruce,
>> * e1ff780485
>
> I was told in this email thread to not include that one.
Ok.
>> * 34a0a81bfb
>
> We already have:
>
> Reformat tables containing function information for better
> clarity (Tom Lane)
>
> so it seems it is covered as part of this.
AFAICR this one is not by the same author, and although the point was
about better clarity, it was not about formating but rather about
restructuring text vs binary string function documentations. Then Tom
reformatted the result.
>> * e829337d42
>
> Uh, this is a doc link formatting addition. I think this falls into the
> error message logic, where it is nice when people want it, but they
> don't need to know about it ahead of time.
Hmmm. ISTM that this is not really about "error message logic", it is
about navigating to libpq functions when one is reference in the
description of another to check what it does, which I had to do a lot
while developing some performance testing code for a project.
>> * "Document color support (Peter Eisentraut)"
>> THIS WAS NOT DOCUMENTED BEFORE?
>>
>> Not as such, AFAICR it was vaguely hinted about in the documentation of
>> command that would use it, but not even all of them. Now there is a new
>> specific section.
>
> Again, this is the first hash you gave.
Possibly, but as the "THIS WAS NOT DOCUMENTED BEFORE?" question seemed to
still be in the release notes, I gathered that the information had not
reached its destination, hence the possible repetition. But maybe the
issue is that this answer is not satisfactory. Sorry for the
inconvenience.
--
Fabien.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: coelho@cri.ensmp.fr, bruce@momjian.us, tgl@sss.pgh.pa.us, alvherre@2ndquadrant.com
Subject: Re: PG 13 release notes, first draft
In-Reply-To: <alpine.DEB.2.22.394.2005130707170.3283649@pseudo>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox