From: | Wells Oliver <wells(dot)oliver(at)gmail(dot)com> |
---|---|
To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
Cc: | pgsql-admin <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: Odd pg dump error: cache lookup failure |
Date: | 2020-08-24 20:06:59 |
Message-ID: | CAOC+FBXosgRbSi-A+VLP8t5pmErEnP3M8aRJJ1z5HcyhvQM_eA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
12.4. Both of those queries return no rows, with and without those options
set.
We do do some nightly processing of data during the same window, in which
views are re-materialized: would that cause this issue? No non-temporary
tables are dropped or re-created, though.
On Mon, Aug 24, 2020 at 12:08 PM Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
wrote:
> On 2020-Aug-24, Wells Oliver wrote:
>
> > My pg_dump scripts have been bombing lately, and this is the error I see
> a
> > bit into the backup process:
> >
> > pg_dump: error: query failed: ERROR: cache lookup failed for attribute 1
> > of relation 1152770777
>
> What pg version is this, and can you run the query directly using psql
> and have it throw the same error? What do
> select * from pg_class where oid = '1152770777'
> and
> select * from pg_attribute where attrelid = '1152770777'
> show? If the latter fails to show an entry for attnum=1, does it
> magically appear if you do
> SET enable_indexscan=off;
> SET enable_bitmapscan=off;
> prior to running the query?
>
> --
> Álvaro Herrera https://www.2ndQuadrant.com/
> PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
>
--
Wells Oliver
wells(dot)oliver(at)gmail(dot)com <wellsoliver(at)gmail(dot)com>
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2020-08-24 23:13:38 | Re: Odd pg dump error: cache lookup failure |
Previous Message | Alvaro Herrera | 2020-08-24 19:08:53 | Re: Odd pg dump error: cache lookup failure |