Ubuntu
pgsql-ogr-fdw package

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

Changelog

pgsql-ogr-fdw (1.1.5-1) unstable; urgency=medium

  * Team upload.
  * New upstream release.
  * Add ${postgresql:Depends} to Depends.
  * Refresh patches.

 -- Bas Couwenberg <email address hidden>  Fri, 28 Jun 2024 06:13:51 +0200

Upload details

Uploaded by:
Debian GIS Project
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
Oracular release universe misc

Downloads

File Size SHA-256 Checksum
pgsql-ogr-fdw_1.1.5-1.dsc 2.1 KiB 4cc2151010ce6e8cf53005cab26720bac585c52385de8770fe6b91443e3482b9
pgsql-ogr-fdw_1.1.5.orig.tar.gz 249.5 KiB 820842a4bd3889d82e767f4eea49954daa894f315e24614650022154446a55d0
pgsql-ogr-fdw_1.1.5-1.debian.tar.xz 5.5 KiB f355a0604a5e8b71b56f2175bd19d7c6b7fb065088ba78ce6c500aa2b89d42a5

No changes file available.

Binary packages built by this source

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