Re: backtrace_functions emits trace for any elog

From: Noah Misch <noah(at)leadboat(dot)com>
To: Ilya Gladyshev <ilya(dot)v(dot)gladyshev(at)gmail(dot)com>
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: backtrace_functions emits trace for any elog
Date: 2023-09-04 21:13:18
Message-ID: 20230904211318.GB3789310@rfd.leadboat.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Sep 04, 2023 at 09:30:32PM +0100, Ilya Gladyshev wrote:
> I used backtrace_functions to debug one of my ideas and found its behavior counter-intuitive and contradictory to it own docs. I think the GUC is supposed to be used to dump backtrace only on elog(ERROR) (should it also be done for higher levels? not sure about this), but, in fact, it does that for any log-level. I have attached a patch that checks log-level before attaching backtrace.

This would make the feature much less useful. Better to change the docs.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Nathan Bossart 2023-09-04 23:08:29 Re: Inefficiency in parallel pg_restore with many tables
Previous Message Noah Misch 2023-09-04 21:09:06 Re: Create shorthand for including all extra tests