<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link="#0563C1" vlink="#954F72"><div class=WordSection1><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>No it is not possible. Performance wise it would suck too to store large rasters per row because of the mem copy stuff involved for some operations.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><a href="https://gis.stackexchange.com/questions/31871/are-there-limitations-using-a-postgis-out-db-raster">https://gis.stackexchange.com/questions/31871/are-there-limitations-using-a-postgis-out-db-raster</a><o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Sadly this limitation has existed for some time, and mostly a limitation of the underlying PostgreSQL.<span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>With changes in PostgreSQL 12 allowing pluggable storage, we could revisit this topic perhaps for PostGIS 3.1. I think it's too late to consider for upcoming PostGIS 3.0<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>Thanks,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>Regina<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'><o:p> </o:p></span></p><div style='border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt'><div><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'>From:</span></b><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'> postgis-devel [mailto:postgis-devel-bounces@lists.osgeo.org] <b>On Behalf Of </b>Pradeep kumar<br><b>Sent:</b> Tuesday, May 14, 2019 3:54 AM<br><b>To:</b> postgis-devel@lists.osgeo.org<br><b>Subject:</b> [postgis-devel] raster2pgsql failed to insert out-db raster(x, y : 16242, 66479)<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><div><div><p class=MsoNormal style='margin-bottom:12.0pt'>Dear All,<br> <br> I am trying to insert a raster (X,Y: 16242, 66479, size on<br>disk:825.3 MB, not compressed) using raster2pgsql tool with "-R" option.<br> <br>command: raster2pgsql -R test_image.tif test_image | psql -U user -d<br>database<br> <br>Error: rt_raster_new: Dimensions requested exceed the maximum (65535 x<br>65535) permitted for a raster<br> <br>This works if I use the tile option "-t heightxwidth". But then multiple<br>rows for a single raster in the database table are created, which is not a<br>desirable result for me.<br> <br>So, I would like to store a raster with height or width more than 65535 in<br>the PostGIS database table as a single row. Is this possible? If so, can<br>you please provide me how?<br> <br>My Environment:<br>Postgres Version: PostgreSQL 10.4 on x86_64-pc-linux-gnu, compiled by gcc<br>(Alpine 6.4.0) 6.4.0, 64-bit<o:p></o:p></p></div><div><p class=MsoNormal>Postgis version: POSTGIS="2.5.0" [EXTENSION] PGSQL="100"<br>GEOS="3.7.0-CAPI-1.11.0 673b9939" PROJ="Rel. 5.0.1, April 1st, 2018"<br>GDAL="GDAL 2.3.2, released 2018/09/21" LIBXML="2.9.8" LIBJSON="0.13.1"<br>RASTER<br> <br>I am looking forward for your reply.<br> <br>Best Regards,<br>Pradeep Gulla <o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div></div></div></div></body></html>