Result for 52F1080E8C1FB3EFE205B5E71249BC866A35CE26

Query result

Key Value
FileName./usr/lib/postgresql/13/lib/bitcode/ogr_fdw/stringbuffer_pg.bc
FileSize10368
MD59BCC5F3DB8727C5193DD93FC1B3FDDA3
SHA-152F1080E8C1FB3EFE205B5E71249BC866A35CE26
SHA-2566B9AAD2C158E2745A4EEB9D40883E7BDA3F2E77FDDE5F09121A5378349D791F0
SSDEEP192:kZRhkoYGr3rxuvhkB0KtTu+AbR4F6mOC7hP6guvEx9TWugJMLn:kZRpr3gbNu6mOC7hiBvmpWC
TLSHT118225B0B77A95A94C1894B3D9CFA838E82BCE080CF64777367956D3C7DE1237A890072
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