Raw Package Information

Package: postgresql-11-ogr-fdw
Source: pgsql-ogr-fdw
Version: 1.1.3-1.pgdg22.04+1
Architecture: amd64
Maintainer: Debian GIS Project <pkg-grass-devel@lists.alioth.debian.org>
Installed-Size: 246
Depends: postgresql-11, libc6 (>= 2.34), libgdal30 (>= 2.2.0), postgresql-11-jit-llvm (>= 14)
Provides: postgresql-ogr-fdw
Homepage: https://github.com/pramsey/pgsql-ogr-fdw
Priority: optional
Section: database
Filename: pool/main/p/pgsql-ogr-fdw/postgresql-11-ogr-fdw_1.1.3-1.pgdg22.04+1_amd64.deb
Size: 100572
SHA256: 81b8e6a0a2505ca3c166d278333672f72370390ba668e8e402c76c7357e323bb
SHA1: d7c023e3dfd6ef4e1a2e016de7b314fe15bbe650
MD5sum: 3eb4b1a2ca158a9f2b74f1df5ece31e1
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
 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.