From: Regina Obe Date: Thu, 21 Feb 2013 13:29:35 +0000 (+0000) Subject: document issue in ticket #2209 in FAQ. Probably only affects me, but who knows. X-Git-Tag: 2.1.0beta2~200 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=df45d10a49910aac679fee1761c6c77f618ff25a;p=postgis document issue in ticket #2209 in FAQ. Probably only affects me, but who knows. git-svn-id: http://svn.osgeo.org/postgis/trunk@11105 b70326c6-7e19-0410-871a-916f4a2858ee --- diff --git a/doc/faq_raster.xml b/doc/faq_raster.xml index f1d200b70..48391a4d5 100644 --- a/doc/faq_raster.xml +++ b/doc/faq_raster.xml @@ -247,8 +247,6 @@ END - - How is PostGIS Raster different from Oracle GeoRaster (SDO_GEORASTER) and SDO_RASTER types? @@ -270,4 +268,23 @@ END + + + + raster2pgsql load of large file fails with String of 388800145 bytes is too long for encoding conversion? + + + + raster2pgsql doesn't make any connections to your database when generating the file to load. If your database has set an explicit client encoding different + from your database encoding, then when loading large raster files (above 30 MB in size), you may run into a bytes is too long for encoding conversion. + This generally happens if for example you have your database in UTF8, but to support windows apps, you have the client encoding set to WIN1252. + To work around this make sure the client encoding is the same as your database encoding during load. You can do this by explicitly setting the encoding in your load script. Example, if you are on windows: + set PGCLIENTENCODING=UTF8 + If you are on Unix/Linux + export PGCLIENTENCODING=UTF8 + Gory details of this issue are detailed in http://trac.osgeo.org/postgis/ticket/2209 + + + +