yes; I tend not to pollute system dirs with user data, so I usually put
(or link) everything pg-related in a dedicated dir accessible by
postgres. I just forgot to do it in this new machine.
Thanks.
Il 06/11/19 10:32, Jorge Gustavo Rocha ha scritto:
> Hi Paolo,
>
> Nice to know you found out the
Hi Paolo,
Nice to know you found out the problem. The easiest option to store
out-of-db rasters can be under Postgresql's data_directory. All users
should be able to read files from there.
# show data_directory;
data_directory
-
/var/lib/postgresql/11/main
Reg
/me stupid: postgresql did not have read access to the file.
sorry for the noise
Il 06/11/19 08:18, Paolo Cavallini ha scritto:
> Hi Jorge,
>
> Il 05/11/19 21:34, Jorge Gustavo Rocha ha scritto:
>
>> If you have GDAL >= 2.4, it should work. Can you check your GDAL version?
>
> 2.4.2+dfsg-2
>
>
Hi Jorge,
Il 05/11/19 21:34, Jorge Gustavo Rocha ha scritto:
> If you have GDAL >= 2.4, it should work. Can you check your GDAL version?
2.4.2+dfsg-2
> Do you also have overviews/pyramids? The overviews should work, because
> they are in db. Only the original raster is out-of-db.
sure, all "no
Hi Paolo,
If you have GDAL >= 2.4, it should work. Can you check your GDAL version?
Do you also have overviews/pyramids? The overviews should work, because
they are in db. Only the original raster is out-of-db.
Regards,
Jorge
Às 20:24 de 05/11/19, Paolo Cavallini escreveu:
> Hi all,
> loading
Hi all,
loading PostGIS rasters from the browser works very well, thanks Ale!
However, those loaded with the -R option (out of db rasters) throw an error:
Warning: Logged warning: RasterIO error:
PostGISRasterRasterBand::IRasterIO(): ERROR: rt_band_load_offline_data:
Cannot open offline raster:
/
