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 1nNdKw-0001IO-69 for pgsql-hackers@arkaria.postgresql.org; Fri, 25 Feb 2022 16:20:55 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1nNdKu-0003Bv-Nu for pgsql-hackers@arkaria.postgresql.org; Fri, 25 Feb 2022 16:20:52 +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 1nNdKt-0003Bl-0M for pgsql-hackers@lists.postgresql.org; Fri, 25 Feb 2022 16:20:52 +0000 Received: from out4-smtp.messagingengine.com ([66.111.4.28]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nNdKp-0004HE-KK for pgsql-hackers@lists.postgresql.org; Fri, 25 Feb 2022 16:20:49 +0000 Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 09C1A5C0217; Fri, 25 Feb 2022 11:20:46 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute4.internal (MEProxy); Fri, 25 Feb 2022 11:20:46 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=anarazel.de; h= cc:cc:content-type:date:date:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:sender:subject :subject:to:to; s=fm3; bh=Uhlvm/01/9n1vRGusmzOzsdpQjvO8Ejy1tojpY DYyzw=; b=qzBTsit6a9OodDL8YLhgStr1AR4EwaCKO5qb+ucecn59sOtnBD4fVr KVG1A4bcdfO5GnitLueO6+KAA1Ni4ZVolWfOLrDN2BN9a6GyQrYF1jmhh+fC18iM wxgRccYlkdcyrhR11065Qem+USruF6zrE80zww+u5Tjv9cPWQKpnnQQlTZLgIDmN vgmoWSyLiunFGP/QW3qzisJCN3hxsgHE/qDg4ISWubBl+AL9DMA9FiNTtiuaaIn3 PGeJCIypkf7JZZxm23xb84zMJ56qHJiOWlPhjItSz7BSeipBYLV+b4JQmkhti0xp VXy/el/xHJY63VEaggKI7MUaXimNKB1Q== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc: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=Uhlvm/01/9n1vRGus mzOzsdpQjvO8Ejy1tojpYDYyzw=; b=P6AhW85M6T8aghEkI1M4bJl1/3kgcnVHO jR7u6ZxZdzryyIpq7/jWXdF8s2glzH/12TtMHEPXRzSUn5LhwWliG3laScpQrnsS hTHHIbM2YicOJ7HNSIkeUPxVmMetZXbm08PhTkjTOOb+O9ksR09SpAHx+MaJ6/2U rWd83iqWKMMYWrYqhbjtdv4MZaTsgICzuRxp/F3N7nnKumJAQeDM6/PxllSf7Xe1 yuYxYT0b9CCTk/9nTRbfFw9x96OTZLSiZEpGVzJ8zAPILQFx0ImOHh6/BcAuiUtp e0o5dlMcdVWe1L0iVTfyBrBn2AEv5YADd6qYBoqUfAvIpCPZfqdyg== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvvddrleeggdekjecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpeffhffvuffkfhggtggujgesthdtredttddtvdenucfhrhhomheptehnughrvghs ucfhrhgvuhhnugcuoegrnhgurhgvshesrghnrghrrgiivghlrdguvgeqnecuggftrfgrth htvghrnhepudekhfekleeugeevteehleffffejgeelueduleeffeeutdelffeujeffhfeu ffdunecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomheprg hnughrvghssegrnhgrrhgriigvlhdruggv X-ME-Proxy: Received: by mail.messagingengine.com (Postfix) with ESMTPA; Fri, 25 Feb 2022 11:20:44 -0500 (EST) Date: Fri, 25 Feb 2022 08:20:43 -0800 From: Andres Freund To: Magnus Hagander Cc: PostgreSQL Developers Subject: Re: Add parameter jit_warn_above_fraction Message-ID: <20220225162043.6gqavxs2evbe6htf@alap3.anarazel.de> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Hi, On 2022-02-25 16:16:01 +0100, Magnus Hagander wrote: > This patch adds a configuration parameter jit_warn_above_fraction that > will cause a warning to be logged if the fraction of time spent on > doing JIT is bigger than the specified one. For example, this can be > used to track down those cases where JIT ends up taking 90% of the > query runtime because of bad estimates... Hm. Could it make sense to do this as a auto_explain feature? Greetings, Andres Freund