| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Nathan Bossart <nathandbossart(at)gmail(dot)com> |
| Cc: | Peter Eisentraut <peter(at)eisentraut(dot)org>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: backtrace_on_internal_error |
| Date: | 2023-12-05 18:30:23 |
| Message-ID: | CA+TgmoZROvY+URoUHwwO+wvdx-VdiGbqozh4+D0QuxWDE2uEHg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Dec 5, 2023 at 1:28 PM Nathan Bossart <nathandbossart(at)gmail(dot)com> wrote:
> On Tue, Dec 05, 2023 at 01:16:22PM -0500, Robert Haas wrote:
> > I think we should consider unconditionally emitting a backtrace when
> > an elog() is hit, instead of requiring a GUC. Or at least any elog()
> > that's not at a DEBUGn level. If the extra output annoys anybody, that
> > means they're regularly hitting an elog(), and it ought to be promoted
> > to ereport().
>
> Perhaps this should be a GUC that defaults to LOG or ERROR.
Why?
--
Robert Haas
EDB: http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tristan Partin | 2023-12-05 18:35:31 | Re: psql not responding to SIGINT upon db reconnection |
| Previous Message | Nathan Bossart | 2023-12-05 18:28:45 | Re: backtrace_on_internal_error |