[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:          |  
--------------------+-------------------------------------------------------
 This one is an odd one and may be an issue with PostgreSQL and not raster.
 Since I'm coming across it when loading raster I'll put it here.

 Okay I managed to load all the raster pictures I have in except for the
 biggest one and it gives this error.


 {{{
 NOTICE:  CREATE TABLE will create implicit sequence
 "armory3_local_rid_seq" for
 serial column "armory3_local.rid"
 NOTICE:  CREATE TABLE / PRIMARY KEY will create implicit index
 "armory3_local_pk
 ey" for table "armory3_local"
 CREATE TABLE
 ERROR:  out of memory
 DETAIL:  String of 388800145 bytes is too long for encoding conversion.
 CONTEXT:  COPY armory3_local, line 1
 CREATE INDEX
 ANALYZE
 }}}

 Now this may be a windows only issue.  You see I have this database set
 with UTF-8 encoding, but to deal with legacy apps, I have the client
 encoding set to :


 {{{
 ALTER DATABASE mydb
   SET client_encoding = 'WIN1252';
 }}}

 So i presume raster2pgsql is encoding as win1252, though for some reason I
 always thought bytea data would be untouched.

 The error only happens with the biggest image I have in this set which is
 ~29 MB.   I'll send you link to image separately.

-- 
Ticket URL: <http://trac.osgeo.org/postgis/ticket/2209>
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.