Result for 81E3516DD27B2D8B74A8872160191DC735935C0B

Query result

Key Value
FileName./usr/lib/postgresql/12/lib/ogr_fdw.so
FileSize63824
MD5FC7BA298EF9E3079B5A933B28A5D20F9
SHA-181E3516DD27B2D8B74A8872160191DC735935C0B
SHA-2562BBFDDC1835195B22693F11F468489A4432AF937D2F246E86140A70B67496081
SSDEEP1536:j3qoGdqu/npyHTD3HNzjep9CGKzPbI3d4:zqjdqufon3Vap9JpG
TLSHT10D53B52FF260697CC0C5E0308EDF81720A20F879B531156F2F85B77B3D6A96951B9E26
hashlookup:parent-total1
hashlookup:trust55

Network graph view

Parents (Total: 1)

The searched file hash is included in 1 parent files which include package known and seen by metalookup. A sample is included below:

Key Value
FileSize90596
MD57B9B61CAC4A23CB2917C86651528038C
PackageDescriptionPostgreSQL 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.
PackageMaintainerUbuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com>
PackageNamepostgresql-12-ogr-fdw
PackageSectiondatabase
PackageVersion1.0.9-1build2
SHA-1F75AAE8780FC1A07DA5A0475DF45E034D6F7A8E7
SHA-256937533C576F18F0374C13FB6BA203F57D45CBD7F92A3EDAFA5A57F5F9579961A