Result for 8445BFE2DE1D8BC3B22B614F9CDF14AD03F5DB78

Query result

Key Value
FileName./usr/lib/postgresql/13/lib/bitcode/ogr_fdw/ogr_fdw_deparse.bc
FileSize23856
MD59984D4A4478DF31F2C0144C8E2A1EBED
SHA-18445BFE2DE1D8BC3B22B614F9CDF14AD03F5DB78
SHA-256F1222DC810F74F6A772C0DCACE54468231B00FC0DB60E9ED3BA36E7302A30224
SSDEEP384:kgO7qsQFgoUD307WuwXshEWEAgVmf9CwAsGdB5Qo1N:tq5tDk7jw8uWEArFAsoBGo1N
TLSHT18FB28D29F6F58652C908163E4D7F41DB185AFE88EF208287A29A373C7D732489F715B1
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
FileSize98328
MD5A90CCE833FFCD629416072C3E7595C29
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-17EA03B090F2F91F8F1D5CFB581DAA21379CD34F2
SHA-256BD6D8B21E4B0BB6EE9A58D2750547274BAD23BA75C296018C19AFDDF90CA09B7