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 1nL0zb-00013E-EK for pgsql-docs@arkaria.postgresql.org; Fri, 18 Feb 2022 11:00:03 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1nL0z3-0006mN-4F for pgsql-docs@arkaria.postgresql.org; Fri, 18 Feb 2022 10:59:29 +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 1nL0z2-0006mE-Sa for pgsql-docs@lists.postgresql.org; Fri, 18 Feb 2022 10:59:28 +0000 Received: from wout3-smtp.messagingengine.com ([64.147.123.19]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nL0yy-0005Iq-6k for pgsql-docs@lists.postgresql.org; Fri, 18 Feb 2022 10:59:28 +0000 Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.west.internal (Postfix) with ESMTP id C4B733201F88; Fri, 18 Feb 2022 05:59:20 -0500 (EST) Received: from mailfrontend2 ([10.202.2.163]) by compute3.internal (MEProxy); Fri, 18 Feb 2022 05:59:21 -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=CtDAqMFqG2kk10EpIcwrF9a4Z0niWhFWLgJLnhZ+Y Dg=; b=XYH7wvIHPSiYx12mNU8YOJGtiV3RDCMt54pQlgRnhILt/UGohSiCMM17B CQZrtBA/yKl4JUYzAA0m+i6Gvko/P/5Dd6PfODEx0LAUfyWpdYTbalZwK0BsUMru s9eDJRClIZwvjU/P/h8YrFtmr9tusun0grptlZ83uMHyZJRpNesSgTqn3SPIYIG3 uaIJMMNWqII5RqztdcDOWnOmTnFVKT5vR3+nKtupCzuwwfPhbzUtot3XJslwv+by t8xPfyTuysVlh5JbsRj5Xh7LTWHiZFNYjPWNbmxe+K69BQKwCHgz94Vns6H+zSAn c8EoGAIykHZo5zYy7NT4m2M52RXFA== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvvddrkedtgddvudcutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefkffggfgfuvfhfhfgjtgfgsehtjeertddtfeejnecuhfhrohhmpefrvghtvghr ucfgihhsvghnthhrrghuthcuoehpvghtvghrrdgvihhsvghnthhrrghuthesvghnthgvrh hprhhishgvuggsrdgtohhmqeenucggtffrrghtthgvrhhnpeefjeegheetuefhveevudel ueeftdejteeiffetvdduhfdtieefgfeutedtveeggfenucevlhhushhtvghrufhiiigvpe dtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehpvghtvghrrdgvihhsvghnthhrrghuthes vghnthgvrhhprhhishgvuggsrdgtohhm X-ME-Proxy: Received: by mail.messagingengine.com (Postfix) with ESMTPA; Fri, 18 Feb 2022 05:59:18 -0500 (EST) Message-ID: <5c089e04-1f73-f9f1-b60d-d71d6c33e3f2@enterprisedb.com> Date: Fri, 18 Feb 2022 11:59:17 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:91.0) Gecko/20100101 Thunderbird/91.6.0 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> <9b3e1b97-4d2f-25af-fa52-1b2c31511444@enterprisedb.com> <7fce4874-1433-42e2-6649-e2c57ce50d4e@oss.nttdata.com> From: Peter Eisentraut In-Reply-To: <7fce4874-1433-42e2-6649-e2c57ce50d4e@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 18.02.22 09:24, Fujii Masao wrote: > Or even backtrace should be logged by write_stderr() so that it's > written to eventlog if necessary? I just wonder why > backtrace_symbols_fd() is used only in ExceptionalCondition(). Probably because it was simpler. It would also make sense to convert the whole thing to use write_stderr() consistently.