Re: range_agg - Mailing list pgsql-hackers

From Alexander Korotkov
Subject Re: range_agg
Date
Msg-id CAPpHfdvwY0kJM0n6GYrxQTz=9efj1qyu+cTv70vn_8pgpEQ8aw@mail.gmail.com
Whole thread Raw
In response to Re: range_agg  (Alexander Korotkov <aekorotkov@gmail.com>)
Responses Re: range_agg  (Alexander Korotkov <aekorotkov@gmail.com>)
List pgsql-hackers
On Mon, Nov 30, 2020 at 10:35 PM Alexander Korotkov
<aekorotkov@gmail.com> wrote:
> On Sun, Nov 29, 2020 at 11:53 PM Paul A Jungwirth
> <pj@illuminatedcomputing.com> wrote:
> >
> > On Sun, Nov 29, 2020 at 11:43 AM Alexander Korotkov
> > <aekorotkov@gmail.com> wrote:
> > > Thank you.  Could you please, update doc/src/sgml/catalogs.sgml,
> > > because pg_type and pg_range catalogs are updated.
> >
> > Attached! :-)
>
> You're quick, thank you.  Please, also take a look at cfbot failure
> https://travis-ci.org/github/postgresql-cfbot/postgresql/builds/746623942
> I've tried to reproduce it, but didn't manage yet.

Got it.  type_sanity test fails on any platform, you just need to
repeat "make check" till it fails.

The failed query checked consistency of range types, but it didn't
take into account ranges of domains and ranges of records, which are
exercised by multirangetypes test running in parallel.  We could teach
this query about such kinds of ranges, but I think that would be
overkill, because we're not going to introduce such builtin ranges
yet.  So, I'm going to just move multirangetypes test into another
group of parallel tests.

------
Regards,
Alexander Korotkov



pgsql-hackers by date:

Previous
From: "David G. Johnston"
Date:
Subject: Re: Change JOIN tutorial to focus more on explicit joins
Next
From: Tom Lane
Date:
Subject: Re: [doc] remove reference to pg_dump pre-8.1 switch behaviour