Re: pgsql: Add support of multirange matching to the existing range GiST in

On Wed, Dec 30, 2020 at 10:04 AM Michael Paquier <michael(at)paquier(dot)xyz> wrote:
> On Tue, Dec 29, 2020 at 11:53:14PM +0300, Alexander Korotkov wrote:
> > On Tue, Dec 29, 2020 at 11:45 PM Alexander Korotkov <akorotkov(at)postgresql(dot)org> wrote:
> >> Add support of multirange matching to the existing range GiST indexes
> >
> > I accidentally squash here a commit which implements GiST multirange
> > indexes. That commit was intended to go separately with its own
> > commit message below. Sorry for that.
>
> 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.

> Please note that you should add a "Discussion:" in those commits to be
> able to track down where this stuff has been discussed.

My oversight, sorry.

------
Regards,
Alexander Korotkov