<div dir="ltr">Roxanne, Allan and Regina,<div><br></div><div>Thanks so much for your help.</div><div><br></div><div>I created a snapshot backup, restored to a new test rds instance, and ran the sql attachment "Spatial Types for PostgreSQL" that you highlighted. That's a great find. My google sleuthing didn't uncover that one. Running that script cleared up the postgis_full_version raster issues:</div><div><blockquote style="margin:0 0 0 40px;border:none;padding:0px"><div><font face="monospace">db=> SELECT postgis_full_version();<br></font></div><div><font face="monospace">POSTGIS="3.1.7 aafe1ff" [EXTENSION] PGSQL="120" (procs need upgrade for use with PostgreSQL "130") GEOS="3.9.1-CAPI-1.14.2" PROJ="8.0.1" LIBXML="2.9.1" LIBJSON="0.13.1" LIBPROTOBUF="1.3.2" WAGYU="0.5.0 (Internal)"<br>(1 row)</font><br></div></blockquote><div><br></div>No more warning about raster being unbundled and requiring an upgrade, but the PGSQL warning is new. I then did the following:</div><div><blockquote style="margin:0 0 0 40px;border:none;padding:0px"><div><font face="monospace">db=> SELECT postgis_extensions_upgrade();<br>NOTICE: Updating extension postgis 3.1.7<br>NOTICE: Extension postgis_raster is not available or not packagable for some reason<br>NOTICE: Extension postgis_topology is not available or not packagable for some reason<br>NOTICE: Extension postgis_tiger_geocoder is not available or not packagable for some reason<br> postgis_extensions_upgrade<br>-------------------------------------------------------------------<br> Upgrade completed, run SELECT postgis_full_version(); for details<br>(1 row)</font><br></div><div><font face="monospace"><br></font></div><div><font face="monospace">db=> SELECT postgis_full_version();<br></font></div><div><font face="monospace">POSTGIS="3.1.7 aafe1ff" [EXTENSION] PGSQL="130" GEOS="3.9.1-CAPI-1.14.2" PROJ="8.0.1" LIBXML="2.9.1" LIBJSON="0.13.1" LIBPROTOBUF="1.3.2" WAGYU="0.5.0 (Internal)"<br>(1 row)</font></div></blockquote></div><div><br></div><div>Success!</div><div><br></div><div>Then I requested an aws upgrade to the test instance via the console and it succeeded! I anticipate the same should work on the production db. I'll give it a try during our next maintenance period.</div><div><br></div><div>Thanks again for everyone's help. Allan, I might need to borrow your hair color after all of this. ;-)</div><div><br></div><div>->jvp<br><blockquote style="margin:0 0 0 40px;border:none;padding:0px"><div><br></div></blockquote></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Jan 24, 2023 at 12:07 AM Regina Obe <<a href="mailto:lr@pcorp.us">lr@pcorp.us</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div class="msg-267313196745718795"><div lang="EN-US"><div class="m_-267313196745718795WordSection1"><p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)">Jim,<u></u><u></u></span></p><p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"><u></u> <u></u></span></p><p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)">Sorry I had missed the thread Roxanne had written.<u></u><u></u></span></p><p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"><u></u> <u></u></span></p><p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)">So you already ran twice<u></u><u></u></span></p><p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"><u></u> <u></u></span></p><p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)">SELECT postgis_extensions_upgrade(); <u></u><u></u></span></p><p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)">SELECT postgis_extensions_upgrade(); <u></u><u></u></span></p><p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"><u></u> <u></u></span></p><p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)">And still shows raster is UNPACKAGED.<u></u><u></u></span></p><p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)">If you did delete some raster functions in panic, then I think that would prevent it from being upgraded.<u></u><u></u></span></p><p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"><u></u> <u></u></span></p><p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)">You want to first make sure you don’t have raster tables running the below query should return no records.<u></u><u></u></span></p><p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"><u></u> <u></u></span></p><p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)">SELECT *<u></u><u></u></span></p><p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)">FROM raster_columns;<u></u><u></u></span></p><p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"><u></u> <u></u></span></p><p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"><u></u> <u></u></span></p><p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)">Easy fix especially if you don’t need raster support, is to run the uninstall raster script I had attached in that mailing list thread Roxanne pointed to<u></u><u></u></span></p><p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"><u></u> <u></u></span></p><p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"><a href="https://lists.osgeo.org/pipermail/postgis-users/attachments/20200529/e32c5d8c/attachment.obj" target="_blank">https://lists.osgeo.org/pipermail/postgis-users/attachments/20200529/e32c5d8c/attachment.obj</a><u></u><u></u></span></p><p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"><u></u> <u></u></span></p><p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"><u></u> <u></u></span></p><p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)">That should cleanly get rid of all remnants of raster. <u></u><u></u></span></p><p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"><u></u> <u></u></span></p><p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)">Hope that helps,<u></u><u></u></span></p><p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)">Regina<u></u><u></u></span></p><p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"><u></u> <u></u></span></p><p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"><u></u> <u></u></span></p><p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"><u></u> <u></u></span></p><div style="border-top:none;border-right:none;border-bottom:none;border-left:1.5pt solid blue;padding:0in 0in 0in 4pt"><div><div style="border-right:none;border-bottom:none;border-left:none;border-top:1pt solid rgb(225,225,225);padding:3pt 0in 0in"><p class="MsoNormal"><b><span style="font-size:11pt;font-family:Calibri,sans-serif">From:</span></b><span style="font-size:11pt;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>Roxanne Reid-Bennett<br><b>Sent:</b> Monday, January 23, 2023 9:29 PM<br><b>To:</b> <a href="mailto:postgis-users@lists.osgeo.org" target="_blank">postgis-users@lists.osgeo.org</a><br><b>Subject:</b> Re: [postgis-users] Upgrade 12->13 stuck due to postgis / raster issue<u></u><u></u></span></p></div></div><p class="MsoNormal"><u></u> <u></u></p><p>Jim,<u></u><u></u></p><p>I did a search on this phrase:<u></u><u></u></p><blockquote style="margin-top:5pt;margin-bottom:5pt"><p class="MsoNormal">raster procs from "2.5.2 r17328" need upgrade<u></u><u></u></p></blockquote><p>I found a post from Regina from 2020 moving from 2.5.2 to 3. It might illumine a bit.<u></u><u></u></p><blockquote style="margin-top:5pt;margin-bottom:5pt"><p><a href="https://lists.osgeo.org/pipermail/postgis-users/2020-May/044225.html" target="_blank">https://lists.osgeo.org/pipermail/postgis-users/2020-May/044225.html</a><u></u><u></u></p></blockquote><p class="MsoNormal"><u></u> <u></u></p><p>And this one for someone who had 100% control of their PG hardware from last fall.<u></u><u></u></p><blockquote style="margin-top:5pt;margin-bottom:5pt"><p><a href="https://groups.google.com/g/postgis-users/c/26iNuhXFHgg" target="_blank">https://groups.google.com/g/postgis-users/c/26iNuhXFHgg</a><u></u><u></u></p></blockquote><p><u></u> <u></u></p><p>And this one from the AWS forums <u></u><u></u></p><blockquote style="margin-top:5pt;margin-bottom:5pt"><p><a href="https://repost.aws/questions/QUEk9HG5x3Qq6sEB3lVmynUw/upgrade-from-postgres-12-7-r-1-to-13-3-r-1-stuck" target="_blank">https://repost.aws/questions/QUEk9HG5x3Qq6sEB3lVmynUw/upgrade-from-postgres-12-7-r-1-to-13-3-r-1-stuck</a><u></u><u></u></p><p>which references this:<u></u><u></u></p><p><a href="https://stackoverflow.com/questions/42634626/postgresql-upgrade-on-amazon-rds-blocked-by-postgis-version" target="_blank">https://stackoverflow.com/questions/42634626/postgresql-upgrade-on-amazon-rds-blocked-by-postgis-version</a><u></u><u></u></p><p>which uses <u></u><u></u></p><pre style="vertical-align:baseline;font-variant-ligatures:normal;font-variant-caps:normal;font-variant-numeric:inherit;font-variant-east-asian:inherit;font-stretch:inherit;box-sizing:inherit;max-height:600px;text-decoration-style:initial;text-decoration-color:initial;overflow:auto;word-spacing:0px"><span class="m_-267313196745718795hljs-keyword"><span style="font-family:"inherit",serif;border:1pt none windowtext;padding:0in">ALTER EXTENSION postgis UPDATE;<u></u><u></u></span></span></pre></blockquote><p>The observation in the last post about waiting overnight and things "magically being fixed", I saw during our dry run, not the production run, but definitely during the dry run. Their observation about rebooting the PG server between upgrades isn't totally "off" either.<u></u><u></u></p><p>Posting in the AWS Forums might get some help from inside Amazon.<u></u><u></u></p><p>Or, if you have any level of support from AWS that would allow you get someone to "poke/prod" on disk, you might get a fix. <u></u><u></u></p><p>Migrating the data is "of course" a last resort, but at least possible. <u></u><u></u></p><p>Given my lack of knowledge of the upgrade steps, I've done what I can. Good luck.<u></u><u></u></p><p>Roxanne<u></u><u></u></p></div></div></div>_______________________________________________<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" rel="noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/postgis-users</a><br>
</div></blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr" class="gmail_signature"><div dir="ltr"><div>______________________________</div><div>Jim VanPeursem, PhD</div><div><a href="http://jvpcoaching.com/" target="_blank">http://jvp.llc</a>/</div><div><span style="font-size:12.8px">us: </span><span title="Call with Google Voice" style="font-size:12.8px"><span title="Call with Google Voice"><span title="Call with Google Voice"><span title="Call with Google Voice"><span title="Call with Google Voice"><span title="Call with Google Voice"><span title="Call with Google Voice"><span title="Call with Google Voice"><span title="Call with Google Voice"><span title="Call with Google Voice">+1 847 414 2759</span></span></span></span></span></span></span></span></span></span><span style="font-size:12.8px"> (+ WhatsApp) -- </span><span style="font-size:12.8px">skype: jimvanpeursem</span><br></div><div><b><i>Bringing clarity and helping you go from where you are to where you want to be</i></b></div></div></div>