[postgis-devel] [PostGIS] #992: [raster] PostGIS raster && operator not installed when GSERIALIZED_ON
PostGIS
trac at osgeo.org
Thu May 26 18:54:08 PDT 2011
#992: [raster] PostGIS raster && operator not installed when GSERIALIZED_ON
----------------------------+-----------------------------------------------
Reporter: robe | Owner: pramsey
Type: defect | Status: new
Priority: blocker | Milestone: PostGIS 2.0.0
Component: postgis raster | Version: trunk
Keywords: |
----------------------------+-----------------------------------------------
Changes (by robe):
* owner: pracine => pramsey
Comment:
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.
--
Ticket URL: <http://trac.osgeo.org/postgis/ticket/992#comment:3>
PostGIS <http://trac.osgeo.org/postgis/>
The PostGIS Trac is used for bug, enhancement & task tracking, a user and developer wiki, and a view into the subversion code repository of PostGIS project.
More information about the postgis-devel
mailing list