Maybe you can try to separate raster2pgsql and psql . First use raster2pgsqland output it to a file on you filesystem. Then use psql to execute this file.
You could see how much time each step takes, and how much space the sql temp file is. Maybe you could use the "-Y" flag to make it faster? Cheers, Rémi-C 2014-02-27 11:03 GMT+01:00 Eloi <[email protected]>: > Hi all, > > My SELECT PostGIS_Full_Version() is: "POSTGIS="2.0.3 r11128" > GEOS="3.3.8-CAPI-1.7.8" PROJ="Rel. 4.8.0, 6 March 2012" GDAL="GDAL 1.10.0, > released 2013/04/24" LIBXML="2.9.0" LIBJSON="UNKNOWN" RASTER" > > I am importing a GeoTIFF (1 band, Type = Byte, Not Compressed file size = > 933.5 MB, columns/rows 43200, 21600, Pixel Size = > 0.008333333333333,-0.008333333333333) > into PostGIS and is taking more than one hour by now. Is that normal? > > This is the command I have used: > raster2pgsql -s 4326 -d -I -C -M -t 5x5 /path/file_name.tif > schema_name.table_name|psql -d db_name > > Yes, very small tiles. The goal is to intersect this raster with point > features. But the issue right now is the import it self that is taking to > much time. > I can see now that the first 1:30 were for inserts and now is starting > with the constraints. Is this the normal speed or am I missing something? > > Thanks. Cheers, > > Eloi > _______________________________________________ > postgis-users mailing list > [email protected] > http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-users >
_______________________________________________ postgis-users mailing list [email protected] http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-users
