Horton

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

Tomas Vondra <tomas.vondra@2ndquadrant.com>

View thread View on postgr.es
From: Tomas Vondra <tomas.vondra@2ndquadrant.com>
To: Thomas Munro <thomas.munro@gmail.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, Dean Rasheed <dean.a.rasheed@gmail.com>, Peter Eisentraut <peter.eisentraut@2ndquadrant.com>, pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2019-08-15T22:37:48Z
Lists: pgsql-hackers 
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.

regards

-- 
Tomas Vondra                  http://www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

Commits

  1. Fix intermittent self-test failures caused by the stats_ext test.

  2. Add security checks to the multivariate MCV estimation code.