<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:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";}
span.gmail-im
{mso-style-name:gmail-im;}
span.m4973381032542911461gmail-im
{mso-style-name:m_4973381032542911461gmail-im;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:"Courier New";}
span.go
{mso-style-name:go;}
span.highlighted
{mso-style-name:highlighted;}
.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=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>I thought I had mentioned running projsync, but maybe I sent before I added that note.<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'>Try running at the command line:<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><pre><span class=highlighted>projsync</span><span class=go> --all</span><o:p></o:p></pre><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Courier New"'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Courier New"'>As detailed in :<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Courier New"'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Courier New"'>https://proj.org/apps/projsync.html#index-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'><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-users [mailto:postgis-users-bounces@lists.osgeo.org] <b>On Behalf Of </b>pham lan<br><b>Sent:</b> Tuesday, March 28, 2023 2:34 PM<br><b>To:</b> PostGIS Users Discussion <postgis-users@lists.osgeo.org><br><b>Subject:</b> Re: [postgis-users] ERROR: transform: Point outside of projection domain (2050)<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><div><div><div><p class=MsoNormal style='margin-bottom:12.0pt'>Hi Regina,<o:p></o:p></p></div><p class=MsoNormal style='margin-bottom:12.0pt'>I did a pg_basebackup from Postgresql10(with postgis2.5) to postgresql10 (with postgis2.5) and the vacuum command went well.<br><i> /usr/pgsql-10/bin/vacuumdb -p 5433 --db geodm --analyze-in-stages --verbose</i><o:p></o:p></p></div><p class=MsoNormal>When I did upgrade postgis 2.5 to 3.0, the upgrade went ok but the vacuum analyze gave the same error. If it is the PROJ version different which causes this problem, what is the good way to deal with this<br><br><i>INFO: "geobordervtx": scanned 2665 of 2665 pages, containing 106839 live rows and 0 dead rows; 3000 rows in sample, 106839 estimated total rows<br>vacuumdb: vacuuming of database "geodm" failed: ERROR: transform: Point outside of projection domain (2050)</i><o:p></o:p></p><div><p class=MsoNormal><o:p> </o:p></p></div><div><div><p class=MsoNormal>#This is the output from the database before postgis upgrade<o:p></o:p></p></div><p class=MsoNormal><span class=gmail-im>geodm=# SELECT postgis_full_version();</span><br><br><span class=gmail-im> postgis_full_version</span><br><br><span class=gmail-im>--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------</span><br><span class=gmail-im>--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------</span><br><span class=gmail-im>---------------------------</span><br><span class=gmail-im> POSTGIS="2.5.5" [EXTENSION] PGSQL="100" GEOS="3.9.2-CAPI-1.14.3" SFCGAL="1.3.1" PROJ="Rel. 7.2.1, January 1st, 2021" GDAL="GDAL 3.2.3, released 2021/04/27" LIBXML="2.9.1" LIBJSON="0.11" LIBPROT</span><br><span class=gmail-im>OBUF="1.0.2" (core procs from "2.5.2 r17328" need upgrade) TOPOLOGY (topology procs from "2.5.2 r17328" need upgrade) RASTER (raster procs from "2.5.2 r17328" need upgrade) (sfcgal procs from "2</span><br><span class=gmail-im>.5.2 r17328" need upgrade) </span><o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal><span class=gmail-im>#This is the output from the database after postgis upgrade </span><o:p></o:p></p></div><p class=MsoNormal><i>geodm=# SELECT postgis_full_version();<br> postgis_full_version<br><br>--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------<br>----------------------------------------<br> POSTGIS="3.0.7 487b488" [EXTENSION] PGSQL="100" GEOS="3.9.2-CAPI-1.14.3" SFCGAL="1.4.1" PROJ="8.2.1" GDAL="GDAL 3.3.3, released 2021/10/25" LIBXML="2.9.7" LIBJSON="0.13.1" LIBPROTOBUF="1.3.0" W<br>AGYU="0.4.3 (Internal)" TOPOLOGY RASTER</i><o:p></o:p></p></div><p class=MsoNormal><o:p> </o:p></p><div><div><p class=MsoNormal>On Mon, Mar 27, 2023 at 11:53 PM Regina Obe <<a href="mailto:lr@pcorp.us">lr@pcorp.us</a>> wrote:<o:p></o:p></p></div><blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in'><div><div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>Did you run </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'> </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>SELECT postgis_extensions_upgrade();</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>SELECT postgis_extensions_upgrade();</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'> </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'> </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>Twice on your 3.0?</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'> </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>You should actually do the same on your 2.5 as well, as they are both at unstable states. The PostGIS 3.0 more so is unstable, cause it looks to have a mix of using the 2.5 and 3.0 libraries.</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'> </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>I don’t think the 2.5 even supported Proj 8.2 or at least not a combination we’ve tested.</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'> </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>Probably the issue is with difference in Proj 7.2 vs Proj 8.2.1</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'> </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>Do you have these running on the same server or different servers?</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'> </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>I think the proj.db files changed between 7.2 and 8.2 and so if the 8.2 is using a proj.db from 7.2 that could be a mess.</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'> </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'> </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'> </span><o:p></o:p></p><div style='border:none;border-left:solid windowtext 1.5pt;padding:0in 0in 0in 4.0pt;border-color:currentcolor currentcolor currentcolor blue'><div><div style='border:none;border-top:solid windowtext 1.0pt;padding:3.0pt 0in 0in 0in;border-color:currentcolor currentcolor'><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><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-users [mailto:<a href="mailto:postgis-users-bounces@lists.osgeo.org" target="_blank">postgis-users-bounces@lists.osgeo.org</a>] <b>On Behalf Of </b>pham lan<br><b>Sent:</b> Monday, March 27, 2023 4:59 PM<br><b>To:</b> PostGIS Users Discussion <<a href="mailto:postgis-users@lists.osgeo.org" target="_blank">postgis-users@lists.osgeo.org</a>><br><b>Subject:</b> Re: [postgis-users] ERROR: transform: Point outside of projection domain (2050)</span><o:p></o:p></p></div></div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p><div><div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Sorry, my bad. I just realized that the information about the postgis version I gave you was wrong. So the original one is 2.5 and the backup one is 3.0. Can it be that the st_transform function caused the problem in this case for different postgis functions?<o:p></o:p></p></div><p class=MsoNormal style='mso-margin-top-alt:auto;margin-bottom:12.0pt'>So the output of select postgis_full_version() are following:<o:p></o:p></p><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>#This is the output from the original database<o:p></o:p></p></div><p class=MsoNormal style='mso-margin-top-alt:auto;margin-bottom:12.0pt'><span class=m4973381032542911461gmail-im>geodm=# SELECT postgis_full_version();</span><br><br><span class=m4973381032542911461gmail-im> postgis_full_version</span><br><br><span class=m4973381032542911461gmail-im>--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------</span><br>--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------<br>---------------------------<br> POSTGIS="2.5.5" [EXTENSION] PGSQL="100" GEOS="3.9.2-CAPI-1.14.3" SFCGAL="1.3.1" PROJ="Rel. 7.2.1, January 1st, 2021" GDAL="GDAL 3.2.3, released 2021/04/27" LIBXML="2.9.1" LIBJSON="0.11" LIBPROT<br>OBUF="1.0.2" (core procs from "2.5.2 r17328" need upgrade) TOPOLOGY (topology procs from "2.5.2 r17328" need upgrade) RASTER (raster procs from "2.5.2 r17328" need upgrade) (sfcgal procs from "2<br>.5.2 r17328" need upgrade) <o:p></o:p></p></div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>#This is output of the target database:<br>geodm=# select postgis_full_version();<br><br> postgis_full_version<br><br>--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------<br>--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------<br>--------------------------------------------------------<br> POSTGIS="3.0.7 r487b488" [EXTENSION] PGSQL="100" GEOS="3.9.2-CAPI-1.14.3" SFCGAL="1.4.1" PROJ="8.2.1" GDAL="GDAL 3.2.3, released 2021/04/27" LIBXML="2.9.7" LIBJSON="0.13.1" LIBPROTOBUF="1.3.0"<br>(core procs from "2.5.2 r17328" need upgrade) TOPOLOGY (topology procs from "2.5.2 r17328" need upgrade) RASTER (raster lib from "2.5.5 r0" need upgrade) (raster procs from "2.5.2 r17328" need u<br>pgrade) (sfcgal procs from "2.5.2 r17328" need upgrade)<o:p></o:p></p><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p></div></div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p><div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>On Mon, Mar 27, 2023 at 10:41 PM pham lan <<a href="mailto:phamlankt@gmail.com" target="_blank">phamlankt@gmail.com</a>> wrote:<o:p></o:p></p></div><blockquote style='border:none;border-left:solid windowtext 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt;border-color:currentcolor currentcolor currentcolor rgb(204,204,204)'><div><div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>you are right, if i dropped the aforementioned index, analyze works without issue. As long as I tried to create the index again, it does not let me creating the index but throw the same error.<o:p></o:p></p></div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>But I wonder why it is working in the original database. What happened during the backup/restore that changed this?<o:p></o:p></p></div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Btw, I see some small difference in the output of the original database. May be it sounds something to you?<o:p></o:p></p><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>#This is the output from the original database<o:p></o:p></p></div><p class=MsoNormal style='mso-margin-top-alt:auto;margin-bottom:12.0pt'>geodm=# SELECT postgis_full_version();<br><br> postgis_full_version<br><br>--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------<br>--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------<br>---------------------------<br> POSTGIS="2.5.5" [EXTENSION] PGSQL="100" GEOS="3.9.2-CAPI-1.14.3" SFCGAL="1.3.1" PROJ="Rel. 7.2.1, January 1st, 2021" GDAL="GDAL 3.2.3, released 2021/04/27" LIBXML="2.9.1" LIBJSON="0.11" LIBPROT<br>OBUF="1.0.2" (core procs from "2.5.2 r17328" need upgrade) TOPOLOGY (topology procs from "2.5.2 r17328" need upgrade) RASTER (raster procs from "2.5.2 r17328" need upgrade) (sfcgal procs from "2<br>.5.2 r17328" need upgrade)<br>(1 row)<o:p></o:p></p></div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p><div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>On Mon, Mar 27, 2023 at 10:21 PM Regina Obe <<a href="mailto:lr@pcorp.us" target="_blank">lr@pcorp.us</a>> wrote:<o:p></o:p></p></div><blockquote style='border:none;border-left:solid windowtext 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt;border-color:currentcolor currentcolor currentcolor rgb(204,204,204)'><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Could be your ST_Transform index triggering the issue and you have at least one geometry out of bounds in there.<br><br>I’d try dropping your geobordervtc_geom_25832_idx and then rerunning analyze on the table.<br>If that does fix it then try to gigure out which geometry is at fault.<br><br>The 25632 is only good for utm zone 32N<br><br><a href="https://epsg.io/25832" target="_blank">https://epsg.io/25832</a><br><br>So I suspect you have a geometry way off from there causing the issue. <br><br>Or it could be missing grid datum shift files at fault too.<br><br>You can update your grid files by running at your command line:<br><br>projsync --all<br><br>As detailed here - <a href="https://proj.org/apps/projsync.html#index-0" target="_blank">https://proj.org/apps/projsync.html#index-0</a><br><br>--------------------------------------<br><br>From: postgis-users [mailto:<a href="mailto:postgis-users-bounces@lists.osgeo.org" target="_blank">postgis-users-bounces@lists.osgeo.org</a>] On Behalf Of pham lan<br>Sent: Monday, March 27, 2023 4:02 PM<br>To: PostGIS Users Discussion <<a href="mailto:postgis-users@lists.osgeo.org" target="_blank">postgis-users@lists.osgeo.org</a>><br>Subject: Re: [postgis-users] ERROR: transform: Point outside of projection domain (2050)<br><br>Hi Regina,<br>Here are more information:<br><br>geodm=# SELECT postgis_full_version();<br> postgis_full_version<br><br>--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------<br>----------------<br> POSTGIS="2.5.5" [EXTENSION] PGSQL="100" GEOS="3.9.2-CAPI-1.14.3" PROJ="Rel. 7.2.1, January 1st, 2021" GDAL="GDAL 3.2.3, released 2021/04/27" LIBXML="2.9.7" LIBJSON="0.13.1" LIBPROTOBUF="1.3.0"<br>TOPOLOGY RASTER<br>(1 row)<br><br><br><br>On Mon, Mar 27, 2023 at 9:43 PM Regina Obe <<a href="mailto:lr@pcorp.us" target="_blank">lr@pcorp.us</a>> wrote:<br>What’s the structure of the table in question?<br><br>\d+ name_of_table<br><br>Should give needed details.<br><br>Also output of <br><br>SELECT postgis_full_version();<br><br>From: postgis-users [mailto:<a href="mailto:postgis-users-bounces@lists.osgeo.org" target="_blank">postgis-users-bounces@lists.osgeo.org</a>] On Behalf Of pham lan<br>Sent: Monday, March 27, 2023 3:27 PM<br>To: PostGIS Users Discussion <<a href="mailto:postgis-users@lists.osgeo.org" target="_blank">postgis-users@lists.osgeo.org</a>><br>Subject: [postgis-users] ERROR: transform: Point outside of projection domain (2050)<br><br>Hi everyone,<br><br>I need your help to figure this out. I have a DB in postgresql 10 with postgis 2.5. I know postgresql 10 is not supported anymore and we have plan to upgrade it soon but it is a different story.<br>The thing is, I want to make a copy of this DB, so I tried a pg_basebackup to another postgres10+postgis 2.5 VM. After that, a vacuum went well but the analyzer throws an error on 1 specific table:<br>ERROR: transform: Point outside of projection domain (2050)<br>i tried also pg_dump/pg_restore but get the same error. Does anyone know what is the problem?<br><br>Thanks for your help!<br>Regards,<br>Lan<br>_______________________________________________<br>postgis-users mailing list<br><a href="mailto:postgis-users@lists.osgeo.org" target="_blank">postgis-users@lists.osgeo.org</a><br><a href="https://lists.osgeo.org/mailman/listinfo/postgis-users" target="_blank">https://lists.osgeo.org/mailman/listinfo/postgis-users</a><br><br>_______________________________________________<br>postgis-users mailing list<br><a href="mailto:postgis-users@lists.osgeo.org" target="_blank">postgis-users@lists.osgeo.org</a><br><a href="https://lists.osgeo.org/mailman/listinfo/postgis-users" target="_blank">https://lists.osgeo.org/mailman/listinfo/postgis-users</a><o:p></o:p></p></blockquote></div></blockquote></div></div></div></div><p class=MsoNormal>_______________________________________________<br>postgis-users mailing list<br><a href="mailto:postgis-users@lists.osgeo.org" target="_blank">postgis-users@lists.osgeo.org</a><br><a href="https://lists.osgeo.org/mailman/listinfo/postgis-users" target="_blank">https://lists.osgeo.org/mailman/listinfo/postgis-users</a><o:p></o:p></p></div></blockquote></div></div></div></body></html>