Re: maximum number of backtrace frames logged by backtrace_functions

On 07.02.22 06:29, 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.

This change looks good to me.  There is also backtrace code in assert.c 
that might want the same treatment.