Hi Team,
Is there a way to confirm if raster is being used by the application team?
PostGIS version - 2.5.4
>From PostGIS version 3.0, we have to create an extension so we can know
that the raster functions may be used by the application team.
Thanks,
Nikhil
upgrade();
>
> SELECT postgis_extensions_update();
>
>
>
> -- if not using raster, you can do this
>
> DROP EXTENSION postgis_raster;
>
>
>
>
>
> #after you are done upgrading your dbs, you can drop the symlinks e.g.
>
> rm /usr/pgsql-11/lib/rtpostgis-
Hi Team,
I am looking for a faster way to upgrade postgis on postgresql 11 from
2.5.4 to 3.1.2.
I am getting below error when doing though yum
Transaction check error:
> file /usr/pgsql-11/share/extension/address_standardizer.control from
> install of postgis31_11-3.1.2-1.rhel7.x86_64
hings 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
> *Sent:* Tue
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
se 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:
e 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 les
On Fri, 25 Aug 2023 at 15:47, Greg Troxel wrote:
> Nikhil Shetty writes:
>
> > 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
>
&
), 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
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 wrote:
>
> Hi Regina,
>
> We do have plans to upgrade both Postgres and PostGIS to higher versions
>
upgrades.
Thanks,
Nikhil
On Fri, Apr 14, 2023 at 5:08 PM Sandro Santilli wrote:
> On Fri, Apr 14, 2023 at 01:29:02PM +0530, Nikhil Shetty wrote:
>
> > geo=# alter extension postgis update to '3.1.2';
> > ERROR: could not access file "$libdir/postgis-2.5":
on these dropped objects?
Thanks,
Nikhil
On Mon, Apr 17, 2023 at 2:54 PM Nikhil Shetty
wrote:
> Hi Sandro,
>
> Thank you, I will try the workaround
>
> BUT I'm wondering: why would you want to upgrade to 3.1.2 when the
> latest PostGIS version in the 3.1 branch is 3.1.8
Sure Sandro,
We will try upgrading to 3.1.5
Thanks,
Nikhil
On Mon, 17 Apr 2023 at 20:39, Sandro Santilli wrote:
> On Mon, Apr 17, 2023 at 04:56:06PM +0200, Sandro Santilli wrote:
> > On Mon, Apr 17, 2023 at 03:18:50PM +0530, Nikhil Shetty wrote:
> >
> > > DET
Hi Team,
We are running on PostgreSQL v10.12 and we are in the process to upgrade it
to v13. We are using PostGIS v2.5.4 on v10.12.
We want to upgrade PostGIS as well to 3.1.2. We plan to follow below
approach
1. Upgrade PostGIS from 2.5.4 to 3.1.2 on PostgreSQL 10.12
2. Upgrade PostgreSQL
18, 2023 at 12:14:55AM +0530, Nikhil Shetty wrote:
>
> > We will try upgrading to 3.1.5
>
> I'd go to 3.1.8 which came out on 2022/11/12
> All these patch-level releases really ONLY contain bug fixes,
> no new features, no new bugs.
>
> If you upgrade to 3.1.5 you'l
Hi Team,
We are planning to upgrade postgres to 15 and postgis from 3.1.2 to 3.3.5.
While installing postgis 3.3.5 we found some dependency issues with gdal36,
we were able to workaround by removing postgis 3.1.2 and gdal32 packages
but for postgres upgrade we need both postgis (3.1.2 and 3.3.5)
ewer PostGIS on your older
> cluster, doesn’t need to be the same, just one where the gdals are
> compatible.
>
>
>
> *From:* Nikhil Shetty
> *Sent:* Thursday, February 15, 2024 11:37 PM
> *To:* PostGIS Users Discussion
> *Subject:* GDAL dependencies during PostGIS upg
of postgis33_15-client-3.3.5-1PGDG.rhel8.x86_64 conflicts with file
> from package postgis33_13-client-3.3.5-1PGDG.rhel8.x86_64
Thanks,
Nikhil
On Fri, Feb 16, 2024 at 11:16 AM Nikhil Shetty
wrote:
> Hi Regina,
>
> We are upgrading from PG 13 3.1.2 to PG 15 3.3.5
>
> I forget if
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 e
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
>
>
>
Hi Team,
I am getting below error when installing gdal 3.5.3
yum install gdal35-libs-3.5.3-7PGDG.rhel8.x86_64.rpm
> Last metadata expiration check: 0:00:02 ago on Tue 12 Mar 2024 07:00:40 AM
> UTC.
> Error:
> Problem: conflicting requests
> - nothing provides libarmadillo.so.10()(64bit)
, 2024-03-12 at 12:46 +0530, Nikhil Shetty wrote:
> > yum install postgis33_15-3.3.3-1.rhel8.x86_64.rpm
>
> The latest version is 3.3.6, not 3.3.3, so please use that one.
>
> Regards,
> --
> Devrim Gündüz
> Open Source Solution Architect, PostgreSQL Major
As I see from the fedora repository, armadillo v10 is only available in
Linux v7 > https://dl.fedoraproject.org/pub/epel/7/x86_64/Packages/a/
For Linux v8, armadillo version is 12.
On Tue, Mar 12, 2024 at 2:34 PM Nikhil Shetty
wrote:
> I installed armadillo package and
skip uninstallable packages or '--nobest'
> to use not only best candidate packages)
gdal is looking for armadillo v10 but our repo is configured with v12.
Thanks,
Nikhil
On Tue, Mar 12, 2024 at 12:56 PM Nikhil Shetty
wrote:
> We have enabled epel repo as well.
>
We have enabled epel repo as well.
yum repolist | grep epel
> *epel**epel*
On Tue, Mar 12, 2024 at 12:46 PM Nikhil Shetty
wrote:
> Hi Team,
>
> I am getting below error when installing gdal 3.5.3
>
> yum install gdal35-libs-3.5.3-7PGD
you using postgis_raster or you just have it installed?
>
>
>
> If you don’t need postgis_raster, I would suggest uninstalling it before
> upgrading.
>
>
>
> *From:* Nikhil Shetty
> *Sent:* Saturday, March 16, 2024 10:55 AM
> *To:* PostGIS Users Discussion
> *Subject:
fix should already be in the PG15 3.3.5 except for the parts
> that have PG16 guards, cause they wouldn’t work in PG15 or lower.
>
> So If you find trying to reapply to 3.3.5 works I’d be surprised and be
> interested in which portion of patch you applied.
>
>
>
>
>
>
&
Hi Team,
I am trying to upgrade the postgres database from PG13 to PG15. pg_upgrade
is crashing with below error when creating the raster_in function
pg_restore: creating FUNCTION "public.raster_in("cstring")"
> pg_restore: while PROCESSING TOC:
> pg_restore: from TOC entry 394; 1255 16439
>
>
> All I know is if you run
>
>
>
> SELECT postgis_full_version();
>
>
>
> And you get an error after upgrading your binaries, then not running
> postgis_extensions_ugprade is not an option.
>
>
>
> *From:* Nikhil Shetty
> *Sent:* Monday, Februar
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
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
32 matches
Mail list logo
