Re: Optionally using a better backtrace library?

From: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
To: Noah Misch <noah(at)leadboat(dot)com>
Cc: Andres Freund <andres(at)anarazel(dot)de>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Optionally using a better backtrace library?
Date: 2023-09-05 09:59:40
Message-ID: 202309050959.sg5dnbyjdlev@alvherre.pgsql
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2023-Sep-04, Noah Misch wrote:

> On Mon, Jul 03, 2023 at 11:58:25AM +0200, Alvaro Herrera wrote:

> > Agreed, these backtraces are pretty close to useless. Not completely,
> > but I haven't found a practical way to use them for actual debugging
> > of production problems.
>
> For what it's worth, I use the attached script to convert the current
> errbacktrace output to a fully-symbolized backtrace.

Much appreciated! I can put this to good use.

--
Álvaro Herrera PostgreSQL Developer — https://www.EnterpriseDB.com/

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message tender wang 2023-09-05 10:10:32 Re: Should consider materializing the cheapest inner path in consider_parallel_nestloop()
Previous Message Daniel Gustafsson 2023-09-05 09:39:26 Re: pg_basebackup: Always return valid temporary slot names