Package: postgresql-17-ogr-fdw Source: pgsql-ogr-fdw Version: 1.1.9-1.pgdg26.04+1 Architecture: amd64 Maintainer: Debian GIS Project Installed-Size: 245 Depends: postgresql-17, libc6 (>= 2.38), libgdal39 (>= 3.7.0) Provides: postgresql-ogr-fdw Homepage: https://github.com/pramsey/pgsql-ogr-fdw Priority: optional Section: database Filename: pool/main/p/pgsql-ogr-fdw/postgresql-17-ogr-fdw_1.1.9-1.pgdg26.04+1_amd64.deb Size: 90840 SHA512: 6072bf9452f52a6fec3a36bbeb24b33ad689507e1167f129103e97160997ac5f6fe35d34091a03ba3c4a12bfba882f974b8a18d060c6a31215d11df29f699d57 SHA256: d850ab4c20f32a95f0178353a93bc2e6d3d2b3b7f0fa7b56ffc33476afbab123 SHA1: cb02da224c1971fa4177006c652921f1c29b9c85 MD5sum: 72aa8739df97468186f0b6f3cabe6f91 Description: PostgreSQL foreign data wrapper for OGR OGR is the vector half of the GDAL spatial data access library. It allows access to a large number of GIS data formats using a simple C API for data reading and writing. Since OGR exposes a simple table structure and PostgreSQL foreign data wrappers allow access to table structures, the fit seems pretty perfect. . This implementation currently has the following limitations: * Only non-spatial query restrictions are pushed down to the OGR driver. PostgreSQL foreign data wrappers support delegating portions of the SQL query to the underlying data source, in this case OGR. This implementation currently pushes down only non-spatial query restrictions, and only for the small subset of comparison operators (>, <, <=, >=, =) supported by OGR. * Spatial restrictions are not pushed down. OGR can handle basic bounding box restrictions and even (for some drivers) more explicit intersection restrictions, but those are not passed to the OGR driver yet. * OGR connections every time Rather than pooling OGR connections, each query makes (and disposes of) two new ones, which seems to be the largest performance drag at the moment for restricted (small) queries. * All columns are retrieved every time. PostgreSQL foreign data wrappers don't require all columns all the time, and some efficiencies can be gained by only requesting the columns needed to fulfill a query. This would be a minimal efficiency improvement, but can be removed given some development time, since the OGR API supports returning a subset of columns.