Re: backtrace_on_internal_error

From: Peter Eisentraut <peter(at)eisentraut(dot)org>
To: Andres Freund <andres(at)anarazel(dot)de>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: backtrace_on_internal_error
Date: 2023-12-11 09:29:26
Message-ID: 60705ae9-6f2a-4a04-8416-a096b4ff11d5@eisentraut.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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").

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message shveta malik 2023-12-11 09:30:50 Re: Synchronizing slots from primary to standby
Previous Message Heikki Linnakangas 2023-12-11 09:27:58 Re: Streaming I/O, vectored I/O (WIP)