Hi Regina, Devirim,
Thank you for the details. We will try to uninstall the old version and
then install the new version.
Thanks,
Nikhil
On Wed, Feb 21, 2024 at 3:51 PM Devrim Gündüz wrote:
> Hi,
>
> On Tue, 2024-02-20 at 22:37 +0530, Nikhil Shetty wrote:
> > I upgraded the existing PostGIS
Hi,
On Tue, 2024-02-20 at 22:37 +0530, Nikhil Shetty wrote:
> I upgraded the existing PostGIS 3.1.2 to 3.3.5 on PG13 but now when I
> am trying to install PostGIS 3.3.5 for PG15 , I am getting below error
>
> Error: Transaction test error:
>
> file
: Tuesday, February 20, 2024 11:33 PM
To: Regina Obe
Cc: PostGIS Users Discussion
Subject: Re: GDAL dependencies during PostGIS upgrade
Hi,
I tired installing the single package but still the same error
yum install -y postgis33_15-client-3.3.5-1PGDG.rhel8.x86_64.rpm
Last metadata
gt;
> But instead just
>
>
>
> yum install -y postgis_33_15
>
>
>
> I’m guessing whatever that client is, they probably get installed in the
> same place, so you only need one of them.
>
>
>
> Alternatively just remove the postgis_33_13_client
>
>
>
, so you only need one of them.
Alternatively just remove the postgis_33_13_client
From: Nikhil Shetty
Sent: Tuesday, February 20, 2024 12:07 PM
To: Regina Obe
Cc: PostGIS Users Discussion
Subject: Re: GDAL dependencies during PostGIS upgrade
Hi Regina,
I upgraded the existing
Hi Regina,
I upgraded the existing PostGIS 3.1.2 to 3.3.5 on PG13 but now when I am
trying to install PostGIS 3.3.5 for PG15 , I am getting below error
Error: Transaction test error:
file /usr/lib/.build-id/b6/89201f4430759c8544cd168dc6ba3e24f7d912 from
install of
Hi Regina,
We are upgrading from PG 13 3.1.2 to PG 15 3.3.5
I forget if pg_upgrade checks the old .so to see if it can still load it or
> if it only checks if the new .so it is expecting in the new cluster is
> still available.
pg_upgrade is checking in the PG13 lib whether the .so file
Nikhil,
Which version of PostgreSQL are you upgrading from.
I forget if pg_upgrade checks the old .so to see if it can still load it or if
it only checks if the new .so it is expecting in the new cluster is still
available.
If it doesn’t check the old to try to load the lib, dropping
