Result for C9027D9A7F10489EC9462A91A5A74D7E6454516B

Query result

Key Value
FileName./usr/lib/postgresql/14/lib/bitcode/ogr_fdw/ogr_fdw.bc
FileSize65268
MD54EA7432BE910C3F38205F55B40F23DD7
SHA-1C9027D9A7F10489EC9462A91A5A74D7E6454516B
SHA-256CFA93477A2298FEF912FF3BB6ED25FF560520F1E99D88D1F435C75E8BB42BF07
SSDEEP1536:GHfuKoPdQBWFTTB6oetARsjGrx0QF8l1L:GHf8PdQ8TpetAR7rhef
TLSHT120538D2976A1C791D49D133F8CBF02CD06B9A604AF62A55333946B1C2DB134CE972AFD
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
FileSize99124
MD59021F72D4E041C8E5A4BD9C42D26D733
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.
PackageMaintainerDebian GIS Project <pkg-grass-devel@lists.alioth.debian.org>
PackageNamepostgresql-14-ogr-fdw
PackageSectiondatabase
PackageVersion1.1.1-2
SHA-1A610C0F9B5CC8B4F14A1C64F7149C17A67174787
SHA-256E58BA902C1D0EF3614EA862AD03540A4248DC3B10909391145557334A40864EB