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

Поиск
Список
Период
Сортировка
От Dean Rasheed
Тема Re: BF failure: could not open relation with OID XXXX while querying pg_views
Дата
Msg-id CAEZATCVNNYv6cwbQ6oueDXdJh61qu8G1JNOVmQRO_X6=wruDjA@mail.gmail.com
обсуждение исходный текст
Ответ на Re: BF failure: could not open relation with OID XXXX while querying pg_views  (Tom Lane <tgl@sss.pgh.pa.us>)
Список 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



В списке pgsql-hackers по дате отправления:

Предыдущее
От: Andrey Borodin
Дата:
Сообщение: Re: Efficient output for integer types
Следующее
От: Tomas Vondra
Дата:
Сообщение: Re: BF failure: could not open relation with OID XXXX while queryingpg_views