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: 
 <CAPL5KHoiNP8Z4Jq=EP0WBKr+07bfwk4sdH9k-+RQSJvYFVsC1A@mail.gmail.com>
References: 
 <CAPL5KHoGa3uvyKp6z6m48LwCnTsK+LRQ_mcA4uKGfqAVSEjV_A@mail.gmail.com>
 <2011525.1636911069@sss.pgh.pa.us>
 <CAPL5KHrkVKVp22XE4S0ByA94-3OvH+9HC19WFFMePK2_c1VF0g@mail.gmail.com>
 <2016240.1636915579@sss.pgh.pa.us>
 <CAPL5KHoiNP8Z4Jq=EP0WBKr+07bfwk4sdH9k-+RQSJvYFVsC1A@mail.gmail.com>
Comments: In-reply-to =?UTF-8?B?0JTQvNC40YLRgNC40Lkg0JjQstCw0L3QvtCy?=
 <firstdismay@gmail.com>
	message dated "Mon, 15 Nov 2021 03:49:27 +0500"
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-ID: <2048099.1636934771.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Sun, 14 Nov 2021 19:06:11 -0500
Message-ID: <2048100.1636934771@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/2048100.1636934771%40sss.pgh.pa.us>
Precedence: bulk

=3D?UTF-8?B?0JTQvNC40YLRgNC40Lkg0JjQstCw0L3QvtCy?=3D <firstdismay@gmail.co=
m> writes:
> =D0=B2=D1=81, 14 =D0=BD=D0=BE=D1=8F=D0=B1. 2021 =D0=B3. =D0=B2 23:46, To=
m Lane <tgl@sss.pgh.pa.us>:
>> This is not "details", this is an evidence-free assertion.  Please show
>> a concrete example of problematic functions.

> Ok, I'll do it.
> [ example ]

This is pretty far from being a self-contained example; I had to guess
at the definitions of several types that you didn't provide.  Having
done so, though, the set of functions and types seem to dump and restore
just fine.  So I still don't see any problem here.

Possibly worth noting is that pg_dump is careful to include this in
its output script:

SET check_function_bodies =3D false;

Without that, I can believe that you'd have some trouble restoring
these functions, since pg_dump doesn't know anything about the
cross-references appearing in the function bodies.  But with that,
there don't appear to be any troublesome cross-references here.

			regards, tom lane