<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;}
@font-face
{font-family:"Comic Sans MS";
panose-1:3 15 7 2 3 3 2 2 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-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;}
span.EmailStyle17
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@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='color:#1F497D'>So I’m curious is 11.14 not supported on GovCloud.<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>Doing micro updates should not require any downtime or very miniscule downtime because the data doesn’t need to be fixed to go up to 11.14.<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>So it really should be just flipping the switch.<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>So 11.14 is really where you want to be for security /bugfix patches anyway. <o:p></o:p></span></p><p class=MsoNormal><span style='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>From:</b> Allan Chase [mailto:allan.chase@bluestaq.com] <br><b>Sent:</b> Monday, February 14, 2022 10:52 PM<br><b>To:</b> Regina Obe <lr@pcorp.us>; 'PostGIS Users Discussion' <postgis-users@lists.osgeo.org><br><b>Subject:</b> RE: [External] RE: [postgis-users] [External] Re: Postgis 3.0.3 extension for AWS RDS Postgres 13.3<o:p></o:p></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Thanks Regina,<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Yeah, I saw that link that you referenced (a few days back) and I kind of went…hmmmm. From that chart, you can upgrade to 3.1.X if you just go from 11.12 to 11.13 (or 14), but the thing that caught me a little off guard was:<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><a href="https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/CHAP_PostgreSQL.html#PostgreSQL.Concepts.General.FeatureSupport.Extensions.13x">PostgreSQL on Amazon RDS - Amazon Relational Database Service</a><o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal>I will definitely try your suggestions below. All this is technically for a system that currently only goes as high as 13.3, so I’m currently stuck with 3.0.3 (this is all on “Gov Cloud”).<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>The main driver for me to want to jump right to 13 was to minimize our down time since it is a production system. If the best answer is to jump from 11 to 12 to 13, I’ll just need to make sure I quantify the downtime (probably 45 minutes – hour) which is fine.<o:p></o:p></p><p class=MsoNormal><span style='font-family:"Comic Sans MS"'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-family:"Comic Sans MS"'>Allan Chase<o:p></o:p></span></p><p class=MsoNormal>Data Engineer<o:p></o:p></p></div><p class=MsoNormal><o:p> </o:p></p><div><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b>From:</b> Regina Obe <<a href="mailto:lr@pcorp.us">lr@pcorp.us</a>> <br><b>Sent:</b> Monday, February 14, 2022 7:10 PM<br><b>To:</b> 'PostGIS Users Discussion' <<a href="mailto:postgis-users@lists.osgeo.org">postgis-users@lists.osgeo.org</a>>; Allan Chase <<a href="mailto:allan.chase@bluestaq.com">allan.chase@bluestaq.com</a>><br><b>Subject:</b> [External] RE: [postgis-users] [External] Re: Postgis 3.0.3 extension for AWS RDS Postgres 13.3<o:p></o:p></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>**************************************************************************<br>ATTENTION: External email <br>Please verify the sender before taking any actions or clicking any links. <br>************************************************************************** <o:p></o:p></p><div><p class=MsoNormal><span style='color:#1F497D'>Allan,<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>Looking at this chart, it looks like you can upgrade from PostGIS 2.5 to 3.1 on PostgreSQL 11 right?<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><a href="https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/CHAP_PostgreSQL.html#PostgreSQL.Concepts.General.FeatureSupport.Extensions.11x">https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/CHAP_PostgreSQL.html#PostgreSQL.Concepts.General.FeatureSupport.Extensions.11x</a><o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>Says PostGIS 3.1 is available for 11.14.<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>That would be a safer bet to upgrade your PostgreSQL 11 first to 3.1.<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>PostgreSQL 13 removed CREATE EXTENSION from unpackaged, which I think the 3.0 release relies on, so that would be one reason why you can’t go from 2.5.2 to 3.0.3.<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>I think we introduced the work-around for that in PostGIS 3.1.<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>So options that theoretically should work<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>Go from your PG 11- PostGIS 2.5.2 to PostGIS 3.1.4<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>Then upgrade from<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>PG 11 PostGIS 3.1.4 -> PG 13 PostGIS 3.1.4<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>Or if you really badly want to go straight to 13<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>PG 11 2.5.2 -> PG 13.5 (which does have PostGIS 3.1.4)<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><a href="https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/CHAP_PostgreSQL.html#PostgreSQL.Concepts.General.FeatureSupport.Extensions.13x">https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/CHAP_PostgreSQL.html#PostgreSQL.Concepts.General.FeatureSupport.Extensions.13x</a><o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>Hope that helps,<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>Regina<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='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>From:</b> Regina Obe [<a href="mailto:lr@pcorp.us">mailto:lr@pcorp.us</a>] <br><b>Sent:</b> Monday, February 14, 2022 8:46 PM<br><b>To:</b> 'PostGIS Users Discussion' <<a href="mailto:postgis-users@lists.osgeo.org">postgis-users@lists.osgeo.org</a>>; 'Allan Chase' <<a href="mailto:allan.chase@bluestaq.com">allan.chase@bluestaq.com</a>><br><b>Cc:</b> 'Sandro Santilli' <<a href="mailto:strk@kbt.io">strk@kbt.io</a>><br><b>Subject:</b> RE: [postgis-users] [External] Re: Postgis 3.0.3 extension for AWS RDS Postgres 13.3<o:p></o:p></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span style='color:#1F497D'>strk,<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>AWS doesn’t allow the below. But I think it should work as part of the ALTER EXTENSION as you have it in 3.3 as that runs under a higher level account.<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>Allan,<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>Can you output what your<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>SELECT * FROM pg_extension WHERE extname =’postgis’;<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>Shows and confirm it does say 2.5.2.<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>If it says something like 2.5.2next then do:<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>ALTER EXTENSION postgis UPDATE TO '2.5.2';<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>Also run:<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>SELECT postgis_full_version();<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>At any rate, Raj might be right that upgrading from 11 to 13 for PostGIS is not supported on AWS. Most people I’ve known on AWS first upgrade to 12 first.<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>Thanks,<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>Regina<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='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>From:</b> postgis-users [<a href="mailto:postgis-users-bounces@lists.osgeo.org">mailto:postgis-users-bounces@lists.osgeo.org</a>] <b>On Behalf Of </b>Allan Chase<br><b>Sent:</b> Monday, February 14, 2022 6:26 PM<br><b>To:</b> Raj Talati <<a href="mailto:rajtalati@gmail.com">rajtalati@gmail.com</a>>; PostGIS Users Discussion <<a href="mailto:postgis-users@lists.osgeo.org">postgis-users@lists.osgeo.org</a>><br><b>Subject:</b> Re: [postgis-users] [External] Re: Postgis 3.0.3 extension for AWS RDS Postgres 13.3<o:p></o:p></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>According to <a href="https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_UpgradeDBInstance.PostgreSQL.html">Upgrading the PostgreSQL DB engine for Amazon RDS - Amazon Relational Database Service</a>, one can upgrade from 11.12 right to 13.3.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal><span style='font-family:"Comic Sans MS"'>Allan Chase<o:p></o:p></span></p><p class=MsoNormal>Data Engineer<o:p></o:p></p></div><p class=MsoNormal><o:p> </o:p></p><div><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b>From:</b> Raj Talati <<a href="mailto:rajtalati@gmail.com">rajtalati@gmail.com</a>> <br><b>Sent:</b> Monday, February 14, 2022 4:08 PM<br><b>To:</b> Allan Chase <<a href="mailto:allan.chase@bluestaq.com">allan.chase@bluestaq.com</a>>; PostGIS Users Discussion <<a href="mailto:postgis-users@lists.osgeo.org">postgis-users@lists.osgeo.org</a>><br><b>Subject:</b> [External] Re: [postgis-users] Postgis 3.0.3 extension for AWS RDS Postgres 13.3<o:p></o:p></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>**************************************************************************<br>ATTENTION: External email <br>Please verify the sender before opening attachments or clicking links. <br>************************************************************************** <o:p></o:p></p><div><div><p class=MsoNormal>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 .<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Hope this helps.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p><div><div><p class=MsoNormal>On Mon, Feb 14, 2022 at 5:40 PM Sandro Santilli <<a href="mailto:strk@kbt.io">strk@kbt.io</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-top:5.0pt;margin-right:0in;margin-bottom:5.0pt'><p class=MsoNormal>On Mon, Feb 14, 2022 at 03:33:29PM -0500, Regina Obe wrote:<br><br>> the workaround is below, but not sure it will work on AWS<br>> RDS as updating system tables might be off limits.<br>> <br>> UPDATE pg_extension SET extversion = 'ANY'<br>> WHERE extname = 'postgis';<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" target="_blank">https://lists.osgeo.org/mailman/listinfo/postgis-users</a><o:p></o:p></p></blockquote></div></div></div></div></div></div></div></div></body></html>