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

Tue Aug 29 12:08:22 PDT 2023

Got it, Thanks Regina!

On Tue, Aug 29, 2023 at 6:55 PM Regina Obe <lr at pcorp.us> wrote:

> I doubt we’ll be ending support of 3.1 in 2024 but we haven’t voted on it.
>
> We still need to EOL 3.0 too which we haven’t voted on either.
>
> So 3.0 will most likely be in 2023.  3.1 probably not because we don’t
> like to EOL two versions in 1 year.
>
>
>
> Also if there is no pressing reason to EOL, e.g the code hasn’t changed so
> much that we can’t apply security patches without rewriting the patch, we
> aren’t in that much of a rush.
>
>
>
> So too things that force us to EOL
>
>
>
>    1. Patches are harder to Apply
>    2. We no longer have CI bots that can comfortably test all the PGs
>    that were supported by that minor
>
>
>
> Thanks,
>
> Regina
>
>
>
> *From:* Nikhil Shetty <nikhil.dba04 at gmail.com>
> *Sent:* Tuesday, August 29, 2023 8:56 AM
> *To:* Regina Obe <lr at pcorp.us>
> *Cc:* PostGIS Users Discussion <postgis-users at lists.osgeo.org>
> *Subject:* Re: [postgis-devel] [postgis-users] PostGIS Known Issues :
> OEL7 to RHEL8 Upgrade
>
>
>
> Hi Regina,
>
>
>
> One quick question, as per doc regd EOL
>
>
>
> The PostGIS project strives to support each minor version of PostGIS for
> 2-4 years after initial release and at the very least until the lowest
> PostgreSQL version supported by the PostGIS minor version is EOL’d
>
>
>
> For PostGIS 3.1(released in 2020), the support will end in 2024? or after
> PostgreSQL 11 EOL i.e 2023(Next 2-3 months) ?
>
>
>
> I was thinking should we go for minor version upgrade (3.1.9) or move
> directly to major version (3.2 or 3.3) (will require more stringent tests)
>
>
>
> Thanks,
>
> Nikhil
>
>
>
>
>
> On Fri, Aug 25, 2023 at 8:06 PM Nikhil Shetty <nikhil.dba04 at gmail.com>
> wrote:
>
> Hi Regina, Greg,
>
>
>
> Thank you for the detailed explanation
>
>
>
> We will upgrade PostGIS to latest release and then migrate to RHEL8
>
>
>
> We will share with the community if there are any findings
>
>
>
> Thanks,
>
> Nikhil
>
>
>
> On Fri, 25 Aug 2023 at 19:37, Regina Obe <lr at pcorp.us> wrote:
>
> Nikhil,
>
>
>
> As Greg had stated in a related post, I’d advice not using a micro we no
> longer support.  I already pointed at all the issues with those here -
> https://git.osgeo.org/gitea/postgis/postgis/src/branch/stable-3.1/NEWS
>
>
>
> The BIG known issue is we can’t help you if anything goes wrong cause we
> don’t support PostGIS 3.1.2 and I honestly can’t remember that far back in
> time (2 years ago).
>
> That’s 7 unsupported micro releases ago paired with a PostgreSQL version
> that is 7 micro releases behind the latest stable PostgreSQL 13.  Yes I
> suspect you’ll have lots of issues.
>
>
>
> Any issues you run into using PostGIS 3.1.2 instead of any of our
> supported micros - https://postgis.net/development/source_code/
>
> are on you.  PostgreSQL group will have the same answer if you ask them if
> you have issues with a micro they stopped supporting a while ago.
>
> If you report an issue to either PostGIS or PostgreSQL groups, our answer
> will be  “Upgrade to the latest micro to make sure it’s not an issue we
> already solved” or go ask the group (e.g. vendor)
>
> who is asking you to run an out of date version of software.
>
>
>
> I also have no idea whether you are packaging your own or getting it from
> a distribution.
>
> Most of the issues that arise are how you package the dependencies, which
> versions you are running with and how it conflicts with stuff you already
> have installed or applications that depend on it.
>
>
>
> I’m also unclear what version of PostGIS you are upgrading from.  Telling
> me you are coming from RHEL7 tells me nothing since I have much newer minor
> versions of PostGIS running on RHEL 7 systems.
>
>
>
> You will need to report at the very least:
>
>
>
> SELECT version(), postgis_full_version();
>
>
>
> From your RHEL7 system and if you are doing a pg_dump and pg_restore or
> not.
>
>
>
> Generally running pg_dump / pg_restore is slowest way to upgrade but least
> hassle of issues so easiest to go if you have few databases or a small
> database.
>
> Doing a replication and then pg_upgrade after is the fastest way to
> upgrade and what I do for databases in the high gigabytes or terabytes
> (least amount of downtime), but there are lots of gotchas with that such as
>
> What I mentioned here:
> https://www.bostongis.com/blog/index.php?/archives/273-Using-pg_upgrade-to-upgrade-PostgreSQL-9.3-PostGIS-2.1-to-PostgreSQL-11-2.5-on-Yum.html
>
>
>
> There are also often issues that arise with PROJ, but those should be less
> so since you are not trying to upgrade on the same system.
>
>
>
>
>
> Hope that helps,
>
> Regina
>
>
>
> *From:* postgis-devel <postgis-devel-bounces at lists.osgeo.org> *On Behalf
> Of *Nikhil Shetty
> *Sent:* Friday, August 25, 2023 4:03 AM
> *To:* PostGIS Users Discussion <postgis-users at lists.osgeo.org>
> *Cc:* PostGIS Development Discussion <postgis-devel at lists.osgeo.org>
> *Subject:* Re: [postgis-devel] [postgis-users] PostGIS Known Issues :
> OEL7 to RHEL8 Upgrade
>
>
>
> Hi Regina,
>
>
>
> Please let us know if upgrading to RHEL8 with 3.1.2 would be an issue or
> any other known issues with PostGIS
>
>
>
> Thanks,
>
> Nikhil
>
>
>
> On Thu, 24 Aug 2023 at 08:24, Nikhil Shetty <nikhil.dba04 at gmail.com>
> wrote:
>
>
>
> Hi Regina,
>
>
>
> We do have plans to upgrade both Postgres and PostGIS to higher versions
> but currently we are focusing on OS upgrade to RHEL8
>
>
>
> Do you think being on PostGIS 3.1.2 will impact OS upgrade? Are there any
> known issues
>
>
>
> Thanks,
>
> Nikhil
>
>
>
> On Wed, 23 Aug 2023 at 23:41, Regina Obe <lr at pcorp.us> wrote:
>
> 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
>
> _______________________________________________
> postgis-users mailing list
> postgis-users at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/postgis-users
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-users/attachments/20230830/f32a02db/attachment.htm>