| From: | Alexander Korotkov <aekorotkov(at)gmail(dot)com> |
|---|---|
| To: | Alexander Korotkov <akorotkov(at)postgresql(dot)org> |
| Cc: | 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-29 20:53:14 |
| Message-ID: | CAPpHfdtc8ZoQEURknPu=6A08FjTixN1ZvneiuyNOPWDZ0G+SZw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers |
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.
> Add GiST indexes for multiranges
>
> This commits adds a pretty trivial way for multirange indexing: approximate
> multirange as union range with no gaps. New multiranges opclass shares the
> majority of functions with ranges opclass.
>
> This is not an ideal way to index multirages, but something we can easily have.
------
Regards,
Alexander Korotkov
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2020-12-29 23:03:07 | pgsql: Suppress log spam from multiple reports of SIGQUIT shutdown. |
| Previous Message | Alexander Korotkov | 2020-12-29 20:45:42 | pgsql: Implement operators for checking if the range contains a multira |