[postgis-devel] Making SFCGAL mandatory

[Darafei "Komяpa" Praliaskouski]

>
>
> > 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.
> >
>
> Probably. I don't remember exactly why we chose to use GUC. Functions in
> their own schema like sfcgal.ST_Intersects() could have been a solution
> as well (?)


Can we change that for PostGIS 3.0, so that instead of
postgis.backend=sfcgal one will set search_path=postgis_sfcgal,public?

This way postgis_sfcgal will be completely separate from postgis.so, and
question on whether to demand presence of sfcgal during build will be much
easier.
-- 
Darafei Praliaskouski
Support me: http://patreon.com/komzpa
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-devel/attachments/20181115/2ca61f22/attachment.html>