[postgis-devel] Making SFCGAL mandatory

Paul Ramsey pramsey at cleverelephant.ca
Wed Nov 14 10:51:18 PST 2018



> On Nov 14, 2018, at 10:36 AM, Raúl Marín Rodríguez <rmrodriguez at carto.com> wrote:
> 
> > But at some level it should be possible - so if someone wants to drop in boost-geometry they could, and won't have to be a part of PostGIS codebase. 
> 
> And I guess this means we could have a GEOS-less build (would it provide something like 'postgis-backend-geos'?).
> 
> Would this kind of runtime selection/dependency make it harder to debug reported issues? If so (my guess), I'd tread carefully.

More to the point, I think, is that adding levels of indirection increases the complexity of the whole thing, for relatively niche use cases. We had a lot of debugging issues arise out of the backend selection GUC, and I bet approximately nobody uses it. It would have been far more effective to just have the 6 functions in question added a ST_IntersectsCGAL() etc, etc, in terms of the real usage of PostGIS. The backend switch was too smart by 1/2.

P

> 
> 
> -- 
> Raúl Marín Rodríguez 
> carto.com <http://carto.com/>
> 
> 
> _______________________________________________
> postgis-devel mailing list
> postgis-devel at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/postgis-devel

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-devel/attachments/20181114/f1d95603/attachment-0001.html>


More information about the postgis-devel mailing list