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 1nQEnk-000164-4g for pgsql-general@arkaria.postgresql.org; Fri, 04 Mar 2022 20:45:24 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1nQEni-0006ZN-3C for pgsql-general@arkaria.postgresql.org; Fri, 04 Mar 2022 20:45:22 +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 1nQEnh-0006ZD-Mc for pgsql-general@lists.postgresql.org; Fri, 04 Mar 2022 20:45:21 +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 1nQEna-0001aE-NZ for pgsql-general@lists.postgresql.org; Fri, 04 Mar 2022 20:45:20 +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=BVFCfVbpidvw08xlXv9WsGL/O/vZA7IUd23DZLHBeII=; b=A7tPJKkhb3VnWQuX/S3LXDVO3X 0fxCmpt9CVQ8hMde8kCCiFwD6NzblDitVHlzGpgNPzWiQyt1WC1DFXsTV3WMo3uTPEcLu2qAWs1EW gg8ldo0Wimbs5asbrkuPlkVLuihfRpoH/dBszbd+ewhpmO/KIJ5gijSuLwkI5yYNgi0A=; Received: from lana.depesz.com ([88.198.49.178] helo=depesz.com) by depesz.com with esmtpa (Exim 4.92) (envelope-from ) id 1nQEnX-0005xP-0E; Fri, 04 Mar 2022 21:45:11 +0100 Date: Fri, 4 Mar 2022 21:45:10 +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: <20220304204510.GA21340@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> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <3969790.1646420992@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 02:09:52PM -0500, Tom Lane wrote: > arm64, eh? I wonder if that's buggier than the Intel code paths. > > 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. Best regards, depesz