Re: Odd pg dump error: cache lookup failure

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Wells Oliver <wells(dot)oliver(at)gmail(dot)com>
Cc: Stephen Frost <sfrost(at)snowman(dot)net>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, pgsql-admin <pgsql-admin(at)postgresql(dot)org>
Subject: Re: Odd pg dump error: cache lookup failure
Date: 2020-08-25 19:33:29
Message-ID: 2762015.1598384009@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Wells Oliver <wells(dot)oliver(at)gmail(dot)com> writes:
> And refreshing materialized views during the dump process wouldn't cause
> this?

matviews can't be part of inheritance trees AFAIR, so we'd need some
other theory to explain it that way.

Did you try tracing down the table OID mentioned in the error to see
if it still exists, and if so what is it?

regards, tom lane

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Wells Oliver 2020-08-25 19:44:50 Re: Odd pg dump error: cache lookup failure
Previous Message Wells Oliver 2020-08-25 19:06:23 Re: Odd pg dump error: cache lookup failure