Received: from malur.postgresql.org ([217.196.149.56])
	by arkaria.postgresql.org with esmtps
 (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <pgsql-docs-owner+archive@lists.postgresql.org>)
	id 1nFdPM-0000jZ-Cc
	for pgsql-docs@arkaria.postgresql.org; Thu, 03 Feb 2022 14:48:24 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.92)
	(envelope-from <pgsql-docs-owner+archive@lists.postgresql.org>)
	id 1nFdPK-0007z7-G4
	for pgsql-docs@arkaria.postgresql.org; Thu, 03 Feb 2022 14:48:22 +0000
Received: from makus.postgresql.org ([2001:4800:3e1:1::229])
	by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1nFdPK-0007yy-8U
	for pgsql-docs@lists.postgresql.org; Thu, 03 Feb 2022 14:48:22 +0000
Received: from sss.pgh.pa.us ([66.207.139.130])
	by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1nFdPH-0006Jf-Hm
	for pgsql-docs@lists.postgresql.org; Thu, 03 Feb 2022 14:48:21 +0000
Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1])
	by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 213EmGQ9252160;
	Thu, 3 Feb 2022 09:48:16 -0500
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Peter Eisentraut <peter.eisentraut@enterprisedb.com>
cc: Fujii Masao <masao.fujii@oss.nttdata.com>, pgsql-docs@lists.postgresql.org
Subject: Re: maximum number of backtrace frames logged by backtrace_functions
In-reply-to: <b219d7c9-fb66-c762-ce90-ef20c0667a02@enterprisedb.com>
References: <0f0ed9f3-3892-e8a3-51c9-ed268dff6bdd@oss.nttdata.com>
 <4e16a3e9-e717-05e1-d905-6c21beba80f8@enterprisedb.com>
 <b22cd3c0-d76b-0379-5971-8637b65b8e87@oss.nttdata.com>
 <b219d7c9-fb66-c762-ce90-ef20c0667a02@enterprisedb.com>
Comments: In-reply-to Peter Eisentraut <peter.eisentraut@enterprisedb.com>
	message dated "Thu, 03 Feb 2022 10:30:00 +0100"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <252158.1643899696.1@sss.pgh.pa.us>
Date: Thu, 03 Feb 2022 09:48:16 -0500
Message-ID: <252159.1643899696@sss.pgh.pa.us>
List-Id: <pgsql-docs.lists.postgresql.org>
List-Help: <https://lists.postgresql.org/manage/>
List-Subscribe: <https://lists.postgresql.org/manage/>
List-Post: <mailto:pgsql-docs@lists.postgresql.org>
List-Owner: <mailto:pgsql-docs-owner@lists.postgresql.org>
List-Archive: <https://www.postgresql.org/list/pgsql-docs>
Archived-At: 
 <https://www.postgresql.org/message-id/252159.1643899696%40sss.pgh.pa.us>
Precedence: bulk

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