Hi Regina,
We are upgrading from 3.1.2 to 3.3.3.
So, after we run below command the only option to rollback to previous
PostGIS version is to install old binaries and restore data from backup?
SELECT postgis_extensions_upgrade();
Thanks,
Nikhil
On Mon, 26 Feb 2024 at 20:23, Regina Obe wrote:
Got it.
Thank you!
On Mon, 26 Feb 2024 at 20:17, Regina Obe wrote:
> yum.postgresql.org has already discontinued support for rhel-7 so I
> would presume so.
>
>
>
> *From:* Nikhil Shetty
> *Sent:* Monday, February 26, 2024 6:27 AM
> *To:* PostGIS Users Discussion
> *Subject:* PostGIS 3.3
Correct. Well that is the safest way cause we don’t support downgrades.
In theory if you just ran with the older binaries with newer scripts, what
you’d have is all the new functions added between 3.1 and 3.3 broken.
You could then just manually run the 3.1 script, but you’d need to
I am very happy to have found the reason.
The client's development database is based on pg12. They modified the
nodes.h file and added two enumerations above
T_SupportRequestIndexCondition. Since the client downloaded pg12-postgis
from postgis.org, the installation file is based on the pg12
Thank you very much, I think this is sufficient.
I found https://github.com/pramsey/postgis-build-windows written by
pramsey, which is very helpful for compiling on Windows.
I will share any new progress.
As a tip, if you encounter "cache lookup failed for operator family 0."
again, you can look
Dapeng,
Is there a reason they found a need to hack their PostgreSQL 12. Can they
maybe use a newer version of PostgreSQL for their windows testing.
I haven’t had time to update instructions for building on windows. It’s very
complicated with all the dependencies needed.
The steps
Hi Team,
We are looking at options available to rollback a PostGIS upgrade in case
there are issues after the upgrade.
Apart from removing new packages and installing old ones and then restoring
the database from backup , do we have any other option?
Thanks,
Nikhil
Hi Team,
I was not able to find the rpm packages for the latest releases of PostGIS
3.3 for rhel7
The latest available version is 3.3.3
https://download.postgresql.org/pub/repos/yum/15/redhat/rhel-7-x86_64/
whereas for rhel8, all the latest releases(3.3.4, 3.3.5 and 3.3.6) are
available. Is it
Hi,
On Mon, 2024-02-26 at 16:56 +0530, Nikhil Shetty wrote:
> I was not able to find the rpm packages for the latest releases of
> PostGIS 3.3 for rhel7
>
> The latest available version is 3.3.3
> https://download.postgresql.org/pub/repos/yum/15/redhat/rhel-7-x86_64/
>
> whereas for rhel8, all
yum.postgresql.org has already discontinued support for rhel-7 so I would
presume so.
From: Nikhil Shetty
Sent: Monday, February 26, 2024 6:27 AM
To: PostGIS Users Discussion
Subject: PostGIS 3.3 latest releases unavailable for rhel7
Hi Team,
I was not able to find the rpm
Which version of PostGIS are you coming from again?
In theory, as long as your old is running a newish PostGIS 3+, it should be
safe enough to just NOT run
SELECT postgis_extensions_upgrade();
If you don’t run that, then your database is just running with a newer lib
file, but old
11 matches
Mail list logo
