Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1w4YrE-002JVk-1p for pgsql-hackers@arkaria.postgresql.org; Mon, 23 Mar 2026 06:33:49 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1w4YrC-00FvT3-1l for pgsql-hackers@arkaria.postgresql.org; Mon, 23 Mar 2026 06:33:46 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1w4YrC-00FvSv-0P for pgsql-hackers@lists.postgresql.org; Mon, 23 Mar 2026 06:33:46 +0000 Received: from mail-10624.protonmail.ch ([79.135.106.24]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1w4Yr9-00000000cHi-0q0J for pgsql-hackers@postgresql.org; Mon, 23 Mar 2026 06:33:45 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=pinaraf.info; s=protonmail; t=1774247621; x=1774506821; bh=Yo1M8F1s9M+HYLzdOXeU4Um/iAd0eJtagvUDm02+Fsw=; h=Date:To:From:Cc:Subject:Message-ID:In-Reply-To:References: Feedback-ID:From:To:Cc:Date:Subject:Reply-To:Feedback-ID: Message-ID:BIMI-Selector; b=ZekimF0vA5u4aiSTrjWsoFSEQ+ebJ9trPrqyKGo99y8fPcdlb5d9XUaaWAtdNztRl Nfzpz7zcorO8f1LRbgJYCwc3EKiEdLyGFOss8yOM4nFXCbIaUojx74B1QlSV3RcG8A A/iuH+c/BhLdsshYZ8gz7nfOCT7ZzVawazoib1PSjKl3HKxiT69hdFlDh4GcB87e2V oN8VU4tbHpA3BdmrjxoExcHvTtzJDNeas8K67WH6nzr2UHOmjbK1vQ65hFp8Hce/ON 0Xey1edp7teObzPNUwB43tB7k8B7sK0F05EyBtq3sZLz/eToALBLu2ue6VTs9wlQtU wN30jpxMlPZbw== Date: Mon, 23 Mar 2026 06:33:33 +0000 To: Tom Lane From: Pierre Ducroquet Cc: Tomas Vondra , Jelte Fennema-Nio , Andres Freund , Greg Sabino Mullane , Adrien Nayrat , Christoph Berg , Euler Taveira , =?utf-8?Q?=C3=81lvaro_Herrera?= , PostgreSQL Hackers , Andreas Karlsson , Anthonin Bonnefoy , pgsql-hackers , Michael Banck Subject: Re: Change default of jit to off Message-ID: In-Reply-To: <1629115.1774023867@sss.pgh.pa.us> References: <49490d8d-e8b9-497b-9a58-712daadb9ca9@anayrat.info> <5b5d04c3-e34e-4ae9-8b39-12b52e63154a@vondra.me> <1629115.1774023867@sss.pgh.pa.us> Feedback-ID: 175348558:user:proton X-Pm-Message-ID: 8a9101c76236cf7bc0bb017b12665b679e515316 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Le vendredi 20 mars 2026 =C3=A0 5:25 PM, Tom Lane a = =C3=A9crit=C2=A0: > Tomas Vondra writes: > > ISTM there's a clear consensus to get this committed for PG19, so > > barring objections I'll take care of that in the next couple days. > > Unless someone else wants to ... >=20 > +1 >=20 > > Another option would be to leave that for mid-beta, which is where we > > tweaked the io_method GUCs last year. But we did that to get some > > testing for 'worker' (in case we revert to 'sync'), and we don't need > > that for jit. >=20 > Doesn't seem like something to change mid-beta. If it makes anyone > unhappy, we'd best find out sooner not later. I've not seen any feedback on my "counter"-proposal: switch jit_tuple_defor= ming to off by default. Sure, for the perfect llvmjit use cases this will r= educe the performance benefits, but it will remove most if not all the prob= lematic queries (for instance queries running on many partitions, adding/mo= ving columns leading to explosions in compilation time...) Of course if there are other troublesome situations, I would love being pro= ven wrong.