[postgis-devel] RFC: Remove mmin and mmax from GBOX

[Paul Ramsey]

On Mon, Jul 11, 2011 at 8:00 AM, Mark Cave-Ayland
<mark.cave-ayland at siriusit.co.uk> wrote:
> I agree you bring up a valid point here; how do we control how many
> dimensions should be indexed? It seems to me that we both see that there is
> something lacking in the current setup, but have different ideas on how to
> go about solving this.

The big hammer is an opclass for every dimensional index and
associated operators. So

2d => g1 && g2
3d => g1 &&& g2
4d => g1 &&&& g2

As it stands now my development path is

2d => g1 && g2
nd => g1 &&& g2

where the nd index creates boxes in as much dimensional space as is
necessary (ala the cube index)

P.