Re: BF failure: could not open relation with OID XXXX while querying pg_views - Mailing list pgsql-hackers

From Tom Lane
Subject Re: BF failure: could not open relation with OID XXXX while querying pg_views
Date
Msg-id 14249.1568435120@sss.pgh.pa.us
Whole thread Raw
In response to Re: BF failure: could not open relation with OID XXXX while queryingpg_views  (Tomas Vondra <tomas.vondra@2ndquadrant.com>)
Responses Re: BF failure: could not open relation with OID XXXX while querying pg_views
List pgsql-hackers
Tomas Vondra <tomas.vondra@2ndquadrant.com> writes:
> On Wed, Aug 14, 2019 at 05:24:26PM +1200, Thomas Munro wrote:
>> On Wed, Aug 14, 2019 at 5:06 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
>>> Oh, hmm --- yeah, that should mean it's safe.  Maybe somebody incautiously
>>> changed one of the other tests that run concurrently with "rules"?

>> Looks like stats_ext.sql could be the problem.  It creates and drops
>> priv_test_view, not in a schema.  Adding Dean, author of commit
>> d7f8d26d.

> Yeah, that seems like it might be the cause. I'll take a look at fixing
> this, probably by creating the view in a different schema.

Ping?  We're still getting intermittent failures of this ilk, eg

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=dragonet&dt=2019-09-14%2003%3A37%3A03

With v12 release approaching, I'd like to not have failures
like this in a released branch.

            regards, tom lane



pgsql-hackers by date:

Previous
From: Amit Kapila
Date:
Subject: Re: [HACKERS] [PATCH] pageinspect function to decode infomasks
Next
From: Michael Paquier
Date:
Subject: Re: [HACKERS] CLUSTER command progress monitor