Result for E463435831BC6038E6639F70E2B3F4E203CEADB4

Query result

Key Value
FileName./usr/lib/postgresql/13/lib/ogr_fdw.so
FileSize50644
MD5FFDF886BBCB55D9A1E819FC0F309CFA8
SHA-1E463435831BC6038E6639F70E2B3F4E203CEADB4
SHA-256FD0E666F89B5C1243447DC7CD34CB0373E46C70F18B37D3E21EBBAD3A1E9BE38
SSDEEP768:4L6U8pDSrp9D16H6I8IfVXaHg5NxvnVLjTtjCi59Jf4bR49Hpcr553D3yQkZBQzY:+YDUH6Hr3qsnDCi5SRoGfeRQzBIoK
TLSHT11933F895B8818E57C5C4127577AA8E68B33303B8D2DE3BA6CC1883652EA710FCD77E51
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
FileSize97328
MD572AAF45312DB05173F5F6DC856F8842D
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-13-ogr-fdw
PackageSectiondatabase
PackageVersion1.1.0-1
SHA-1825CA71D3EA0229BB545E10DFED7115CEA683183
SHA-256CBBD366C47498D0B446823DE0EA1CE3C5E38B6A157CB2CA12DC7D22339824328