On 24 April 2014 21:19, Guillaume Drolet <droletguilla...@gmail.com> wrote: > I tried the same command as in my previous post on my PC at home. It's > Windows 7 64bit as well and the cluster has the same locale > ('French.Canadian.1252'.) and encoding (UTF8). > > The command was successful so my work colleague and I, who experiences > the same behaviour as the one described previously on this list, > suspect that it may be due to some problems or conflict between > PostGIS and the hardware (we have similar systems): is this a sensible > hypothesis?
I doubt it. I use raster2pgsql frequently on Windows, since PostGIS pre-2.0 and I have never experienced any such issues. raster2pgsql is a standalone command line utility that generates SQL commands and outputs them to stdout. raster2pgsql has no run-time dependency on PostgreSQL or PostGIS. First thing to check is: does raster2pgsql generate valid output, if redirected to file, does the SQL commands in output file look well-formed and complete? If not, which SQL lines are broken? Do the broken lines correspond to any character data in non-ASCII encodings? For example, check if you run raster2pgsql with -F switch to add column with the name of your raster file and the raster file name contains characters with French accents, etc. I'd suggest, don't use psql.exe or load any data to PostgreSQL until you confirm raster2pgsql generates text output with complete well-formed and valid SQL commands first. Best regards, -- Mateusz Łoskot, http://mateusz.loskot.net _______________________________________________ postgis-users mailing list postgis-users@lists.osgeo.org http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-users