Postgres Pro
Downloads
Home   >   mailing lists

Re: Optionally using a better backtrace library? - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: Optionally using a better backtrace library?
Date
Msg-id 202309050959.sg5dnbyjdlev@alvherre.pgsql
Whole thread Raw
In response to Re: Optionally using a better backtrace library?  (Noah Misch <noah@leadboat.com>)
Responses Re: Optionally using a better backtrace library?
List pgsql-hackers
Tree view 
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/

pgsql-hackers by date:

Previous
From: Daniel Gustafsson
Date:
Subject: Re: pg_basebackup: Always return valid temporary slot names
Next
From: tender wang
Date:
Subject: Re: Should consider materializing the cheapest inner path in consider_parallel_nestloop()