On Sun, 15 Sep 2019 at 12:20, Tomas Vondra wrote:
>
> On Sun, Sep 15, 2019 at 11:27:19AM +0100, Dean Rasheed wrote:
> >On Sun, 15 Sep 2019 at 11:11, Tomas Vondra
> >wrote:
> >>
> >> On Sun, Sep 15, 2019 at 10:16:30AM +0100, Dean Rasheed wrote:
> >> >
> >> >Ah sorry, I missed this thread before.
On Sun, Sep 15, 2019 at 11:27:19AM +0100, Dean Rasheed wrote:
On Sun, 15 Sep 2019 at 11:11, Tomas Vondra wrote:
On Sun, Sep 15, 2019 at 10:16:30AM +0100, Dean Rasheed wrote:
>
>Ah sorry, I missed this thread before. As author of that commit, it's
>really on me to fix it, and the cause seems pr
On Sun, 15 Sep 2019 at 11:11, Tomas Vondra wrote:
>
> On Sun, Sep 15, 2019 at 10:16:30AM +0100, Dean Rasheed wrote:
> >
> >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.
>
On Sat, 14 Sep 2019 at 05:25, Tom Lane wrote:
>
> Tomas Vondra 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 wrote:
> >>> Oh, hmm --- yeah, that should mean it's safe. Maybe somebody incautiously
> >>> changed one of the
On Sun, Sep 15, 2019 at 10:16:30AM +0100, Dean Rasheed wrote:
On Sat, 14 Sep 2019 at 05:25, Tom Lane wrote:
Tomas Vondra 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 wrote:
>>> Oh, hmm --- yeah, that should mean it's safe
Tomas Vondra 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 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 l
On Wed, Aug 14, 2019 at 05:24:26PM +1200, Thomas Munro wrote:
On Wed, Aug 14, 2019 at 5:06 PM Tom Lane 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 pro
On Wed, Aug 14, 2019 at 5:06 PM Tom Lane 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.
Peter Eisentraut writes:
> On 2019-08-14 05:52, Tom Lane wrote:
>> Thomas Munro writes:
>>> They all raised "ERROR: could not open relation with OID "
>>> while running:
>>> SELECT viewname, definition FROM pg_views
>>> WHERE schemaname IN ('pg_catalog', 'public')
>>> ORDER BY viewname;
>> I th
On 2019-08-14 05:52, Tom Lane wrote:
> Thomas Munro writes:
>> Here are three strange recent failures in the "rules" test:
>> ...
>> They all raised "ERROR: could not open relation with OID "
>> while running:
>> SELECT viewname, definition FROM pg_views
>> WHERE schemaname IN ('pg_catalog', 'p
Thomas Munro writes:
> Here are three strange recent failures in the "rules" test:
> ...
> They all raised "ERROR: could not open relation with OID "
> while running:
> SELECT viewname, definition FROM pg_views
> WHERE schemaname IN ('pg_catalog', 'public')
> ORDER BY viewname;
I think the pr
Hi,
Here are three strange recent failures in the "rules" test:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=blenny&dt=2019-08-13%2022:19:27
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=alewife&dt=2019-07-27%2009:39:05
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=
12 matches
Mail list logo