Result for 9D01C47868DF9E536A585A68747A47C19F9EBF92

Query result

Key Value
FileName./usr/share/doc/postgresql-10-ogr-fdw/copyright
FileSize1531
MD5B9EAE8DE6CED8D999B806061D4314D1E
SHA-19D01C47868DF9E536A585A68747A47C19F9EBF92
SHA-2562E5E3CAD45B5E494310B1E4955421DF5BAFA23CD13709181487903D526248694
SSDEEP24:gttzRRSoRhKKGUxrwNJHZH0yf3gtk1Hc1hMK9QH0sUv4kOk4/+/U3oq4sFig:s3FxyJxl/El5QH0s5ANU3oWFig
TLSHT18B31B74FF68403632DD223E29555B8E9A7337189B4AB16C4E45EF3086B290ADD1FA464
hashlookup:parent-total2
hashlookup:trust60

Network graph view

Parents (Total: 2)

The searched file hash is included in 2 parent files which include package known and seen by metalookup. A sample is included below:

Key Value
FileSize29392
MD5EFB208D5290427817C1194A222966713
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-10-ogr-fdw
PackageSectiondatabase
PackageVersion1.0.5-2
SHA-1439081135AAFA8B2073A6C92C42449F92AA153CD
SHA-25642631D380EB4FF25B2ED703784B35B274B4A5860AFAD74B34E6AEEF34A3DD53D
Key Value
FileSize27300
MD584DCBEDCDE509DF087709A1A19BA0609
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-10-ogr-fdw
PackageSectiondatabase
PackageVersion1.0.5-2
SHA-1C32237FB12A5074A1E9FEDE740A409DE83AA81E7
SHA-25671F1E4EDCE2A8B976D5EEC637198BDF7A4D225B543755998410849EE8E294872