| From: | Wells Oliver <wells(dot)oliver(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| 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:44:50 |
| Message-ID: | CAOC+FBXLBO+r=9xF2c5E5vT7jGsqFq49LJ+Ka4Cqn16J38SLYQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
It doesn't exist any longer, which lead me to try to think of things that
might be dropped during the dump process.
On Tue, Aug 25, 2020 at 12:33 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> 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
>
--
Wells Oliver
wells(dot)oliver(at)gmail(dot)com <wellsoliver(at)gmail(dot)com>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2020-08-25 19:51:03 | Re: Odd pg dump error: cache lookup failure |
| Previous Message | Tom Lane | 2020-08-25 19:33:29 | Re: Odd pg dump error: cache lookup failure |