Package: postgresql-9.3-ogr-fdw
Source: pgsql-ogr-fdw
Version: 1.0.7-2.pgdg18.04+2
Architecture: i386
Maintainer: Debian GIS Project <pkg-grass-devel@lists.alioth.debian.org>
Installed-Size: 92
Depends: postgresql-9.3, libc6 (>= 2.4), libgdal20 (>= 2.2.0)
Homepage: https://github.com/pramsey/pgsql-ogr-fdw
Priority: optional
Section: database
Filename: pool/main/p/pgsql-ogr-fdw/postgresql-9.3-ogr-fdw_1.0.7-2.pgdg18.04+2_i386.deb
Size: 29180
SHA256: 4cb5354e09eaab635d338a774447f71332eaea7681dfe332984dcf5f4f3d4de6
SHA1: 690f5dfcb56416c7b224d9668cb0cedab7678dab
MD5sum: 46b39917d94e800dd3528eedaf4d012c
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.