| From: | Alexander Kuzmenkov <a(dot)kuzmenkov(at)postgrespro(dot)ru> |
|---|---|
| To: | Craig Ringer <craig(at)2ndquadrant(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: PATCH: backtraces for error messages |
| Date: | 2018-06-20 15:51:33 |
| Message-ID: | 8d9f9ebf-adf7-1743-f200-28166267f06d@postgrespro.ru |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 06/20/2018 06:10 PM, Craig Ringer wrote:
>
> I recently needed a way to get backtraces from errors in a convenient,
> non-interactive and indescriminate way. The attached patch is the
> result. It teaches Pg to use libunwind to self-backtrace in elog/ereport.
>
> Anyone think this is useful/interesting/worth pursuing?
>
This would be a great thing to have. I often need to add stack traces to
the logs, and for now I just link with libunwind and add some ad-hoc
function to grab the traces. Having libunwind support in core would make
this simpler.
--
Alexander Kuzmenkov
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2018-06-20 15:51:48 | Re: found xmin from before relfrozenxid on pg_catalog.pg_authid |
| Previous Message | Alvaro Herrera | 2018-06-20 15:45:26 | Re: partition -> partitioned |