| From: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
|---|---|
| To: | Craig Ringer <craig(at)2ndquadrant(dot)com> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: PATCH: backtraces for error messages |
| Date: | 2018-06-20 17:34:13 |
| Message-ID: | D5096465-812F-44A8-9388-607C800225BD@yesql.se |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> On 20 Jun 2018, at 17:10, Craig Ringer <craig(at)2ndquadrant(dot)com> wrote:
> BTW, Álvaro posted a simpler patch at https://www.postgresql.org/message-id/20180410213203.nl645o5vj5ap66sl@alvherre.pgsql. It uses backtrace() from glibc, and requires each site you want to bt to be annotated explicitly. I forgot about backtrace() completely when I wrote mine, and I prefer the control libunwind gives me anyway, but the reduced dependency would be nice. Especially since backtrace() is in FreeBSD too.
Just as a datapoint regarding this; backtrace() is not available in OpenBSD,
but there is a library in ports which implements it, libexecinfo.
cheers ./daniel
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2018-06-20 17:46:11 | Re: Fast default stuff versus pg_upgrade |
| Previous Message | Ashwin Agrawal | 2018-06-20 17:31:05 | Re: Avoiding Tablespace path collision for primary and standby |