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

From Fujii Masao
Subject Re: maximum number of backtrace frames logged by backtrace_functions
Date
Msg-id 33675df8-60e1-7da6-8995-3743668fd682@oss.nttdata.com
Whole thread Raw
In response to Re: maximum number of backtrace frames logged by backtrace_functions  (Fujii Masao <masao.fujii@oss.nttdata.com>)
Responses Re: maximum number of backtrace frames logged by backtrace_functions  (Peter Eisentraut <peter.eisentraut@enterprisedb.com>)
List pgsql-docs

On 2022/02/04 9:48, Fujii Masao wrote:
> 
> 
> On 2022/02/03 23:48, Tom Lane wrote:
>> 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).
> 
> +1. I made this change to the patch and confirmed that it worked fine.

Barring any objection, I will commit the patch.

Regards,

-- 
Fujii Masao
Advanced Computing Technology Center
Research and Development Headquarters
NTT DATA CORPORATION



pgsql-docs by date:

Previous
From: "Jonathan S. Katz"
Date:
Subject: Re: documentation on HOT
Next
From: Peter Eisentraut
Date:
Subject: Re: maximum number of backtrace frames logged by backtrace_functions