Re: backtrace_on_internal_error - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: backtrace_on_internal_error
Date
Msg-id 60705ae9-6f2a-4a04-8416-a096b4ff11d5@eisentraut.org
Whole thread Raw
In response to Re: backtrace_on_internal_error  (Andres Freund <andres@anarazel.de>)
List pgsql-hackers
On 08.12.23 19:14, Andres Freund wrote:
> FWIW, I did some analysis on aggregated logs on a larger number of machines,
> and it does look like that'd be a measurable increase in log volume. There are
> a few voluminous internal errors in core, but the bigger issue is
> extensions. They are typically much less disciplined about assigning error
> codes than core PG is.

Good point.  Also, during development, I often just put elog(ERROR, 
"real error later").




pgsql-hackers by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Re: Streaming I/O, vectored I/O (WIP)
Next
From: shveta malik
Date:
Subject: Re: Synchronizing slots from primary to standby