From: Ed Sabol <edwardjsabol@gmail.com>
To: pgsql-admin@lists.postgresql.org <pgsql-admin@lists.postgresql.org>
Subject: Re: pg_dump: WARNING: could not find operator
Date: Tue, 11 Jul 2023 18:30:12 -0400
Message-ID: <E773BD1D-6B16-463E-96E5-17484B9626EC@gmail.com> (raw)
In-Reply-To: <2563738.1689114275@sss.pgh.pa.us>
References: <D4B58A89-B5F5-4B26-A5EE-1B6976FD0895@gmail.com>
<2563738.1689114275@sss.pgh.pa.us>
On Jul 11, 2023, at 6:24 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> 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.
I'm mainly concerned about the pg_upgrade going smoothly. I'd like to minimize downtime as much as possible. I was planning to use "pg_upgrade --link", if it matters.
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: edwardjsabol@gmail.com, pgsql-admin@lists.postgresql.org
Subject: Re: pg_dump: WARNING: could not find operator
In-Reply-To: <E773BD1D-6B16-463E-96E5-17484B9626EC@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