[postgis-tickets] [PostGIS] #2209: [raster]: String of 388800145 bytes is too long for encoding conversion

[PostGIS]

#2209: [raster]:  String of 388800145 bytes is too long for encoding conversion
--------------------+-------------------------------------------------------
 Reporter:  robe    |       Owner:  dustymugs    
     Type:  defect  |      Status:  new          
 Priority:  medium  |   Milestone:  PostGIS 2.1.0
Component:  raster  |     Version:  trunk        
 Keywords:          |  
--------------------+-------------------------------------------------------

Comment(by dustymugs):

 For a split second I thought this was a memory issue but after seeing the
 word "encoding" and the size of the raster file, it definitely has
 something to do with PostgreSQL.  raster2pgsql doesn't know anything about
 the database's settings for client encoding as it never (ever!) touches a
 database.

 I found the place in PostgreSQL's source that emits that error message and
 the max size permitted for an encoding conversion is ~250 MB.

 http://doxygen.postgresql.org/memutils_8h_source.html

 Having the client encoding be the same as the server encoding eliminates
 the conversion process.

 I don't know what we can do about this though beyond leaving a note in the
 docs...

-- 
Ticket URL: <http://trac.osgeo.org/postgis/ticket/2209#comment:2>
PostGIS <http://trac.osgeo.org/postgis/>
The PostGIS Trac is used for bug, enhancement & task tracking, a user and developer wiki, and a view into the subversion code repository of PostGIS project.