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 1nF9wB-0000Sg-Ts for pgsql-docs@arkaria.postgresql.org; Wed, 02 Feb 2022 07:20:19 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1nF9wA-000653-QH for pgsql-docs@arkaria.postgresql.org; Wed, 02 Feb 2022 07:20:18 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nF9wA-00064t-IX for pgsql-docs@lists.postgresql.org; Wed, 02 Feb 2022 07:20:18 +0000 Received: from out1-smtp.messagingengine.com ([66.111.4.25]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nF9w7-0004IN-NG for pgsql-docs@lists.postgresql.org; Wed, 02 Feb 2022 07:20:18 +0000 Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 543005C019F; Wed, 2 Feb 2022 02:20:14 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute4.internal (MEProxy); Wed, 02 Feb 2022 02:20:14 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=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=cRNZc2yCuF8orB0QYIKsUeyGj8J14J2r6J76IIa4qL4=; b=F9Uja4Zw RuXk3uIvT9r+CarkLk+FxnN0NDhPo/87OpDc14cXgf2Vrsk0DY7epd90hqk5agkI TDJ0zn+c7xUD0Kd5Z5MhjNRR4B7h/pWA7Y9/fJLJ0l4eQPxPCDYnIDhcLl63jvYB fTuWxHhefqjHEDdc8PZgT2JtDoP5iLHKJepZ1S3qCZPp93UW76hzpThqD+eQrZ/1 PWWwPyHPSBiK9Lbd1MB57IR0jv1aMLngj289jtKAvGAdjCIH1RLlw5MH4gxzuo7w NPa8Poewe3AFywAaO6LB2pzl/ZXwTNh59zbMXPE5I8jSJBz1M1pdaJPs3V57hhCu TOUDbuqW8jeqcw== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvvddrgeeggddutddvucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepkfffgggfuffvfhfhjggtgfesthejredttdefjeenucfhrhhomheprfgvthgv rhcugfhishgvnhhtrhgruhhtuceophgvthgvrhdrvghishgvnhhtrhgruhhtsegvnhhtvg hrphhrihhsvggusgdrtghomheqnecuggftrfgrthhtvghrnhepfeejgeehteeuhfevvedu leeufedtjeetiefftedvudfhtdeifefgueettdevgefgnecuvehluhhsthgvrhfuihiivg eptdenucfrrghrrghmpehmrghilhhfrhhomhepphgvthgvrhdrvghishgvnhhtrhgruhht segvnhhtvghrphhrihhsvggusgdrtghomh X-ME-Proxy: Received: by mail.messagingengine.com (Postfix) with ESMTPA; Wed, 2 Feb 2022 02:20:12 -0500 (EST) Message-ID: <4e16a3e9-e717-05e1-d905-6c21beba80f8@enterprisedb.com> Date: Wed, 2 Feb 2022 08:20:12 +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.0 Subject: Re: maximum number of backtrace frames logged by backtrace_functions Content-Language: en-US To: Fujii Masao , pgsql-docs@lists.postgresql.org References: <0f0ed9f3-3892-e8a3-51c9-ed268dff6bdd@oss.nttdata.com> From: Peter Eisentraut In-Reply-To: <0f0ed9f3-3892-e8a3-51c9-ed268dff6bdd@oss.nttdata.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 01.02.22 18:04, Fujii Masao wrote: > The maximum number of backtrace frames logged by backtrace_functions is > 100. Isn't it better to document this information so that users can > understand not all backtrace always can be logged? Patch attached. The 100 was chosen as more than you'll ever need. If you are encountering cases with more than that, let's increase the limit.