Re: PATCH: backtraces for error messages

Поиск
Список
Период
Сортировка
От Daniel Gustafsson
Тема Re: PATCH: backtraces for error messages
Дата
Msg-id D5096465-812F-44A8-9388-607C800225BD@yesql.se
обсуждение исходный текст
Ответ на PATCH: backtraces for error messages  (Craig Ringer <craig@2ndquadrant.com>)
Список pgsql-hackers
> On 20 Jun 2018, at 17:10, Craig Ringer <craig@2ndquadrant.com> wrote:

> BTW, Álvaro posted a simpler patch at
https://www.postgresql.org/message-id/20180410213203.nl645o5vj5ap66sl@alvherre.pgsql.It uses backtrace() from glibc,
andrequires 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

В списке pgsql-hackers по дате отправления:

Предыдущее
От: Ashwin Agrawal
Дата:
Сообщение: Re: Avoiding Tablespace path collision for primary and standby
Следующее
От: Andrew Dunstan
Дата:
Сообщение: Re: Fast default stuff versus pg_upgrade