Opened 4 years ago
Closed 4 years ago
#4756 closed defect (wontfix)
PostGIS 3.0.2 is bundled with GDAL 2.4.4 that has ogr2ogr incompatible with PG12
Reported by: | mlt | Owned by: | strk |
---|---|---|---|
Priority: | medium | Milestone: | PostGIS 3.0.3 |
Component: | build | Version: | 3.0.x |
Keywords: | ogr2ogr, gdal, windows, win32, packaging | Cc: |
Description
PostGIS 3.0.2 available for download for PostgreSQL 12 and Windows at http://download.osgeo.org/postgis/windows/pg12/ has ogr2ogr that is built with GDAL 2.4.4 that is incompatible with PostgreSQL 12. https://github.com/OSGeo/gdal/issues/1692 . I presume newer GDAL should be packaged for Windows.
Change History (2)
comment:1 by , 4 years ago
Component: | postgis → build/upgrade/install |
---|---|
Owner: | changed from | to
comment:2 by , 4 years ago
Resolution: | → wontfix |
---|---|
Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
mlt I do plan to release the upcoming PostGIS 3.0.3 with GDAL 3.0.4 or GDAL 3.1. However I'm not sure which problem you are having here. I suspect my upgrade won't fix your issue.
The ogr2ogr that is distributed with windows PostGIS Bundle doesn't even have PostgreSQL driver packaged in with it. I did that intentionally because then I'd have possible issues with libpq that is distributed with each PostgreSQL version and I use the same GDAL package across all the PostGIS bundle PostgreSQL versions.
You can verify with below that PostgreSQL is not a supported driver
The ogr2ogr is pretty barebones and was there just cause I needed to verify drivers before ogrfdw introduced option to list drivers.
If you need an ogr2ogr that contains postgresql support — I highly recommend using one of Tamas package https://www.gisinternals.com/. His is what I use when I need PostgreSQL support or some other non-built in drivers. He also has versions built whenever a change in GDAL.
Alternative would be to use the Foreign Data Wrapper (ogr_fdw) which I find easier to use than fussing with ogr2ogr.
The issue I pointed out in that GDAL ticket doesn't affect the ogr_fdw since ogr_fdw doesn't rely on the PostgreSQL plumbing in GDAL. It has it's own plumbing which is a bit different from postgresql to postgresql.