[prev in list] [next in list] [prev in thread] [next in thread] 

List:       postgis-users
Subject:    Re: [postgis-users] Postgis 3.0.3 extension for AWS RDS Postgres 13.3
From:       Raj Talati <rajtalati () gmail ! com>
Date:       2022-02-14 23:07:30
Message-ID: CAP7G0B4Sy4fPjga36V2pNvec0psUA+a4LDYh4Y93LOTgBHWwcw () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


If this AWS RDS you cannot upgrade directly from 11.x to 13.x . You will
need to upgrade to 12.x and if you did like upgraded 11.x to 12.x and the.
Upgraded fro 12.x to 13.3 then when you upgraded from 11.x to 12.x you need
to upgrade Postgis too as AWS as that should allow you to upgrade postgis
and then when you upgrade Postgres to 13 you should able to upgrade Postgis
too. If we bypass Postgis upgrade while going from 11-> 12 and just so
while doing 12->13 you will face this issue .

Hope this helps.

On Mon, Feb 14, 2022 at 5:40 PM Sandro Santilli <strk@kbt.io> wrote:

> On Mon, Feb 14, 2022 at 03:33:29PM -0500, Regina Obe wrote:
>
> > the workaround is below, but not sure it will work on AWS
> > RDS as updating system tables might be off limits.
> >
> > UPDATE pg_extension SET extversion = 'ANY'
> > WHERE extname = 'postgis';
>
> Allan: please let us know if AWS RDS allows or not the above
> UPDATE, as we are planning to use that construct for
> the postgis_extensions_upgrade() function in PostGIS-3.3.0
>
> --strk;
> _______________________________________________
> postgis-users mailing list
> postgis-users@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/postgis-users
>

[Attachment #5 (text/html)]

<div dir="auto">If this AWS RDS you cannot upgrade directly from 11.x to 13.x . You \
will need to upgrade to 12.x and if you did like upgraded 11.x to 12.x and the. \
Upgraded fro 12.x to 13.3 then when you upgraded from 11.x to 12.x you need to \
upgrade Postgis too as AWS as that should allow you to upgrade postgis and then when \
you upgrade Postgres to 13 you should able to upgrade Postgis too. If we bypass \
Postgis upgrade while going from 11-&gt; 12 and just so while doing 12-&gt;13 you \
will face this issue .</div><div dir="auto"><br></div><div dir="auto">Hope this  \
helps.</div><div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On \
Mon, Feb 14, 2022 at 5:40 PM Sandro Santilli &lt;<a \
href="mailto:strk@kbt.io">strk@kbt.io</a>&gt; wrote:<br></div><blockquote \
class="gmail_quote" style="margin:0px 0px 0px \
0.8ex;border-left-width:1px;border-left-style:solid;padding-left:1ex;border-left-color:rgb(204,204,204)">On \
Mon, Feb 14, 2022 at 03:33:29PM -0500, Regina Obe wrote:<br> <br>
&gt; the workaround is below, but not sure it will work on AWS<br>
&gt; RDS as updating system tables might be off limits.<br>
&gt; <br>
&gt; UPDATE pg_extension SET extversion = &#39;ANY&#39;<br>
&gt; WHERE extname = &#39;postgis&#39;;<br>
<br>
Allan: please let us know if AWS RDS allows or not the above<br>
UPDATE, as we are planning to use that construct for<br>
the postgis_extensions_upgrade() function in PostGIS-3.3.0<br>
<br>
--strk;<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" rel="noreferrer" \
target="_blank">https://lists.osgeo.org/mailman/listinfo/postgis-users</a><br> \
</blockquote></div></div>



_______________________________________________
postgis-users mailing list
postgis-users@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/postgis-users


[prev in list] [next in list] [prev in thread] [next in thread]