Re: BF failure: could not open relation with OID XXXX while querying pg_views

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
Subject: Re: BF failure: could not open relation with OID XXXX while querying pg_views
Date: 2019-08-14 03:52:54
Message-ID: 8670.1565754774@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Thomas Munro <thomas(dot)munro(at)gmail(dot)com> writes:
> Here are three strange recent failures in the "rules" test:
> ...
> They all raised "ERROR: could not open relation with OID <varies>"
> while running:
> SELECT viewname, definition FROM pg_views
> WHERE schemaname IN ('pg_catalog', 'public')
> ORDER BY viewname;

I think the problem is probably that Peter ignored this bit of advice
in parallel_schedule:

# rules cannot run concurrently with any test that creates
# a view or rule in the public schema

when he inserted "collate.linux.utf8" concurrently with "rules".

(I suspect BTW that the point is not so much that you better not
*create* such an object, as that you better not *drop* it concurrently
with that query.)

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2019-08-14 04:39:11 Re: Regression test failure in regression test temp.sql
Previous Message Michael Paquier 2019-08-14 03:00:25 Re: using explicit_bzero