Package: postgresql-16-ogr-fdw
Source: pgsql-ogr-fdw
Version: 1.1.9-1.pgdg26.04+1
Architecture: amd64
Maintainer: Debian GIS Project <pkg-grass-devel@lists.alioth.debian.org>
Installed-Size: 245
Depends: postgresql-16, 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-16-ogr-fdw_1.1.9-1.pgdg26.04+1_amd64.deb
Size: 90792
SHA512: b17a57661b123f5ff6f47da58848da7eb5d09b0b4c52a421fdba67e02e5615f52ad0982e172953a7a98075fd8ce49b6fa14fd09f91e63248c729c08931d9ba28
SHA256: 3a1c6928406f758ae01ae434f9c1993eb05c7457a2efcab58cc1f8bdf732804e
SHA1: 571723c4e170bd8b2a346fab710be9ad25214be1
MD5sum: fa669f652e0b9200b8f6c3521d13632c
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.