From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
Cc: | Thomas Munro <thomas(dot)munro(at)gmail(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:05:59 |
Message-ID: | 12000.1565759159@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> writes:
> On 2019-08-14 05:52, Tom Lane wrote:
>> Thomas Munro <thomas(dot)munro(at)gmail(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Thomas Munro | 2019-08-14 05:24:26 | Re: BF failure: could not open relation with OID XXXX while querying pg_views |
Previous Message | Peter Eisentraut | 2019-08-14 05:00:27 | Re: BF failure: could not open relation with OID XXXX while querying pg_views |