Re: PG 14.5 -- Impossible to restore dump due to interaction/order of views, functions, and generated columns - Mailing list pgsql-general

From Tom Lane
Subject Re: PG 14.5 -- Impossible to restore dump due to interaction/order of views, functions, and generated columns
Date
Msg-id 3635234.1670340237@sss.pgh.pa.us
Whole thread Raw
In response to PG 14.5 -- Impossible to restore dump due to interaction/order of views, functions, and generated columns  ("Nunya Business" <nb3425586@gmail.com>)
Responses Re[2]: PG 14.5 -- Impossible to restore dump due to interaction/order of views, functions, and generated columns  ("Nunya Business" <nb3425586@gmail.com>)
Re[2]: PG 14.5 -- Impossible to restore dump due to interaction/order of views, functions, and generated columns  ("Nunya Business" <nb3425586@gmail.com>)
List pgsql-general
"Nunya Business" <nb3425586@gmail.com> writes:
> Within my schema there is a table that has a GENERATED ALWAYS column 
> that calls a plpgsql function.  The called function has a "row type" 
> variable declared that  references a view.  While the schema itself 
> functions properly day to day, and pg_dumpall works as expected, the 
> generated SQL fails to successfully execute.  The table in question is 
> restored with no rows, and an error is generated during the COPY stating 
> that the type does not exist.

Hmm, do you have actually circular dependencies in that?  pg_dump has
some heuristics for dealing with such cases, but maybe it needs more.
Please create a self-contained example and submit it to pgsql-bugs.

            regards, tom lane



pgsql-general by date:

Previous
From: Michael Loftis
Date:
Subject: Re: postgres large database backup
Next
From: Adrian Klaver
Date:
Subject: Re: PG 14.5 -- Impossible to restore dump due to interaction/order of views, functions, and generated columns