From b83f502d11a2448f4fa23ccf999da51185f833a7 Mon Sep 17 00:00:00 2001 From: Regina Obe Date: Thu, 21 Feb 2013 14:09:21 +0000 Subject: [PATCH] missing para tag git-svn-id: http://svn.osgeo.org/postgis/trunk@11107 b70326c6-7e19-0410-871a-916f4a2858ee --- doc/faq_raster.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/faq_raster.xml b/doc/faq_raster.xml index 7c951fe0b..5fd496999 100644 --- a/doc/faq_raster.xml +++ b/doc/faq_raster.xml @@ -276,7 +276,7 @@ END 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. + 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 -- 2.40.0