<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>Jim,</p>
<p>I did a search on this phrase:<br>
</p>
<blockquote type="cite"
cite="mid:CADJG2i7uKCNZ3jMkZknn7Q9PUkvf2Ez3DbpJV3b75L3vGa17Gw@mail.gmail.com">raster
procs from "2.5.2 r17328" need upgrade</blockquote>
<p>I found a post from Regina from 2020 moving from 2.5.2 to 3. It
might illumine a bit.</p>
<blockquote>
<p><a class="moz-txt-link-freetext" href="https://lists.osgeo.org/pipermail/postgis-users/2020-May/044225.html">https://lists.osgeo.org/pipermail/postgis-users/2020-May/044225.html</a></p>
</blockquote>
<br>
<p>And this one for someone who had 100% control of their PG
hardware from last fall.<br>
</p>
<blockquote>
<p><a class="moz-txt-link-freetext" href="https://groups.google.com/g/postgis-users/c/26iNuhXFHgg">https://groups.google.com/g/postgis-users/c/26iNuhXFHgg</a></p>
</blockquote>
<p><br>
</p>
<p>And this one from the AWS forums <br>
</p>
<blockquote>
<p><a class="moz-txt-link-freetext" href="https://repost.aws/questions/QUEk9HG5x3Qq6sEB3lVmynUw/upgrade-from-postgres-12-7-r-1-to-13-3-r-1-stuck">https://repost.aws/questions/QUEk9HG5x3Qq6sEB3lVmynUw/upgrade-from-postgres-12-7-r-1-to-13-3-r-1-stuck</a></p>
<p>which references this:</p>
<p><a class="moz-txt-link-freetext" href="https://stackoverflow.com/questions/42634626/postgresql-upgrade-on-amazon-rds-blocked-by-postgis-version">https://stackoverflow.com/questions/42634626/postgresql-upgrade-on-amazon-rds-blocked-by-postgis-version</a></p>
<p>which uses <br>
</p>
<pre class="lang-sql s-code-block" style="margin: 0px; padding: var(--su12); border: 0px; font-style: normal; font-variant-ligatures: normal; font-variant-caps: normal; font-variant-numeric: inherit; font-variant-east-asian: inherit; font-weight: 400; font-stretch: inherit; line-height: var(--lh-md); font-family: var(--ff-mono); font-size: var(--fs-body1); vertical-align: baseline; box-sizing: inherit; width: auto; max-height: 600px; overflow: auto; background-color: var(--highlight-bg); border-radius: var(--br-md); --_cb-line-numbers-bg:var(--black-050); color: var(--highlight-color); overflow-wrap: normal; letter-spacing: normal; orphans: 2; text-align: left; text-indent: 0px; text-transform: none; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration-thickness: initial; text-decoration-style: initial; text-decoration-color: initial;"><code class="hljs language-sql" style="margin: 0px; padding: 0px; border: 0px; font-style: inherit; font-variant: inherit; font-weight: inherit; font-stretch: inherit; line-height: inherit; font-family: inherit; font-size: var(--_pr-code-fs); vertical-align: baseline; box-sizing: inherit; background-color: transparent; white-space: inherit;"><span class="hljs-keyword" style="margin: 0px; padding: 0px; border: 0px; font-style: inherit; font-variant: inherit; font-weight: inherit; font-stretch: inherit; line-height: inherit; font-family: inherit; font-size: 13px; vertical-align: baseline; box-sizing: inherit; color: var(--highlight-keyword);">ALTER EXTENSION postgis UPDATE;
</span></code></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.<br>
</p>
<p>Posting in the AWS Forums might get some help from inside Amazon.</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. </p>
<p>Migrating the data is "of course" a last resort, but at least
possible. <br>
</p>
<p>Given my lack of knowledge of the upgrade steps, I've done what I
can. Good luck.<br>
</p>
<p>Roxanne<br>
</p>
</body>
</html>