Update Postgres PostGIS Proj extension to 8/9 [239824756]

Assigned

Bug

Status Update

No update yet.

Description

de...@kartverket.no

created issue #1

Jul 22, 2022 12:39PM

Problem you have encountered:

Currently when running postgis_full_version(); on a Postgres Cloud SQL instance it gives this response:

POSTGIS="3.1.4 3.1.4" [EXTENSION] PGSQL="140" GEOS="3.5.0-CAPI-1.9.0 4392" SFCGAL="1.3.8" PROJ="Rel. 6.0.0, March 1st, 2019" LIBXML="2.9.10" LIBJSON="0.15" LIBPROTOBUF="1.4.0" TOPOLOGY

What you expected to happen:

Proj is the projection library of PostGIS. 6.0 was released in 2019 and is overdue for an update. We have several teams who are eager to use Cloud SQL but require at least Proj 8 to be able to store their data there.

Steps to reproduce:

Set up a new Postgres Cloud SQL instance
Install the PostGIS extension by running CREATE EXTENSION postgis;
Run postgis_full_version(); and look for the PROJ version

Other information (workarounds you have tried, documentation consulted, etc):

Comments

sa...@google.com <sa...@google.com> #2Aug 3, 2022 01:42PM

Assigned to sa...@google.com.

Hello,

Thank you for reporting the issue.

I think Porj version 8.1-8.2 will support PostGIS 3.1 and above. Check this Versions of Proj support for PostGIS here.

jv...@google.com <jv...@google.com> #3Aug 4, 2022 10:40AM

Comment has been deleted.

Message last modified on Aug 4, 2022 09:02PM

[Deleted User] <[Deleted User]> #4Aug 8, 2022 06:54AM

I think Porj version 8.1-8.2 will support PostGIS 3.1 and above. Check this Versions of Proj support for PostGIS here.

Hi! Yes that is true, but it's not included with any Postgres versions currently available. Not sure if you want me to try and install it, as I'm not sure how I would do that with Cloud SQL. Feel free to pass me any actionable fixes you come up with and I'll verify them as fast as I can.

sa...@google.com <sa...@google.com> #5Aug 8, 2022 07:10AM

Reassigned to gc...@google.com.

This has been forwarded to the Engineering Team so that they may evaluate it. Note that there are no ETAs for this. All communication regarding this has to be done here.

IssueTracker