pgsql-ogr-fdw 1.0.12-1build1 source package in Ubuntu

Changelog

pgsql-ogr-fdw (1.0.12-1build1) groovy; urgency=medium

  * No-change rebuild against libgdal27

 -- Graham Inggs <email address hidden>  Sun, 21 Jun 2020 23:16:29 +0000

Upload details

Uploaded by:
Graham Inggs on 2020-06-21
Uploaded to:
Groovy
Original maintainer:
Debian GIS Project
Architectures:
any
Section:
misc
Urgency:
Medium Urgency

See full publishing history Publishing

Series Pocket Published Component Section
Groovy release on 2020-06-26 universe misc

Downloads

File Size SHA-256 Checksum
pgsql-ogr-fdw_1.0.12.orig.tar.gz 243.8 KiB 30990dae79347084d90d8e15a07d5cbc5fedd43b3175d87875a5606a8ba3a664
pgsql-ogr-fdw_1.0.12-1build1.debian.tar.xz 4.9 KiB 9708e0a4a430e45449ab54a789e1f0e91677e2164ac80a670132d5ab592435bf
pgsql-ogr-fdw_1.0.12-1build1.dsc 2.1 KiB c3ee2add51d2cb1ec283e938a69c97d7859cb0cda3fc6d4a3babadc303d73715

View changes file

Binary packages built by this source

postgresql-12-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-12-ogr-fdw-dbgsym: debug symbols for postgresql-12-ogr-fdw