Package: postgresql-16-ogr-fdw
Source: pgsql-ogr-fdw
Version: 1.1.9-1.pgdg22.04+1
Architecture: amd64
Maintainer: Debian GIS Project <pkg-grass-devel@lists.alioth.debian.org>
Installed-Size: 268
Depends: postgresql-16, 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-16-ogr-fdw_1.1.9-1.pgdg22.04+1_amd64.deb
Size: 108716
SHA512: 7f1cb3bebd1e10e250c2ce78a296eac13fa397fa040a1a44b3380137967b9e6c791124ab9edc8362e5b97f2a49043d615ee2537d09f6bea833bbb0034224c417
SHA256: e696cd8e918f84097faa4d9becf09c464ae726c9f7a48d9107e80f278e63666b
SHA1: ef27e7dbc22d44481d0dc9a3e89eaca4397d3ced
MD5sum: 8c826237b0699252b4061bf63bb1265d
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.