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 1tL4ed-00CZx5-Ay for pgsql-bugs@arkaria.postgresql.org; Tue, 10 Dec 2024 18:08:15 +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 1tL4ea-007wSP-NC for pgsql-bugs@arkaria.postgresql.org; Tue, 10 Dec 2024 18:08:13 +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 1tL4ea-007wSG-Ei for pgsql-bugs@lists.postgresql.org; Tue, 10 Dec 2024 18:08:13 +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 1tL4eZ-0027dN-66 for pgsql-bugs@lists.postgresql.org; Tue, 10 Dec 2024 18:08:12 +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 4BAI89RY084250; Tue, 10 Dec 2024 13:08:09 -0500 From: Tom Lane To: Artur Zakirov cc: PostgreSQL mailing lists Subject: Re: pg_dump crash on identity sequence with not loaded attributes In-reply-to: References: <4137493.1733781111@sss.pgh.pa.us> <66804.1733844592@sss.pgh.pa.us> Comments: In-reply-to Artur Zakirov message dated "Tue, 10 Dec 2024 18:54:22 +0100" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <84248.1733854089.1@sss.pgh.pa.us> Date: Tue, 10 Dec 2024 13:08:09 -0500 Message-ID: <84249.1733854089@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Artur Zakirov writes: > Alternatively, instead of forcing owning_tab->interesting to true, I > think we could always initialize owning_tab's attributes (i.e. arrays > like owning_tab->attnames, owning_tab->attidenity), which are used by > dumpSequence() and which causes the crash. Are there any downsides of > it? Lots. The entire point of the ->interesting flag is to avoid fetching additional details about tables that we don't really care about. Unless I misunderstand, you're proposing throwing away that whole optimization, which has got to be an overall loss. regards, tom lane