From: Ron <ronljohnsonjr@gmail.com>
To: pgsql-admin@lists.postgresql.org
Subject: Re: pg_dump: WARNING: could not find operator
Date: Wed, 12 Jul 2023 22:08:03 -0500
Message-ID: <312a596e-034d-99d1-2f99-00c8b863eb83@gmail.com> (raw)
In-Reply-To: <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>
<115BEF7D-2297-45FE-A69D-C3E1C42133F1@gmail.com>
On 7/12/23 22:04, Ed Sabol wrote:
> 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
>>
>> SELECT * FROM pg_operator
>> WHERE oprcom IN (2234078, 2234199)
>> OR oprnegate IN (2234078, 2234199);
>>
>> 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);
Will they automagically disappear when you restore the pg_dump?
--
Born in Arizona, moved to Babylonia.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: ronljohnsonjr@gmail.com, pgsql-admin@lists.postgresql.org
Subject: Re: pg_dump: WARNING: could not find operator
In-Reply-To: <312a596e-034d-99d1-2f99-00c8b863eb83@gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox