Subject: Re: PG 13 release notes, first draft
To: Justin Pryzby <pryzby@telsasoft.com>,
 Amit Kapila <amit.kapila16@gmail.com>
References: <20200505031600.GB21752@momjian.us>
 <CAA4eK1+tOd6vTXBjUyjEQF+NALdoX8d-EZu5HEs_nxZ-huX2Hw@mail.gmail.com>
 <CAA4eK1+DDmycMNy9VQH8dFcPnkF5j8MNWVHL4yWNZ_0BL8HF2Q@mail.gmail.com>
 <20200512004155.GP18456@telsasoft.com>
Cc: Bruce Momjian <bruce@momjian.us>,
 PostgreSQL-development <pgsql-hackers@postgresql.org>
From: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Organization: 2ndQuadrant
Message-ID: <08a50ae9-89fe-a29b-c4e4-0fb5033c2f06@2ndquadrant.com>
Date: Thu, 14 May 2020 23:01:51 +0200
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:52.0)
 Gecko/20100101 Thunderbird/52.9.1
MIME-Version: 1.0
In-Reply-To: <20200512004155.GP18456@telsasoft.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Precedence: bulk

On 2020-05-12 02:41, Justin Pryzby wrote:
> I'm not opposed to including it, but I think it's still true that the user
> doesn't need to know in advance that the error message will be additionally
> helpful in the event of corruption.  If we were to include more "error" items,
> we might also include these:
> 
> 71a8a4f6e36547bb060dbcc961ea9b57420f7190 Add backtrace support for error reporting

This is actually a legitimate user-visible feature and should be listed 
somewhere.

-- 
Peter Eisentraut              http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services