How to Install and Uninstall postgresql-16-ogr-fdw Package on Kali Linux
Last updated: November 07,2024
1. Install "postgresql-16-ogr-fdw" package
Please follow the instructions below to install postgresql-16-ogr-fdw on Kali Linux
$
sudo apt update
Copied
$
sudo apt install
postgresql-16-ogr-fdw
Copied
2. Uninstall "postgresql-16-ogr-fdw" package
Please follow the steps below to uninstall postgresql-16-ogr-fdw on Kali Linux:
$
sudo apt remove
postgresql-16-ogr-fdw
Copied
$
sudo apt autoclean && sudo apt autoremove
Copied
3. Information about the postgresql-16-ogr-fdw package on Kali Linux
Package: postgresql-16-ogr-fdw
Source: pgsql-ogr-fdw (1.1.4-3)
Version: 1.1.4-3+b1
Installed-Size: 251
Maintainer: Debian GIS Project
Architecture: amd64
Provides: postgresql-ogr-fdw
Depends: postgresql-16, libc6 (>= 2.34), libgdal34 (>= 2.2.0)
Size: 103072
SHA256: 36ab6c35746d894367c6a6f6333833752bf8f89ba6e83a1ba946d639b5ea164c
SHA1: ecc9b41db6dbbfeb0de49c46703acc04c25b5e22
MD5sum: 84b33284c13591d1cbee3c06fe008d9e
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 (>, <, <=, >=, =) 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:
Homepage: https://github.com/pramsey/pgsql-ogr-fdw
Section: database
Priority: optional
Filename: pool/main/p/pgsql-ogr-fdw/postgresql-16-ogr-fdw_1.1.4-3+b1_amd64.deb
Source: pgsql-ogr-fdw (1.1.4-3)
Version: 1.1.4-3+b1
Installed-Size: 251
Maintainer: Debian GIS Project
Architecture: amd64
Provides: postgresql-ogr-fdw
Depends: postgresql-16, libc6 (>= 2.34), libgdal34 (>= 2.2.0)
Size: 103072
SHA256: 36ab6c35746d894367c6a6f6333833752bf8f89ba6e83a1ba946d639b5ea164c
SHA1: ecc9b41db6dbbfeb0de49c46703acc04c25b5e22
MD5sum: 84b33284c13591d1cbee3c06fe008d9e
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 (>, <, <=, >=, =) 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:
Homepage: https://github.com/pramsey/pgsql-ogr-fdw
Section: database
Priority: optional
Filename: pool/main/p/pgsql-ogr-fdw/postgresql-16-ogr-fdw_1.1.4-3+b1_amd64.deb