Re: BRIN range operator class - Mailing list pgsql-hackers

From Emre Hasegeli
Subject Re: BRIN range operator class
Date
Msg-id CAE2gYzwY8y1LfRk9MHc09XXLTPrqZnM8oJEqhgWfat8NV7OQZw@mail.gmail.com
Whole thread Raw
In response to Re: BRIN range operator class  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Responses Re: BRIN range operator class  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Re: BRIN range operator class  (Alvaro Herrera <alvherre@2ndquadrant.com>)
List pgsql-hackers
> After looking at 05 again, I don't like the "same as %" business.
> Creating a whole new class of exceptions is not my thing, particularly
> not in a regression test whose sole purpose is to look for exceptional
> (a.k.a. "wrong") cases.  I would much rather define the opclasses for
> those two datatypes using the existing @> operators rather than create
> && operators for this purpose.  We can add a note to the docs, "for
> historical reasons the brin opclass for datatype box/point uses the <@
> operator instead of &&", or something like that.

I worked around this by adding point <@ box operator as the overlap
strategy and removed additional && operators.

> AFAICS this is just some pretty small changes to patches 05 and 06.
> Will you please resubmit?

New series of patches are attached.  Note that
brin-inclusion-v08-04-fix-brin-deform-tuple.patch is the one from you.

Attachment

pgsql-hackers by date:

Previous
From: Emre Hasegeli
Date:
Subject: Re: BRIN range operator class
Next
From: Volker Aßmann
Date:
Subject: Re: Disabling trust/ident authentication configure option