Ubuntu
pgsql-ogr-fdw package

pgsql-ogr-fdw 1.0.4-1 source package in Ubuntu

Changelog

pgsql-ogr-fdw (1.0.4-1) unstable; urgency=low

  * New upstream release.
  * Drop gdal-2.2 patch, included by upstream.
  * Replace Priority extra with optional as required by policy 4.0.1.

 -- Michael Fladischer <email address hidden>  Tue, 17 Oct 2017 18:19:28 +0200

Upload details

Uploaded by:
Debian GIS Project
Uploaded to:
Sid
Original maintainer:
Debian GIS Project
Architectures:
any
Section:
misc
Urgency:
Low Urgency

See full publishing history Publishing

Series Pocket Published Component Section

Downloads

File Size SHA-256 Checksum
pgsql-ogr-fdw_1.0.4-1.dsc 1.7 KiB cb29210b8c22f63c67b20ece30cb2cbc9180e293aab9bff0579595b0d1eec575
pgsql-ogr-fdw_1.0.4.orig.tar.gz 237.8 KiB 16b0d18e1a9c969cdbde351d9cf69195e090b8fe4ad025747dc64f300260f40b
pgsql-ogr-fdw_1.0.4-1.debian.tar.xz 3.8 KiB 6f0d3f93fe86db5f118e7115e292b251381e43f313f030c92db5fa0233ccf59c

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