[Tile-serving] [osm2pgsql-dev/osm2pgsql] Refuse to import if PostGIS's core procedures aren't updated. (Discussion #2140)

[mboeringa]

I noticed osm2pgsql currently happily starts an import session with outdated PostGIS core procedures. While this may not be directly critical, and somewhat out of the responsibility of osm2pgsql, I still think it is good practice to refuse import in such a configuration.

I run some own software written in Python, and have been bitten by this issue in my own code, and have since adjusted my own tool to issue a warning if outdated PostGIS core procedures are detected upon start up, and block processing if so.

I find this really helpful to not forget to update the core procedures after a PostGIS update. Especially novice users are usually unaware of the need to do so, and may run into issues.

This situation can be easily detected by parsing the string returned by `SELECT PostGIS_Full_Version();`, which often is already a requirement in software development related to PostGIS to detect other (version) incompatibilities.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/osm2pgsql-dev/osm2pgsql/discussions/2140
You are receiving this because you are subscribed to this thread.

Message ID: <osm2pgsql-dev/osm2pgsql/repo-discussions/2140 at github.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/tile-serving/attachments/20240215/c054c1d9/attachment.htm>