From: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
To: Justin Pryzby <pryzby@telsasoft.com>
To: Amit Kapila <amit.kapila16@gmail.com>
Cc: Bruce Momjian <bruce@momjian.us>
Cc: PostgreSQL-development <pgsql-hackers@postgresql.org>
Subject: Re: PG 13 release notes, first draft
Date: Thu, 14 May 2020 23:01:51 +0200
Message-ID: <08a50ae9-89fe-a29b-c4e4-0fb5033c2f06@2ndquadrant.com> (raw)
In-Reply-To: <20200512004155.GP18456@telsasoft.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>
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
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: peter.eisentraut@2ndquadrant.com, pryzby@telsasoft.com, amit.kapila16@gmail.com, bruce@momjian.us
Subject: Re: PG 13 release notes, first draft
In-Reply-To: <08a50ae9-89fe-a29b-c4e4-0fb5033c2f06@2ndquadrant.com>
* 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