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 1kgNUN-0004sa-9v for pgsql-hackers@arkaria.postgresql.org; Sat, 21 Nov 2020 07:39: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 1kgNUM-0000Uz-1Y for pgsql-hackers@arkaria.postgresql.org; Sat, 21 Nov 2020 07:39:18 +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 1kgNUL-0000Ur-9t for pgsql-hackers@lists.postgresql.org; Sat, 21 Nov 2020 07:39:17 +0000 Received: from forward4-smtp.messagingengine.com ([66.111.4.238]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kgNUI-00077N-Gz for pgsql-hackers@postgresql.org; Sat, 21 Nov 2020 07:39:15 +0000 Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailforward.nyi.internal (Postfix) with ESMTP id 7045D1942F9C; Sat, 21 Nov 2020 02:39:13 -0500 (EST) Received: from mailfrontend2 ([10.202.2.163]) by compute3.internal (MEProxy); Sat, 21 Nov 2020 02:39:13 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; bh=VerAqZKrOFoReD9MnC7m0+YKuruM68Y9+ZcC8kxgY w0=; b=eGa1na2NGf5aJwtSuKlbvxPK5/TjQcL0nGy+Q96rGlSgpbmZZ4wTqYQdc FoBumlbijKo09ryDYGijBSvfclOAmBw0sSS1arE1eQn2EDrBGe9GtmzpiGlYpj4M TvRI6rQKJrRYmXj/r7hyR731jG1gOFkotLGpaxvTYUSsF3KST1iB9s9vGXp7en0p JV3jKp/uKYyAUdQesBrM1xVkMHzoXPpBRuHTWUEOWCkK4c+cwtiEUxjJ0KP6x5Jv I89lb9RDTAAbG3FD0ZGopoASgRgNI2BY5GLhBp5Oj1aLj6N1oIlJmxGiM25fDGLS u+s7Wac9+PUQ5e/3rsuaIhjqo4W0w== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedujedrudeguddgudduudcutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmd enucfjughrpefuvfhfhfhokffffgggjggtgfesthejredttdefjeenucfhrhhomheprfgv thgvrhcugfhishgvnhhtrhgruhhtuceophgvthgvrhdrvghishgvnhhtrhgruhhtsegvnh htvghrphhrihhsvggusgdrtghomheqnecuggftrfgrthhtvghrnhepheehieejgfevhfdv heelkeeuvefhheehvdehtefghfetfeeggefgveejjeffgfdvnecukfhppeekjedrudejje drjeehrdelgeenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhr ohhmpehpvghtvghrrdgvihhsvghnthhrrghuthesvghnthgvrhhprhhishgvuggsrdgtoh hm X-ME-Proxy: Received: from april.pezone.net (p57b14b5e.dip0.t-ipconnect.de [87.177.75.94]) by mail.messagingengine.com (Postfix) with ESMTPA id 29FCA3064AA6; Sat, 21 Nov 2020 02:39:12 -0500 (EST) Subject: Re: jit and explain nontext To: Justin Pryzby References: <20201014193859.GS9241@telsasoft.com> <3643530.1602724513@sss.pgh.pa.us> <20201015014326.GU9241@telsasoft.com> <20201017192134.GD9241@telsasoft.com> <20201120161622.GI24784@telsasoft.com> Cc: David Rowley , Tom Lane , pgsql-hackers@postgresql.org, Andres Freund From: Peter Eisentraut Organization: EnterpriseDB Message-ID: Date: Sat, 21 Nov 2020 08:39:11 +0100 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 In-Reply-To: <20201120161622.GI24784@telsasoft.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On 2020-11-20 17:16, Justin Pryzby wrote: > It matters if it was planned with jit but executed without jit. > > postgres=# DEALLOCATE p; SET jit=on; SET jit_above_cost=0; prepare p as select from generate_series(1,9); explain(format yaml) execute p; SET jit=off; explain(format yaml) execute p; > > Patched shows this for both explains: > JIT: + > Functions: 3 + > > Unpatched shows only in the first case. In this context, I don't see the point of this change. If you set jit=off explicitly, then there is no need to clutter the EXPLAIN output with a bunch of zeroes about JIT.