[raster] PostGIS raster && operator not installed when GSERIALIZED_ON

[robe]

When GSERIALIZED is ON, raster && operator still built with geometry_gist_sel which is only valid for our non-GSERIALIZED.

Pierre et al,

Mind if I fix this one?

[robe]

Paul,

Maybe you should tackle this one or tell us what needs to be done here.

The issue is raster operator is defined like this:

CREATE OPERATOR && (
    LEFTARG = raster, RIGHTARG = raster, PROCEDURE = st_overlap,
    COMMUTATOR = '&&',
    RESTRICT = geometry_gist_sel, JOIN = geometry_gist_joinsel
    );

My first thought was to include the gserialized header in there and then change to this to match the way you have geometry:

#ifdef GSERIALIZED_ON CREATE OPERATOR && (

LEFTARG = raster, RIGHTARG = raster, PROCEDURE = st_overlap, COMMUTATOR = '&&', RESTRICT = contsel, JOIN = contjoinsel );

#else CREATE OPERATOR && (

LEFTARG = raster, RIGHTARG = raster, PROCEDURE = st_overlap, COMMUTATOR = '&&', RESTRICT = geometry_gist_sel, JOIN = geometry_gist_joinsel );

#endif

But I've never understood the difference between contsel and geometry_gist_sel and why I wouldn't just go with contsel, contjoinsel in both the GSERIALIZED ON/OF cases and then not have to include the header file.

[Bborie Park]

I didn't see this ticket before I made this exact change in r7394. With this change and a few more due to the maximum srid permitted in GSERIALIZED, the raster regressions pass (minus the existing issues with MapAlgebra).

[pramsey]

Is this ticket now dead? If so, close.

[robe]

yes it's dead.