Re: BF failure: could not open relation with OID XXXX while querying pg_views
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Cc: Thomas Munro <thomas.munro@gmail.com>,
pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2019-08-14T05:05:59Z
Lists: pgsql-hackers
Peter Eisentraut <peter.eisentraut@2ndquadrant.com> writes:
> On 2019-08-14 05:52, Tom Lane wrote:
>> Thomas Munro <thomas.munro@gmail.com> writes:
>>> 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".
> This test file is set up to create everything in the "collate_tests"
> schema. Is that not working correctly?
Oh, hmm --- yeah, that should mean it's safe. Maybe somebody incautiously
changed one of the other tests that run concurrently with "rules"?
regards, tom lane
Commits
-
Fix intermittent self-test failures caused by the stats_ext test.
- 5576cbc8ff1f 12.0 landed
- 3d9a3ef5cbfc 13.0 landed
-
Add security checks to the multivariate MCV estimation code.
- d7f8d26d9f4c 12.0 cited