<h2>Raw Package Information</h2>
<pre class="literal-block">
Package: postgresql-10-ogr-fdw
Source: pgsql-ogr-fdw
Version: 1.1.3-1.pgdg22.04+1
Architecture: amd64
Maintainer: Debian GIS Project &lt;pkg-grass-devel@lists.alioth.debian.org&gt;
Installed-Size: 123
Depends: postgresql-10, libc6 (&gt;= 2.34), libgdal30 (&gt;= 2.2.0)
Provides: postgresql-ogr-fdw
Homepage: https://github.com/pramsey/pgsql-ogr-fdw
Priority: optional
Section: database
Filename: pool/main/p/pgsql-ogr-fdw/postgresql-10-ogr-fdw_1.1.3-1.pgdg22.04+1_amd64.deb
Size: 34124
SHA256: dcadda60eddfa5765fbe33f6fdac46ca103f1ac78c8d472ccb3c8d3d601dd10d
SHA1: c99c5aac7da39fc2891fec8370b4d20e35d461f0
MD5sum: 624984bb34cf3689b5fca9f2f96a0683
Description: 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 (&gt;, &lt;, &lt;=, &gt;=, =) 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&#39;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.


</pre>