Re: pg_dump crash on identity sequence with not loaded attributes - Mailing list pgsql-bugs

From Tom Lane
Subject Re: pg_dump crash on identity sequence with not loaded attributes
Date
Msg-id 84249.1733854089@sss.pgh.pa.us
Whole thread Raw
In response to Re: pg_dump crash on identity sequence with not loaded attributes  (Artur Zakirov <zaartur@gmail.com>)
Responses Re: pg_dump crash on identity sequence with not loaded attributes
List pgsql-bugs
Artur Zakirov <zaartur@gmail.com> 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



pgsql-bugs by date:

Previous
From: Artur Zakirov
Date:
Subject: Re: pg_dump crash on identity sequence with not loaded attributes
Next
From: Artur Zakirov
Date:
Subject: Re: pg_dump crash on identity sequence with not loaded attributes