Hi We have been looking into this problem some more. So it seems we can reproduce this by using postgis raster tiles of 100 x 100. raster2pgsql cmd was: raster2pgsql bigtiff.tif -C -r -s 27700 -t 100x100 -P -I -M -Y <schema.tablename> | psql <connection details>
The effect seems more pronounced using GDAL 2.2 (trunk) vs GDAL 2.1 With a tilesize of 256*256 it is fine. This is a very large tif btw; ~150000 x 200000 pixels -- View this message in context: http://osgeo-org.1560.x6.nabble.com/Memory-increase-in-postgis-raster-driver-tp5277284p5280563.html Sent from the GDAL - Dev mailing list archive at Nabble.com. _______________________________________________ gdal-dev mailing list gdal-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/gdal-dev
