Re: maximum number of backtrace frames logged by backtrace_functions - Mailing list pgsql-docs

From Tom Lane
Subject Re: maximum number of backtrace frames logged by backtrace_functions
Date
Msg-id 252159.1643899696@sss.pgh.pa.us
Whole thread Raw
In response to Re: maximum number of backtrace frames logged by backtrace_functions  (Peter Eisentraut <peter.eisentraut@enterprisedb.com>)
Responses Re: maximum number of backtrace frames logged by backtrace_functions  (Fujii Masao <masao.fujii@oss.nttdata.com>)
List pgsql-docs
Peter Eisentraut <peter.eisentraut@enterprisedb.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



pgsql-docs by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: maximum number of backtrace frames logged by backtrace_functions
Next
From: Fujii Masao
Date:
Subject: Re: maximum number of backtrace frames logged by backtrace_functions