[postgis-users] [postgis-devel] PostGIS Known Issues : OEL7 to RHEL8 Upgrade

[Regina Obe]

3.1.2 is not the latest stable release for 3.1, so you really shouldn’t be using that.  The 3.1.2 is before the PostgreSQL security vulnerability patches for example and numerous bugs have been fixed since then.

 

Latest 3.1 is 3.1.9

 

https://postgis.net/2023/05/PostGIS-3.3.3-3.2.5-3.1.9-3.0.9-Patch-Releases/

News specific for 3.1 - https://git.osgeo.org/gitea/postgis/postgis/raw/tag/3.1.9/NEWS

 

I would say the same holds true for PostgreSQL 13.12 is the latest stable, so not sure why you are trying to use a version several micro updates behind

 

https://www.postgresql.org/about/news/postgresql-154-149-1312-1216-1121-and-postgresql-16-beta-3-released-2689/

 

 

Hope that helps,

Regina

 

 

From: postgis-devel [mailto:postgis-devel-bounces at lists.osgeo.org] On Behalf Of Nikhil Shetty
Sent: Wednesday, August 23, 2023 2:02 PM
To: PostGIS Development Discussion <postgis-devel at lists.osgeo.org>; postgis-users at lists.osgeo.org
Subject: [postgis-devel] PostGIS Known Issues : OEL7 to RHEL8 Upgrade

 

Hi Team, 

 

We want to know if there are any open/known issues that we may face post-migration of the Postgres database  instance  with PostGIS enabled from centos7/RHEL7/OEL7 to RHEL8. 

 

We came across one issue regarding collation(https://wiki.postgresql.org/wiki/Locale_data_changes), the solution for which is to reindex or use logical replication. This is not related to PostGIS but still a concern causing index corruption 

 

In a similar way, we want to understand if there are any other known issues related to PostGIS that should be taken care of

 

PostgreSQL : 13.6

PostGIS : 3.1.2

 

Thanks and Regards,

Nikhil

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-users/attachments/20230823/79fce523/attachment.htm>