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 ) id 1nH6dY-0001Yr-Be for pgsql-docs@arkaria.postgresql.org; Mon, 07 Feb 2022 16:13:08 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1nH6dX-0005iT-7E for pgsql-docs@arkaria.postgresql.org; Mon, 07 Feb 2022 16:13:07 +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 ) id 1nH6dW-0005iJ-VX for pgsql-docs@lists.postgresql.org; Mon, 07 Feb 2022 16:13:06 +0000 Received: from out3-smtp.messagingengine.com ([66.111.4.27]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nH6dU-0003ui-6z for pgsql-docs@lists.postgresql.org; Mon, 07 Feb 2022 16:13:05 +0000 Received: from compute2.internal (compute2.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id CD3CB5C0048; Mon, 7 Feb 2022 11:13:01 -0500 (EST) Received: from mailfrontend2 ([10.202.2.163]) by compute2.internal (MEProxy); Mon, 07 Feb 2022 11:13:01 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:date:date:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:sender:subject :subject:to:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; bh=5oqCtNiCuWpAB+I9LG87miZ1382S16gCynm9s/J1T T0=; b=It1Lwyd2sf5SdzAA4Ne0BG9AwGMsqOSR1JxrR8y8vrsvEE80w5qTmRJ5h jXXYEhRH2pmBjVEfvJ5Kd5+9ZH7xfdULEYl48fo0++/oczxNigatkHo/+AR7dDZG p7Tvzkt47Z9hnKODSIxnwJVjphZcl8ZizRlauDU2PD4Q6DTq19e5aiS1oVwRsOMd alxdRIBqg2bld4jgJbApHTXC6EQXYdcjudBCj3aLg4yFPZ1VtMsNPivsi/W+Pdya vAetO8TmkHfUZm+Lf/lSTSMVnTCnagZ0/fI1DQdqn0jaT+Vi8Is09p6N9hWOm1kX JGS0XixRxDHqdRAQyQa2Ot4chwAmw== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvvddrheehgdekfecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefkffggfgfuvfhfhfgjtgfgsehtkeertddtfeejnecuhfhrohhmpefrvghtvghr ucfgihhsvghnthhrrghuthcuoehpvghtvghrrdgvihhsvghnthhrrghuthesvghnthgvrh hprhhishgvuggsrdgtohhmqeenucggtffrrghtthgvrhhnpeelgfetfeeitdelleeggeej vefhueetfedvtdejheevueeifeegvdfhueeludetueenucevlhhushhtvghrufhiiigvpe dtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehpvghtvghrrdgvihhsvghnthhrrghuthes vghnthgvrhhprhhishgvuggsrdgtohhm X-ME-Proxy: Received: by mail.messagingengine.com (Postfix) with ESMTPA; Mon, 7 Feb 2022 11:13:00 -0500 (EST) Message-ID: Date: Mon, 7 Feb 2022 17:12:58 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:91.0) Gecko/20100101 Thunderbird/91.5.1 Subject: Re: maximum number of backtrace frames logged by backtrace_functions Content-Language: en-US To: Fujii Masao , Tom Lane Cc: pgsql-docs@lists.postgresql.org References: <0f0ed9f3-3892-e8a3-51c9-ed268dff6bdd@oss.nttdata.com> <4e16a3e9-e717-05e1-d905-6c21beba80f8@enterprisedb.com> <252159.1643899696@sss.pgh.pa.us> <33675df8-60e1-7da6-8995-3743668fd682@oss.nttdata.com> From: Peter Eisentraut In-Reply-To: <33675df8-60e1-7da6-8995-3743668fd682@oss.nttdata.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 07.02.22 06:29, Fujii Masao wrote: >> >> On 2022/02/03 23:48, Tom Lane wrote: >>> Peter Eisentraut 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.