Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1mmKWL-0001B6-6O for pgsql-general@arkaria.postgresql.org; Sun, 14 Nov 2021 18:46:29 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1mmKWJ-00032C-In for pgsql-general@arkaria.postgresql.org; Sun, 14 Nov 2021 18:46:27 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1mmKWJ-000323-7M for pgsql-general@lists.postgresql.org; Sun, 14 Nov 2021 18:46:27 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1mmKWC-0002DT-UN for pgsql-general@lists.postgresql.org; Sun, 14 Nov 2021 18:46:26 +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 1AEIkJEt2016241; Sun, 14 Nov 2021 13:46:19 -0500 From: Tom Lane To: =?UTF-8?B?0JTQvNC40YLRgNC40Lkg0JjQstCw0L3QvtCy?= cc: pgsql-general@lists.postgresql.org Subject: Re: pg_restore depending on user functions In-reply-to: References: <2011525.1636911069@sss.pgh.pa.us> Comments: In-reply-to =?UTF-8?B?0JTQvNC40YLRgNC40Lkg0JjQstCw0L3QvtCy?= message dated "Sun, 14 Nov 2021 23:37:19 +0500" MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-ID: <2016239.1636915579.1@sss.pgh.pa.us> Content-Transfer-Encoding: quoted-printable Date: Sun, 14 Nov 2021 13:46:19 -0500 Message-ID: <2016240.1636915579@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk =3D?UTF-8?B?0JTQvNC40YLRgNC40Lkg0JjQstCw0L3QvtCy?=3D writes: > =D0=B2=D1=81, 14 =D0=BD=D0=BE=D1=8F=D0=B1. 2021 =D0=B3. =D0=B2 22:31, To= m Lane : >> 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. > No, in this case it is not: > Function A using function B. > =D0=A1reating function A before function B results in a compilation erro= r. > Function B has no dependencies and is generated without errors. The seco= nd > run of the circuit creates function A. > If I could specify a function dependency, it would change the order of > recovery This is not "details", this is an evidence-free assertion. Please show a concrete example of problematic functions. >> ... What minor release are you using? > PostgreSQL 14.1 (Debian 14.1-1.pgdg110+1) on x86_64-pc-linux-gnu, compi= led > by gcc (Debian 10.2.1-6) 10.2.1 20210110, 64-bit > pg_restote, pg_dump from this build Ok, so you're up to date all right. But again, you didn't say what concrete problem you were having with a dump/restore of an identity column. It works fine for me. regards, tom lane