Re: pgsql: Add support of multirange matching to the existing range GiST in - Mailing list pgsql-committers

From Alexander Korotkov
Subject Re: pgsql: Add support of multirange matching to the existing range GiST in
Date
Msg-id CAPpHfdsmuF7=R=ZW+Yc7TFt8=grLzzB_q3rDbx6=GafTrE2ZFg@mail.gmail.com
Whole thread Raw
In response to Re: pgsql: Add support of multirange matching to the existing range GiST in  (Alexander Korotkov <aekorotkov@gmail.com>)
List pgsql-committers
On Wed, Dec 30, 2020 at 11:08 AM Alexander Korotkov
<aekorotkov@gmail.com> wrote:
> On Wed, Dec 30, 2020 at 10:04 AM Michael Paquier <michael@paquier.xyz> wrote:
> > The buildfarm got a bit angry after this commit:
> > https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=clam&dt=2020-12-30%2003%3A00%3A11
> >
> > Here is a diff from member clam, that uses ppc64:
> >  select count(*) from test_multirange_gist where mr <@
> >  int4range(10,50);
> > - count
> > --------
> > -   500
> > -(1 row)
> > -
> > +ERROR:  unknown multirange operator 4540
> >
> > This points out to OID_RANGE_MULTIRANGE_CONTAINED_OP.
>
> Thank you for pointing this out.  I'll investigate this.

Should be fixed by 62097a4cc8.

------
Regards,
Alexander Korotkov



pgsql-committers by date:

Previous
From: Alexander Korotkov
Date:
Subject: pgsql: Fix selectivity estimation @> (anymultirange, anyrange) operator
Next
From: Tom Lane
Date:
Subject: pgsql: Use setenv() in preference to putenv().