Re: BF failure: could not open relation with OID XXXX while querying pg_views
Dean Rasheed <dean.a.rasheed@gmail.com>
From: Dean Rasheed <dean.a.rasheed@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Tomas Vondra <tomas.vondra@2ndquadrant.com>,
Thomas Munro <thomas.munro@gmail.com>, Peter Eisentraut <peter.eisentraut@2ndquadrant.com>, pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2019-09-15T09:16:30Z
Lists: pgsql-hackers
On Sat, 14 Sep 2019 at 05:25, Tom Lane <tgl@sss.pgh.pa.us> wrote: > > Tomas Vondra <tomas.vondra@2ndquadrant.com> writes: > > 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. > > Ping? We're still getting intermittent failures of this ilk, eg > > https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=dragonet&dt=2019-09-14%2003%3A37%3A03 > > With v12 release approaching, I'd like to not have failures > like this in a released branch. > Ah sorry, I missed this thread before. As author of that commit, it's really on me to fix it, and the cause seems pretty clear-cut, so I'll aim to get that done today. Regards, Dean
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