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.94.2) (envelope-from ) id 1r4kIZ-009vuR-3M for pgsql-committers@arkaria.postgresql.org; Sun, 19 Nov 2023 16:05:27 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1r4kIV-0049aH-Df for pgsql-committers@arkaria.postgresql.org; Sun, 19 Nov 2023 16:05:23 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1r4kIV-0049a9-66 for pgsql-committers@lists.postgresql.org; Sun, 19 Nov 2023 16:05:23 +0000 Received: from sss.pgh.pa.us ([68.162.161.243]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1r4kIO-006L2A-Br; Sun, 19 Nov 2023 16:05:21 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 3AJG5CWD1106877; Sun, 19 Nov 2023 11:05:12 -0500 From: Tom Lane To: Daniel Gustafsson cc: pgsql-committers@lists.postgresql.org, Andres Freund Subject: Re: pgsql: llvmjit: Use explicit LLVMContextRef for inlining In-reply-to: References: Comments: In-reply-to Daniel Gustafsson message dated "Fri, 17 Nov 2023 10:52:39 +0000" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <1106875.1700409912.1@sss.pgh.pa.us> Date: Sun, 19 Nov 2023 11:05:12 -0500 Message-ID: <1106876.1700409912@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Daniel Gustafsson writes: > llvmjit: Use explicit LLVMContextRef for inlining It looks like the v12 back-port of this wasn't quite right: canebrake and urutu have both been showing assertion failures down inside LLVMContextDispose since it went in. They aren't complaining about v13 and later, though. No idea what the cause may be, but perhaps the right answer is just to revert this and not try to fix the bug in v12? regards, tom lane