Package: postgresql-13-ogr-fdw Source: pgsql-ogr-fdw Version: 1.1.7-1~exp1.pgdg22.04+1 Architecture: amd64 Maintainer: Debian GIS Project Installed-Size: 271 Depends: postgresql-13, postgresql-13-jit-llvm (>= 15), libc6 (>= 2.34), libgdal30 (>= 2.2.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-13-ogr-fdw_1.1.7-1~exp1.pgdg22.04+1_amd64.deb Size: 109252 SHA256: 31c62124162f7cbee598b8a06abb333ab8b5dc59d8c3949f3ffa8c9ac6ab0f62 SHA1: 4f6dd92412465a636267518b38dff9ee5f27e98d MD5sum: cda30d10d917ec5ce23ac62ec9a33a10 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.