pgsql-ogr-fdw 1.0.7-2 source package in Ubuntu


pgsql-ogr-fdw (1.0.7-2) unstable; urgency=medium

  * Team upload.
  * Move from experimental to unstable.

 -- Bas Couwenberg <email address hidden>  Sat, 13 Oct 2018 08:33:53 +0200

Upload details

Uploaded by:
Debian GIS Project on 2018-10-13
Uploaded to:
Original maintainer:
Debian GIS Project
Medium Urgency

See full publishing history Publishing

Series Pocket Published Component Section
Eoan release on 2019-04-18 universe misc
Disco release on 2018-11-23 universe misc


File Size SHA-256 Checksum
pgsql-ogr-fdw_1.0.7-2.dsc 2.1 KiB ae80cb23b8603901536a73b465b86b3f7a6bb0cf38f54eae0f7959cc7b927b77
pgsql-ogr-fdw_1.0.7.orig.tar.gz 238.4 KiB c776d9ad108818bae33336ca8d2219837e04d2c25c9086928e4bb6e06947b6e9
pgsql-ogr-fdw_1.0.7-2.debian.tar.xz 4.4 KiB 7038b0f261000ebb085b52da75f2c662eba2ea27096d822636db25172f51b484

Available diffs

No changes file available.

Binary packages built by this source

postgresql-11-ogr-fdw: 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.

postgresql-11-ogr-fdw-dbgsym: debug symbols for postgresql-11-ogr-fdw