Regression in PostGIS extension, and wrong documentation

PostgreSQL
1

The installation instructions on Use PostGIS extension - Percona Operator for PostgreSQL break on step 6, because that “image” URL doesn’t exist in deploy/cr.yaml. I think it’s been moved to deploy/operator.yaml, but even when I change it in there and “kubectl apply -f deploy/operator.yaml -n postgres-operator”, the pod fails with the error “/opt/crunchy/bin/uid_postgres.sh no such file or directory”.

Workaround: “git checkout v2.7.0” and then change the “image” value in deploy/cr.yaml to “docker.io/percona/percona-postgresql-operator:2.7.0-ppg17.5.2-postgres-gis3.3.8”. Then it installs and runs perfectly with those instructions.

It seems like there was both some PostGIS regression between v2.7.0 and v2.8.0 / v2.8.1, and that your instructions on that page are outdated.

2

Hi,

A fter the Operator is started, modify the deploy/cr.yaml configuration file with PostGIS-enabled image - use docker.io/percona/percona-postgresql-operator:2.8.1-ppg17.7-postgres-gis3.3.8 instead of docker.io/percona/percona-postgresql-operator:2.8.1-ppg17.7-postgres

Indeed there is an error in provided example. Not `docker.io/percona/percona-postgresql-operator:2.8.1-ppg17.7-postgres but `docker.io/percona/percona-distribution-postgresql:17.7-1` . I will create a task for our doc team to update example.

But I was able to start the cluster with gis image ‘percona/percona-postgresql-operator:2.8.1-ppg17.7-postgres-gis3.3.8‘ image without issues. Can you provide more details steps to reproduce and/or your cr?

Also, are you using v2.8.1 tag and or main branch? Because in main branch the postgresVersion is set to 18 and this indeed may lead to issues.

3

Hi,

Please also note the note from PGO 2.8.1 operator release re PostgreSQL RPMs rebuilt to disable debug assertions Percona Operator for PostgreSQL 2.8.1 (2025-12-16) - Percona Operator for PostgreSQL . We are planning to release 2.8.2 in soon to fix this.

4

When I completely reset my whole Kubernetes environment, and re-ran the installation instructions from that page with this change as your proposed:

diff --git a/deploy/cr.yaml b/deploy/cr.yaml
index ab2e5baf8..54d0563ec 100644
--- a/deploy/cr.yaml
+++ b/deploy/cr.yaml
@@ -154,7 +154,7 @@ spec:
 #          test-label: value


-  image: docker.io/percona/percona-distribution-postgresql:17.7-1
+  image: docker.io/percona/percona-postgresql-operator:2.8.1-ppg17.7-postgres-gis3.3.8
   imagePullPolicy: Always
   postgresVersion: 17
 #  port: 5432

then it started working.

So it looks like just a documentation issue.

Thank you so much :grinning_face:.

1 Like
5

Hi @SelectStar ,

Thanks reaching back with update! Glad to hear it worked. JFYI: the task for updating docs Jira .