Re: BF failure: could not open relation with OID XXXX while querying pg_views
Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
From: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
To: Tom Lane <tgl@sss.pgh.pa.us>, Thomas Munro <thomas.munro@gmail.com>
Cc: pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2019-08-14T05:00:27Z
Lists: pgsql-hackers
On 2019-08-14 05:52, Tom Lane wrote:
> Thomas Munro <thomas.munro@gmail.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".
This test file is set up to create everything in the "collate_tests"
schema. Is that not working correctly?
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
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