Postgres Pro
Downloads
Home   >   mailing lists

Re: backtrace_on_internal_error - Mailing list pgsql-hackers

From Nathan Bossart
Subject Re: backtrace_on_internal_error
Date
Msg-id 20231205174034.GA2757816@nathanxps13
Whole thread Raw
In response to backtrace_on_internal_error  (Peter Eisentraut <peter@eisentraut.org>)
Responses Re: backtrace_on_internal_error
List pgsql-hackers
Tree view 
On Tue, Dec 05, 2023 at 11:55:05AM +0100, Peter Eisentraut wrote:
> Would others find this useful?

Yes.  I think I would use this pretty frequently.

> Any other settings or variants in this area
> that should be considered while we're here?

IMO it would be nice to have a way to turn on backtraces for everything, or
at least everything above a certain logging level.  That would primarily be
useful for when you don't know exactly which C function is producing the
error.

-- 
Nathan Bossart
Amazon Web Services: https://aws.amazon.com

pgsql-hackers by date:

Previous
From: Krishnakumar R
Date:
Subject: Add checks in pg_rewind to abort if backup_label file is present
Next
From: Davin Shearer
Date:
Subject: Re: Emitting JSON to file using COPY TO