How to Install and Uninstall postgresql-13-ogr-fdw Package on Ubuntu 21.10 (Impish Indri)
Last updated: November 13,2024
1. Install "postgresql-13-ogr-fdw" package
This tutorial shows how to install postgresql-13-ogr-fdw on Ubuntu 21.10 (Impish Indri)
$
sudo apt update
Copied
$
sudo apt install
postgresql-13-ogr-fdw
Copied
2. Uninstall "postgresql-13-ogr-fdw" package
Here is a brief guide to show you how to uninstall postgresql-13-ogr-fdw on Ubuntu 21.10 (Impish Indri):
$
sudo apt remove
postgresql-13-ogr-fdw
Copied
$
sudo apt autoclean && sudo apt autoremove
Copied
3. Information about the postgresql-13-ogr-fdw package on Ubuntu 21.10 (Impish Indri)
Package: postgresql-13-ogr-fdw
Architecture: amd64
Version: 1.1.0-1
Priority: optional
Section: universe/database
Source: pgsql-ogr-fdw
Origin: Ubuntu
Maintainer: Ubuntu Developers
Original-Maintainer: Debian GIS Project
Bugs: https://bugs.launchpad.net/ubuntu/+filebug
Installed-Size: 260
Provides: postgresql-ogr-fdw
Depends: postgresql-13, libc6 (>= 2.14), libgdal28 (>= 2.2.0)
Filename: pool/universe/p/pgsql-ogr-fdw/postgresql-13-ogr-fdw_1.1.0-1_amd64.deb
Size: 100788
MD5sum: 30b2703f5a955242f9e81a344a41fd97
SHA1: 2f66d1f467870c293d1c19a8b08b8bac61cb5ab3
SHA256: 91711f299ba6d110ba9b00cf1e2750df771b0cfa427f86934053ea2768aba3ea
SHA512: 52ac029d9a8e4c33e288ad33f9a5ad373834dc5b79d3e266b1e92c545ec9b8c5a1601aae4322c29479abb341c74209556e279dd97dccf288f201c8fe8008cd97
Homepage: https://github.com/pramsey/pgsql-ogr-fdw
Description-en: 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.
Description-md5: 5f6108f90edfb86f7c870551bc52f9e2
Architecture: amd64
Version: 1.1.0-1
Priority: optional
Section: universe/database
Source: pgsql-ogr-fdw
Origin: Ubuntu
Maintainer: Ubuntu Developers
Original-Maintainer: Debian GIS Project
Bugs: https://bugs.launchpad.net/ubuntu/+filebug
Installed-Size: 260
Provides: postgresql-ogr-fdw
Depends: postgresql-13, libc6 (>= 2.14), libgdal28 (>= 2.2.0)
Filename: pool/universe/p/pgsql-ogr-fdw/postgresql-13-ogr-fdw_1.1.0-1_amd64.deb
Size: 100788
MD5sum: 30b2703f5a955242f9e81a344a41fd97
SHA1: 2f66d1f467870c293d1c19a8b08b8bac61cb5ab3
SHA256: 91711f299ba6d110ba9b00cf1e2750df771b0cfa427f86934053ea2768aba3ea
SHA512: 52ac029d9a8e4c33e288ad33f9a5ad373834dc5b79d3e266b1e92c545ec9b8c5a1601aae4322c29479abb341c74209556e279dd97dccf288f201c8fe8008cd97
Homepage: https://github.com/pramsey/pgsql-ogr-fdw
Description-en: 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.
Description-md5: 5f6108f90edfb86f7c870551bc52f9e2