Re: pg_dump: WARNING: could not find operator

From: Ed Sabol <edwardjsabol(at)gmail(dot)com>
To: "pgsql-admin(at)lists(dot)postgresql(dot)org" <pgsql-admin(at)lists(dot)postgresql(dot)org>
Subject: Re: pg_dump: WARNING: could not find operator
Date: 2023-07-11 22:30:12
Message-ID: E773BD1D-6B16-463E-96E5-17484B9626EC@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

On Jul 11, 2023, at 6:24 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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.

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Laurenz Albe 2023-07-12 06:26:02 Re: pg_dump: WARNING: could not find operator
Previous Message Tom Lane 2023-07-11 22:24:35 Re: pg_dump: WARNING: could not find operator