Result for 8BBA7E2FE1F99B6B8B7D9F3DB5C9EBDD0468AE9E

Query result

Key Value
FileName./usr/lib/postgresql/13/lib/bitcode/ogr_fdw/ogr_fdw_func.bc
FileSize5996
MD5F23278340FAB952A6DC6D8B8FD9CAE3C
SHA-18BBA7E2FE1F99B6B8B7D9F3DB5C9EBDD0468AE9E
SHA-256AA5B1A54056D5C7B0AC51432352B0100A9A2BBA2C3F52FBE55B27F70073EC47E
SSDEEP96:k69cXSFkqvkHIk/EhkeweaUQBLOKtZDy+KPYXrBD1oHToYqXWdEWoYmwgbZ:k+cqvzhk7epKtTuYHgHg9
TLSHT1EBC14B1E33540A51C185073D9DBF01CAA7BAEA428F52E75726D6B62CBAB032E6C10A71
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
FileSize100788
MD530B2703F5A955242F9E81A344A41FD97
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-13-ogr-fdw
PackageSectiondatabase
PackageVersion1.1.0-1
SHA-12F66D1F467870C293D1C19A8B08B8BAC61CB5AB3
SHA-25691711F299BA6D110BA9B00CF1E2750DF771B0CFA427F86934053EA2768ABA3EA