| From: | Alexander Korotkov <aekorotkov(at)gmail(dot)com> |
|---|---|
| To: | Michael Paquier <michael(at)paquier(dot)xyz> |
| Cc: | Alexander Korotkov <akorotkov(at)postgresql(dot)org>, pgsql-committers <pgsql-committers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: pgsql: Add support of multirange matching to the existing range GiST in |
| Date: | 2020-12-30 17:41:10 |
| Message-ID: | CAPpHfdsmuF7=R=ZW+Yc7TFt8=grLzzB_q3rDbx6=GafTrE2ZFg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers |
On Wed, Dec 30, 2020 at 11:08 AM Alexander Korotkov
<aekorotkov(at)gmail(dot)com> wrote:
> On Wed, Dec 30, 2020 at 10:04 AM Michael Paquier <michael(at)paquier(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2020-12-30 17:56:34 | pgsql: Use setenv() in preference to putenv(). |
| Previous Message | Alexander Korotkov | 2020-12-30 17:39:58 | pgsql: Fix selectivity estimation @> (anymultirange, anyrange) operator |