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 1nQrVA-0002co-85 for pgsql-general@arkaria.postgresql.org; Sun, 06 Mar 2022 14:04:48 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1nQrUc-0003wr-5p for pgsql-general@arkaria.postgresql.org; Sun, 06 Mar 2022 14:04:14 +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 1nQrUb-0003tT-OI for pgsql-general@lists.postgresql.org; Sun, 06 Mar 2022 14:04:13 +0000 Received: from lana.depesz.com ([88.198.49.178] helo=depesz.com) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nQrUT-00039t-Uh for pgsql-general@lists.postgresql.org; Sun, 06 Mar 2022 14:04:12 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=depesz.com; s=20170201; h=In-Reply-To:Content-Type:MIME-Version:References:Reply-To: Message-ID:Subject:Cc:To:Sender:From:Date:Content-Transfer-Encoding: Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender: Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=2aeP79Xn5tg8FTd7Y3mnhQu8lT1kdxxTS1nMRpOoZHM=; b=ECHVLiaswApGocITbeLF4Dyltp oPWC5PL/0zY/ee9fbktaoUFjUk0y9hohMoHVbqBUMYht6js/EzttVUpOuqucPG7VmeTDyURE1jH8H coSiTNgxSH0G1FfCkHpBaEgQMngk8zhScXkfHvFECCMc0e/vkflUenyiS8jFCsRrbWFw=; Received: from lana.depesz.com ([88.198.49.178] helo=depesz.com) by depesz.com with esmtpa (Exim 4.92) (envelope-from ) id 1nQrUQ-0001oo-8A; Sun, 06 Mar 2022 15:04:02 +0100 Date: Sun, 6 Mar 2022 15:04:02 +0100 From: hubert depesz lubaczewski Sender: depesz@depesz.com To: Tom Lane Cc: PostgreSQL General , Andres Freund Subject: Re: Interesting fail when migrating Pg from Ubuntu Bionic to Focal Message-ID: <20220306140402.GA6360@depesz.com> Reply-To: depesz@depesz.com References: <20220303150428.GA26036@depesz.com> <20220303151156.GB26036@depesz.com> <20220303163921.GA10776@depesz.com> <20220303164401.GA13056@depesz.com> <3969790.1646420992@sss.pgh.pa.us> <20220304204510.GA21340@depesz.com> <3984384.1646431394@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <3984384.1646431394@sss.pgh.pa.us> User-Agent: Mutt/1.10.1 (2018-07-13) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Fri, Mar 04, 2022 at 05:03:14PM -0500, Tom Lane wrote: > hubert depesz lubaczewski writes: > > On Fri, Mar 04, 2022 at 02:09:52PM -0500, Tom Lane wrote: > >> I tried and failed to reproduce this on Fedora 35 on aarch64, > >> but that has what I think is a newer LLVM version: > > > I have suspicion that it also kinda depends on number of rows in there. > > When I deleted some schemas, which included some functions, the problem > > disappeared. > > I wasn't able to pinpoint specific thing, though, and when I called the > > pg_proc + pg_roles query for each separate row - it worked flawlessly. > > Mmm ... it might have just been that the planner chose not to use > JIT when it thought there were fewer rows involved. Did you check > with EXPLAIN that these cut-down cases still used JIT? Hi, I tore these boxes down, so can't check immediately, but I think I remember that you're right - single-row queries didn't use JIT. Best regards, depesz