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 1nPoUD-0006Ln-8a for pgsql-general@arkaria.postgresql.org; Thu, 03 Mar 2022 16:39:29 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1nPoUB-0000Fm-TG for pgsql-general@arkaria.postgresql.org; Thu, 03 Mar 2022 16:39:27 +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 1nPoUB-0000FW-Gp for pgsql-general@lists.postgresql.org; Thu, 03 Mar 2022 16:39:27 +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 1nPoU8-00056B-5Q for pgsql-general@lists.postgresql.org; Thu, 03 Mar 2022 16:39:26 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=depesz.com; s=20170201; h=In-Reply-To:Content-Transfer-Encoding:Content-Type: MIME-Version:References:Reply-To:Message-ID:Subject:To:Sender:From:Date:Cc: 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=GNHghGh5b1XZ//m3fnUHhZyeeGCFjISIivxtoZ7f//A=; b=fiTixrWqrTmnhehJpvw49GaWBM /s5Iihu8s/FzdVlQ9eg3l013ZSB67mIpEiE068S7N8Toy10mLOu4l9AxeHhJ6T+paf0uVC+qo0qeY taXtab36Bm+kEFksD0yYBKNJZKsN0K7MAuKc0zfuTrNfDBJiIb+XSr0FkD8WDRarUnBY=; Received: from lana.depesz.com ([88.198.49.178] helo=depesz.com) by depesz.com with esmtpa (Exim 4.92) (envelope-from ) id 1nPoU5-0003L8-9M for pgsql-general@lists.postgresql.org; Thu, 03 Mar 2022 17:39:21 +0100 Date: Thu, 3 Mar 2022 17:39:21 +0100 From: hubert depesz lubaczewski Sender: depesz@depesz.com To: PostgreSQL General Subject: Re: Interesting fail when migrating Pg from Ubuntu Bionic to Focal Message-ID: <20220303163921.GA10776@depesz.com> Reply-To: depesz@depesz.com References: <20220303150428.GA26036@depesz.com> <20220303151156.GB26036@depesz.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20220303151156.GB26036@depesz.com> 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 Thu, Mar 03, 2022 at 04:11:56PM +0100, hubert depesz lubaczewski wrote: > On Thu, Mar 03, 2022 at 04:04:28PM +0100, hubert depesz lubaczewski wrote: > > and it worked, so I'm kinda at loss here. > > based on some talk on IRC, I was able to get stack trace from fail: Based on the stack trace I was able to get it to break using simple query: select p.proname, (SELECT rolname from pg_catalog.pg_roles where oid = p.proowner) from pg_proc p; I took a simple look at ranges of oid/prowner, and they look fine: =# select min(proowner), max(proowner), count(*) from pg_proc; min │ max │ count ─────┼─────┼─────── 10 │ 10 │ 2970 (1 row) 16:38:34 db: postgres@postgres, pid:1991057 =# select min(oid), max(oid), count(*) from pg_roles; min │ max │ count ─────┼───────────┼─────── 10 │ 310235824 │ 244 (1 row) Also, as I didn't mention it before: it's Pg 12.9. Best regards, depesz