| 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:16:22 |
| Message-ID: | CA+Tgmoas4qK-Um-RwSLAUXfKN+UothbofQ_3pfDtWGdrtaBNtA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Dec 5, 2023 at 12:40 PM Nathan Bossart <nathandbossart(at)gmail(dot)com> wrote:
> On Tue, Dec 05, 2023 at 11:55:05AM +0100, Peter Eisentraut wrote:
> > Would others find this useful?
>
> Yes. I think I would use this pretty frequently.
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().
--
Robert Haas
EDB: http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nathan Bossart | 2023-12-05 18:24:58 | Re: Make COPY format extendable: Extract COPY TO format implementations |
| Previous Message | Robert Haas | 2023-12-05 18:10:44 | Re: trying again to get incremental backup |