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

Changelog

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

  * Add missing postgresql-server-dev-all test dependency.
  * Clean up better after testsuite.

 -- Christoph Berg <email address hidden>  Sun, 10 Dec 2017 08:43:26 +0100

Upload details

Uploaded by:
Debian GIS Project on 2017-12-10
Uploaded to:
Sid
Original maintainer:
Debian GIS Project
Architectures:
any
Section:
misc
Urgency:
Medium Urgency

See full publishing history Publishing

Series Pocket Published Component Section
Bionic release on 2017-12-10 universe misc

Downloads

File Size SHA-256 Checksum
pgsql-ogr-fdw_1.0.5-2.dsc 2.1 KiB 2f3dd7fb360b18907e3bc4ccdb358a16ad0fba2d80e7213d3a9878f1801c4d5c
pgsql-ogr-fdw_1.0.5.orig.tar.gz 238.1 KiB ae1fffa0917f07921d0738f9f3129da72a344d37cc810dd02b7c9b8db3d597f8
pgsql-ogr-fdw_1.0.5-2.debian.tar.xz 3.8 KiB 85892337bf08a8b5df5702e46acc5cec14652e28a7a9735dfb908ab096e8d94a

Available diffs

No changes file available.

Binary packages built by this source

postgresql-10-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
 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.

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