Result for 0C653CBB1E618487B1433278B8D23FA0AD920709

Query result

Key Value
FileName./usr/lib/postgresql/13/lib/bitcode/ogr_fdw/ogr_fdw_func.bc
FileSize5860
MD5E03D6DA4ECB8CDF3412E7656FD458D58
SHA-10C653CBB1E618487B1433278B8D23FA0AD920709
SHA-25660A1809B0762567BEFD771CFE581AE6D4DECA3AD1A14B14F5B7CC93A1E81E9E0
SSDEEP96:kM59cXSFkq6JVRWE8SEh7q/mHTn3ZHGmQ6YKtZDy+KacJ1ouoYqXWf7oYmwgbB/:kMrcq6nmh7q/0r3gkYKtT+hgV
TLSHT15DC12B2933641A91C05E073DEDAF42C75739EA089FC6B7577785B72CB9F021E69108B2
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
FileSize99488
MD55042B2C86342CBE7EB329B4E6F837A6C
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.1-1+b1
SHA-121F94D177270A370A9D33982AD0870309E2BA1D2
SHA-25641A8CE6B890A31004E52D11D3B1C4ADD43B0E7A9F1ACC201FC756BB4A3C2EF4E