public inbox for [email protected]  

help / color / mirror / Atom feed

From: Peter Eisentraut <[email protected]>
To: Fujii Masao <[email protected]>
To: Tom Lane <[email protected]>
Cc: [email protected]
Subject: Re: maximum number of backtrace frames logged by backtrace_functions
Date: Mon, 7 Feb 2022 17:12:58 +0100
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>

On 07.02.22 06:29, Fujii Masao wrote:
>>
>> On 2022/02/03 23:48, Tom Lane wrote:
>>> Peter Eisentraut <[email protected]> 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.

view thread (15+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected], [email protected]
  Subject: Re: maximum number of backtrace frames logged by backtrace_functions
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox