Content-Type: text/plain;
	charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.7\))
Subject: Re: pg_dump: WARNING: could not find operator
From: Ed Sabol <edwardjsabol@gmail.com>
In-Reply-To: <2c5b816e55fb35405f7d7afad3a517866c89c671.camel@cybertec.at>
Date: Wed, 12 Jul 2023 23:04:56 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <115BEF7D-2297-45FE-A69D-C3E1C42133F1@gmail.com>
References: <D4B58A89-B5F5-4B26-A5EE-1B6976FD0895@gmail.com>
 <2563738.1689114275@sss.pgh.pa.us>
 <E773BD1D-6B16-463E-96E5-17484B9626EC@gmail.com>
 <2c5b816e55fb35405f7d7afad3a517866c89c671.camel@cybertec.at>
To: "pgsql-admin@lists.postgresql.org" <pgsql-admin@lists.postgresql.org>
Archived-At: 
 <https://www.postgresql.org/message-id/115BEF7D-2297-45FE-A69D-C3E1C42133F1%40gmail.com>
Precedence: bulk

On Jul 12, 2023, at 2:26 AM, Laurenz Albe <laurenz.albe@cybertec.at> =
wrote:
> To find out which operators are causing the trouble, you can run =
queries like
>=20
> SELECT * FROM pg_operator
> WHERE oprcom IN (2234078, 2234199)
>   OR oprnegate IN (2234078, 2234199);
>=20
> and test everything that uses these broken operators particularly =
well.

OK, I found them in one of our databases. Based on the oprcode values, =
they seem to be related to an extension we have installed (pgsphere, in =
case anyone is curious). Probably from an old version of the extension, =
I'm guessing, as the current pgsphere passes all regression testing.

So how do I clean up these dangling operators? Is it as easy as the =
following?

DELETE FROM pg_operator
WHERE oprcom IN (2234078, 2234199)
  OR oprnegate IN (2234078, 2234199);

Thanks,
Ed