[postgis-users] Postgis 3.0.3 extension for AWS RDS Postgres 13.3
Allan Chase
If there isn't a Postgis upgrade path when upgrading Postgres 11.12 (2.5.2) to 13.3 (3.0.3), can we just drop the extension, do the upgrade, then re-create the extension in the new database? I get an error message saying that it can't upgrade due to "no upgrade path" for 2.5.2 to 3.0.3.
Allan Chase
Data Engineer
_______________________________________________
postgis-users mailing list
postgi...@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/postgis-users
Regina Obe
Are you able to hold off? I think Amazon should be releasing an update
soon.
If you can't wait, 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';
ALTER EXTENSION postgis UPDATE;
SELECT postgis_extensions_upgrade();
Sandro Santilli
> 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';
UPDATE, as we are planning to use that construct for
the postgis_extensions_upgrade() function in PostGIS-3.3.0
--strk;
Raj Talati
Allan Chase
According to Upgrading the PostgreSQL DB engine for Amazon RDS - Amazon Relational Database Service, one can upgrade from 11.12 right to 13.3.
Allan Chase
Data Engineer
From: Raj Talati <rajt...@gmail.com>
Sent: Monday, February 14, 2022 4:08 PM
To: Allan Chase <allan...@bluestaq.com>; PostGIS Users Discussion <postgi...@lists.osgeo.org>
Subject: [External] Re: [postgis-users] Postgis 3.0.3 extension for AWS RDS Postgres 13.3
**************************************************************************
ATTENTION: External email
Please verify the sender before opening attachments or clicking links.
**************************************************************************
Raj Talati
Regina Obe
strk,
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.
Allan,
Can you output what your
SELECT * FROM pg_extension WHERE extname =’postgis’;
Shows and confirm it does say 2.5.2.
If it says something like 2.5.2next then do:
ALTER EXTENSION postgis UPDATE TO '2.5.2';
Also run:
SELECT postgis_full_version();
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.
Thanks,
Regina
From: postgis-users [mailto:postgis-us...@lists.osgeo.org] On Behalf Of Allan Chase
Regina Obe
Allan,
Looking at this chart, it looks like you can upgrade from PostGIS 2.5 to 3.1 on PostgreSQL 11 right?
Says PostGIS 3.1 is available for 11.14.
That would be a safer bet to upgrade your PostgreSQL 11 first to 3.1.
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.
I think we introduced the work-around for that in PostGIS 3.1.
So options that theoretically should work
Go from your PG 11- PostGIS 2.5.2 to PostGIS 3.1.4
Then upgrade from
PG 11 PostGIS 3.1.4 -> PG 13 PostGIS 3.1.4
Or if you really badly want to go straight to 13
PG 11 2.5.2 -> PG 13.5 (which does have PostGIS 3.1.4)
Hope that helps,
Regina
From: Regina Obe [mailto:l...@pcorp.us]
Sent: Monday, February 14, 2022 8:46 PM
To: 'PostGIS Users Discussion' <postgi...@lists.osgeo.org>; 'Allan Chase' <allan...@bluestaq.com>
Cc: 'Sandro Santilli' <st...@kbt.io>
Subject: RE: [postgis-users] [External] Re: Postgis 3.0.3 extension for AWS RDS Postgres 13.3
strk,
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.
Allan,
Can you output what your
SELECT * FROM pg_extension WHERE extname =’postgis’;
Shows and confirm it does say 2.5.2.
If it says something like 2.5.2next then do:
ALTER EXTENSION postgis UPDATE TO '2.5.2';
Also run:
SELECT postgis_full_version();
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.
Thanks,
Regina
From: postgis-users [mailto:postgis-us...@lists.osgeo.org] On Behalf Of Allan Chase
Sent: Monday, February 14, 2022 6:26 PM
Allan Chase
Thanks Regina,
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:
PostgreSQL on Amazon RDS - Amazon Relational Database Service
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”).
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.
Allan Chase
Data Engineer
From: Regina Obe <l...@pcorp.us>
Sent: Monday, February 14, 2022 7:10 PM
To: 'PostGIS Users Discussion' <postgi...@lists.osgeo.org>; Allan Chase <allan...@bluestaq.com>
Subject: [External] RE: [postgis-users] [External] Re: Postgis 3.0.3 extension for AWS RDS Postgres 13.3
**************************************************************************
ATTENTION: External email
Please verify the sender before taking any actions or clicking any links.
**************************************************************************
Regina Obe
So I’m curious is 11.14 not supported on GovCloud.
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.
So it really should be just flipping the switch.
So 11.14 is really where you want to be for security /bugfix patches anyway.