On Wed, Dec 30, 2020 at 11:08 AM Alexander Korotkov
wrote:
> On Wed, Dec 30, 2020 at 10:04 AM Michael Paquier 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 membe
On Wed, Dec 30, 2020 at 10:04 AM Michael Paquier 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
> > wrote:
> >> Add support of multirange matching to the existing range GiST indexes
> >
> > I accidentally squas
On Tue, Dec 29, 2020 at 11:53:14PM +0300, Alexander Korotkov wrote:
> On Tue, Dec 29, 2020 at 11:45 PM Alexander Korotkov
> wrote:
>> Add support of multirange matching to the existing range GiST indexes
>
> I accidentally squash here a commit which implements GiST multirange
> indexes. That co
On Tue, Dec 29, 2020 at 11:45 PM Alexander Korotkov
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
Add support of multirange matching to the existing range GiST indexes
6df7a9698b has introduced a set of operators between ranges and multiranges.
Existing GiST indexes for ranges could easily support majority of them.
This commit adds support for new operators to the existing range GiST indexes.
