Re: pg_dump: WARNING: could not find operator

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Edward J(dot) Sabol" <edwardjsabol(at)gmail(dot)com>
Cc: pgsql-admin(at)lists(dot)postgresql(dot)org
Subject: Re: pg_dump: WARNING: could not find operator
Date: 2023-07-13 04:26:58
Message-ID: 2797947.1689222418@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

"Edward J. Sabol" <edwardjsabol(at)gmail(dot)com> writes:
> On Jul 12, 2023, at 11:08 PM, Ron <ronljohnsonjr(at)gmail(dot)com> wrote:
>> Will they automagically disappear when you restore the pg_dump?

> Yeah, that's what Tom Lane said, but I'm not planning to restore the pg_dump (unless something catastrophic happens). I'm planning to use "pg_upgrade --link".

As far as catalog data is concerned, pg_upgrade is the same as
pg_dumpall + restore.

regards, tom lane

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message Charles Schultz 2023-07-13 11:43:23 Training for seasoned DBAs new to postgres?
Previous Message Edward J. Sabol 2023-07-13 04:08:42 Re: pg_dump: WARNING: could not find operator