Result for F50913C65B19F6F5CD739998272F0ADD4B0A7034

Query result

Key Value
FileName./usr/lib/postgresql/14/lib/bitcode/ogr_fdw/stringbuffer_pg.bc
FileSize10616
MD55059C541E029247AB4FF909F62CD2D65
SHA-1F50913C65B19F6F5CD739998272F0ADD4B0A7034
SHA-256FE766027FF4AF3687679ABA2E970547B1DDE2098F138646B02331177A110AC4F
SSDEEP192:kROvh7yKcWYb7rTd+KtTduCnyzxUkkKNxTWPJML:kReU3XrTd5nkYKNlW
TLSHT1F3223A1FB3AC8A41D1491F3D8CE7419DC2AAB4848F30E7A777A61B3CAEF102E58D1156
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
FileSize96856
MD51275E390BEC0B0F83C2C33BCFBE82912
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-1AFD2D9502867354D3A87911AB1F134F2574C7333
SHA-256A7FF6FD143AC30BCFBB798803DFDE74BEC42F29E72A0D28BBEBF2529CF3810D3