Re: maximum number of backtrace frames logged by backtrace_functions

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>
Cc: Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com>, pgsql-docs(at)lists(dot)postgresql(dot)org
Subject: Re: maximum number of backtrace frames logged by backtrace_functions
Date: 2022-02-03 14:48:16
Message-ID: 252159.1643899696@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-docs

Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com> writes:
> How about we issue a message when the backtrace is cut off. Then it's
> immediately visible to the user, instead of hidden away somewhere in the
> documentation. Something like this (untested):

+1 for idea (I didn't test it either). Is "nframes" useful enough to
include in the report?

regards, tom lane

In response to

Responses

Browse pgsql-docs by date

  From Date Subject
Next Message Fujii Masao 2022-02-04 00:48:58 Re: maximum number of backtrace frames logged by backtrace_functions
Previous Message Peter Eisentraut 2022-02-03 09:30:00 Re: maximum number of backtrace frames logged by backtrace_functions