pgsql-ogr-fdw 1.0.9-1build2 source package in Ubuntu

Changelog

pgsql-ogr-fdw (1.0.9-1build2) focal; urgency=medium

  * No-change rebuild with fixed binutils on arm64.

 -- Matthias Klose <email address hidden>  Mon, 10 Feb 2020 08:15:29 +0100

Upload details

Uploaded by:
Matthias Klose on 2020-02-10
Uploaded to:
Focal
Original maintainer:
Debian GIS Project
Architectures:
any
Section:
misc
Urgency:
Medium Urgency

See full publishing history Publishing

Series Pocket Published Component Section
Focal release on 2020-02-13 universe misc

Downloads

File Size SHA-256 Checksum
pgsql-ogr-fdw_1.0.9.orig.tar.gz 240.6 KiB a0eb072b08fe63fe065983cc67fa2f36af9010455932a78307cdf919d970be95
pgsql-ogr-fdw_1.0.9-1build2.debian.tar.xz 4.9 KiB 495875e4d44a756a9e3e1c9b8cceb4ad67986a442968eebd95a7661d9b0d2aaf
pgsql-ogr-fdw_1.0.9-1build2.dsc 2.1 KiB 0fb4417dfc42f5e2fcee936e01c6d68b270f156f393eb468589b60cab1a58c94

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