Bug report #8765
Postgis raster shows random data with out-db image data
|Affected QGIS version:||2.0.1||Regression?:||No|
|Operating System:||Easy fix?:||No|
|Pull Request or Patch supplied:||No||Resolution:||duplicate|
|Crashes QGIS or corrupts data:||Yes||Copied to github as #:||17471|
Out-db rasters from postgis database are shown as random data and sometimes crashes QGIS.
The problem might come from the way the database is queried.
Query made by QGIS taken from the server:
SELECT st_band(rast, 3), st_width(rast), st_height(rast), ....
As far as I have tested "st_band" in queries return data as out-db referenced rasters and contain no pixel data.
If there are no modification to the data like st_union or something like that, rasters stays as file references, which obviously cannot be used by the client over the network.
#1 Updated by asdf asdf over 9 years ago
Forgot to add details of the used version.
QGIS version 2.0.1-Dufour
QGIS code revision d94c044
Compiled against Qt 4.8.5
Running against Qt 4.8.5
Compiled against GDAL/OGR 1.10.0
Running against GDAL/OGR 1.10.1
Compiled against GEOS 3.4.2-CAPI-1.8.2
Running against GEOS 3.4.2-CAPI-1.8.2 r3921
PostgreSQL Client Version 9.2.4
SpatiaLite Version 4.1.1
QWT Version 5.2.3
PROJ.4 Version 480
QScintilla2 Version 2.7.2
#5 Updated by asdf asdf almost 9 years ago
I'm not sure if this is duplicate of the #8628, this might actually be a just problem created by me by creating overviews manually as I have overviews for other use and didn't want to duplicate static raster data indb.
As a consequence of this self made overviews rasters are not indb and the overview query will fail as it relies that the data is always indb.
Anyways the question is should the overview query always expect indb data or not.