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

From: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com>
Cc: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: BF failure: could not open relation with OID XXXX while querying pg_views
Date: 2019-08-14 05:24:26
Message-ID: CA+hUKGL=OzL3wSUKz+pp+RgXDVkqf=aHgJMdoL=66o-OWQ7Knw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Aug 14, 2019 at 5:06 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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.

--
Thomas Munro
https://enterprisedb.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2019-08-14 05:59:16 use of the term "verifier" with SCRAM
Previous Message Tom Lane 2019-08-14 05:05:59 Re: BF failure: could not open relation with OID XXXX while querying pg_views