[postgis-users] more memory issues with raster2pgsql

[Bborie Park]

How big is the original? Numbers of pixels width and height? Number of
bands? Pixel types of the bands? I just want to know so that I can tell you
if its even possible to store that raster as one database value.

Utf-8 shouldn't be an issue as the raster data itself isn't in any
character set encoding. They're almost always numerical values.

All my production and dev postgresql clusters are in utf8 and I've never
seen a raster encoding issue.

-bborie
On Mar 28, 2014 6:36 PM, "georgew" <gws293 at hotmail.com> wrote:

> Thanks bborie, however from the error message I received the problem seems
> due to the need to convert the original raster to utf-8. But the original
> raster is in utf-8 already.
> If I follow your suggestion (and after this mystery conversion is done)
> will
> I be able to recombine the tiles to create a single raster, to be just like
> the original?
>
>
>
>
> --
> View this message in context:
> http://postgis.17.x6.nabble.com/more-memory-issues-with-raster2pgsql-tp5006000p5006002.html
> Sent from the PostGIS - User mailing list archive at Nabble.com.
> _______________________________________________
> postgis-users mailing list
> postgis-users at lists.osgeo.org
> http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-users/attachments/20140328/3b1fdcff/attachment.html>