[proposal] improve postgis support ( latest geos, proj, gdal, sfcgal )

now the SELECT PostGIS_Full_Version();

                        postgis_full_version                                                                
                                           
------------------------------------------------------------------------------------------------------ 

POSTGIS="3.3.2 4975da8" [EXTENSION] PGSQL="150" 
    GEOS="3.9.0-CAPI-1.16.2" 
    SFCGAL="1.3.8" 
    PROJ="7.2.1" 
    GDAL="GDAL 3.2.2,
    released 2021/03/05" LIBXML="2.9.10" 
    LIBJSON="0.15" LIBPROTOBUF="1.3.3 " 
    WAGYU="0.5.0 (Internal)" TOPOLOGY RASTER
(1 row)

and I think it could be improved.

If most packages are being built in a container, I think it might be worthwhile to use the latest of some of the postgis-related packages.

imho: You can check the postgis/postgis:15-master Dockerfile ;

  • SFCGAL 1.4 ( with cgal header only )
  • Geos, GDAL, PROJ build
  • postgis Test

At this moment, the vast majority of such libraries came from Debian. However, such changes require compiling them manually. I don’t think that such an update will benefit us somehow.

1 Like

at least the current compiled SFCGAL can be upgraded

  • libcgal-dev can be removed. ;
  • and modify the code to : SFCGAL 1.4.1 + CGAL 5.5.2 header only

I can also do the Pull Request …

I don’t think that such an update will benefit us somehow.

Although I acknowledge that this is not the most critical point in the NEON project, which would require high priority or significant developer resources, it is worth mentioning that the postgis, geos, gdal, and proj libraries are developed at a faster pace than the more conservative Debian. Furthermore, if some of the packages are already compiled, having an up-to-date PostGIS ecosystem could be one of the advantages of the NEON project compared to other Debian-based Postgres cloud services.

disclaimer: I am a GitHub - postgis/docker-postgis: Docker image for PostGIS contributor;

1 Like

Alternatives:

  1. ) probably a custom docker image option would solve my problem.

~ “allow users to provide their own docker image that includes the extensions they want, or something like that”

2.) The other alternative is adding debian:bookworm based image.
It has a newer Geos (3.11 )

so I can select

  • Postgres:15 - bullseye ( → this is the current image )
  • Postgres:15 - bookworm - testing

Feel free to contribute

yes, we have such ideas

I’d prefer to stay on the current base image.

2 Likes

Probably an upgrade to Debian 12 will solve most of the problems. :slight_smile:

  • Debian 12.0 “Bookworm” ( Planned For Release On 10 )