| From: | Peter Geoghegan <pg(at)bowt(dot)ie> |
|---|---|
| To: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
| Cc: | Justin Pryzby <pryzby(at)telsasoft(dot)com>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: PG 13 release notes, first draft |
| Date: | 2020-05-14 21:02:52 |
| Message-ID: | CAH2-WzmMq+53zOn+6VDhSHj2pa9mn0MLGx1KE3u38sP=0ObD9g@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, May 14, 2020 at 2:02 PM Peter Eisentraut
<peter(dot)eisentraut(at)2ndquadrant(dot)com> wrote:
> 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.
+1 -- it's very handy. Plus it has user-facing knobs.
--
Peter Geoghegan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Justin Pryzby | 2020-05-14 21:10:06 | Re: PG 13 release notes, first draft |
| Previous Message | Peter Eisentraut | 2020-05-14 21:01:51 | Re: PG 13 release notes, first draft |