From: Tom Lane <tgl@sss.pgh.pa.us>
To: Ed Sabol <edwardjsabol@gmail.com>
cc: "pgsql-admin@lists.postgresql.org" <pgsql-admin@lists.postgresql.org>
Subject: Re: pg_dump: WARNING: could not find operator
In-reply-to: <D4B58A89-B5F5-4B26-A5EE-1B6976FD0895@gmail.com>
References: <D4B58A89-B5F5-4B26-A5EE-1B6976FD0895@gmail.com>
Comments: In-reply-to Ed Sabol <edwardjsabol@gmail.com>
	message dated "Tue, 11 Jul 2023 18:15:08 -0400"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <2563737.1689114275.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Tue, 11 Jul 2023 18:24:35 -0400
Message-ID: <2563738.1689114275@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/2563738.1689114275%40sss.pgh.pa.us>
Precedence: bulk

Ed Sabol <edwardjsabol@gmail.com> writes:
> Hello! I'm in the process of migrating some 10.23 database instances to =
15.3, and I'm getting these warnings when doing a pg_dumpall on one of the=
 servers:
> pg_dump: WARNING: could not find operator with OID 2234078
> pg_dump: WARNING: could not find operator with OID 2234199

> Is this indicative of a problem that I should fix before running pg_upgr=
ade? If so, how?

> And how do I find out what these OIDs are and what's referencing them?

=46rom a quick look at the pg_dump source code, this is indicative of
dangling links in either pg_operator.oprcom, pg_operator.oprnegate,
or pg_aggregate.aggsortop.  With no context it's difficult to guess
how they got there.  While you could clean it up manually, pg_dump
is just going to omit those clauses from its output, so there's no
real need to do anything if that outcome is sufficient.

			regards, tom lane