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 1sqhui-00C38V-Tq for pgsql-hackers@arkaria.postgresql.org; Tue, 17 Sep 2024 23:47:21 +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 1sqhui-000Jkk-Fn for pgsql-hackers@arkaria.postgresql.org; Tue, 17 Sep 2024 23:47:20 +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 1sqhui-000JkT-67 for pgsql-hackers@lists.postgresql.org; Tue, 17 Sep 2024 23:47:20 +0000 Received: from charmander.telsasoft.com ([50.244.222.1] helo=pryzbyj2023.telsasoft) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sqhub-001iPA-2j for pgsql-hackers@lists.postgresql.org; Tue, 17 Sep 2024 23:47:18 +0000 Received: by pryzbyj2023.telsasoft (Postfix, from userid 1000) id 55749298B; Tue, 17 Sep 2024 18:47:11 -0500 (CDT) Date: Tue, 17 Sep 2024 18:47:11 -0500 From: Justin Pryzby To: Tom Lane Cc: Robert Haas , =?utf-8?B?0JDQvdC00YDQtdC5INCg0LDRh9C40YbQutC40Lk=?= , pgsql-hackers@lists.postgresql.org Subject: Re: BUG #18545: \dt breaks transaction, calling error when executed in SET SESSION AUTHORIZATION Message-ID: References: <18545-feba138862f19aaa@postgresql.org> <72802.1721415837@sss.pgh.pa.us> <1722241488.182053205@f169.i.mail.ru> <3593204.1722466756@sss.pgh.pa.us> <3618203.1722473994@sss.pgh.pa.us> <916377.1722809337@sss.pgh.pa.us> <1807627.1722970465@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1807627.1722970465@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk This commit seems to trigger elog(), not reproducible in the parent commit. 6e086fa2e77 Allow parallel workers to cope with a newly-created session user ID. postgres=# SET min_parallel_table_scan_size=0; CLUSTER pg_attribute USING pg_attribute_relid_attnum_index; ERROR: pg_attribute catalog is missing 26 attribute(s) for relation OID 70321 postgres=# \errverbose ERROR: XX000: pg_attribute catalog is missing 26 attribute(s) for relation OID 70321 LOCATION: RelationBuildTupleDesc, relcache.c:658 This is not completely deterministic: postgres=# CLUSTER pg_attribute USING pg_attribute_relid_attnum_index; CLUSTER postgres=# CLUSTER pg_attribute USING pg_attribute_relid_attnum_index; CLUSTER postgres=# CLUSTER pg_attribute USING pg_attribute_relid_attnum_index; CLUSTER postgres=# CLUSTER pg_attribute USING pg_attribute_relid_attnum_index; CLUSTER postgres=# CLUSTER pg_attribute USING pg_attribute_relid_attnum_index; ERROR: pg_attribute catalog is missing 26 attribute(s) for relation OID 70391 But I think this will be reproducible in any database with a nontrivial number of attributes.