From: Tom Lane <tgl@sss.pgh.pa.us>
To: =?UTF-8?B?0JTQvNC40YLRgNC40Lkg0JjQstCw0L3QvtCy?= <firstdismay@gmail.com>
cc: pgsql-general@lists.postgresql.org
Subject: Re: pg_restore depending on user functions
In-reply-to: 
 <CAPL5KHoGa3uvyKp6z6m48LwCnTsK+LRQ_mcA4uKGfqAVSEjV_A@mail.gmail.com>
References: 
 <CAPL5KHoGa3uvyKp6z6m48LwCnTsK+LRQ_mcA4uKGfqAVSEjV_A@mail.gmail.com>
Comments: In-reply-to =?UTF-8?B?0JTQvNC40YLRgNC40Lkg0JjQstCw0L3QvtCy?=
 <firstdismay@gmail.com>
	message dated "Sun, 14 Nov 2021 15:10:32 +0500"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <2011524.1636911069.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Sun, 14 Nov 2021 12:31:09 -0500
Message-ID: <2011525.1636911069@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/2011525.1636911069%40sss.pgh.pa.us>
Precedence: bulk

=3D?UTF-8?B?0JTQvNC40YLRgNC40Lkg0JjQstCw0L3QvtCy?=3D <firstdismay@gmail.co=
m> writes:
> 1. I can determine the dependencies of the custom functions when creatin=
g
> the pg_dump? I did not find anything suitable for SUPPORT, probably this=
 is
> not the case?
> To recreate all of the functionality, I had to run schema recovery twice=
.
> (--schema-only)

Usually this is caused by being careless about search_path assumptions
in your functions ... but with no details, it's impossible to say
anything with certainty.

> 2. Why is pg_restore trying to set the value of fields of type GENERATED
> ALWAYS?

Otherwise it couldn't guarantee that the rows were restored with the same
values of the identity column that they had before.  I recall that we
had some bugs with GENERATED ALWAYS in early v10 versions, but when I try
it now, dump/restore of a table with an identity column seems to work
as expected.  What minor release are you using?

			regards, tom lane