#5189 closed defect (fixed)

upgrade failing from 3.2 to 3.3 - could not find function "gserialized_gist_sortsupport_2d"

Reported by: robe Owned by: robe
Priority: blocker Milestone: PostGIS 3.3.0
Component: QA/buildbots Version: master
Keywords: Cc:

Description

Looks like debbie's upgrades are failing going from PostGIS 3.2 to master (PG14) with this error:

https://debbie.postgis.net/job/PostGIS_Regress/21785/consoleFull

8:57:57 TMPDIR is /var/lib/jenkins/workspace/postgis/tmp/3_3_pg14w64
18:57:57 Creating database 'postgis_reg' 
18:57:57 Loading unpackaged components from /var/lib/jenkins/workspace/pg/rel/pg14w64/share/postgresql/contrib/postgis-3.2
18:57:57 Loading PostGIS into 'postgis_reg' 
18:57:57  failed (Error encountered loading /var/lib/jenkins/workspace/pg/rel/pg14w64/share/postgresql/contrib/postgis-3.2/postgis.sql: /var/lib/jenkins/workspace/postgis/tmp/3_3_pg14w64/regress_log)
18:57:57 psql:/var/lib/jenkins/workspace/pg/rel/pg14w64/share/postgresql/contrib/postgis-3.2/postgis.sql:564: ERROR:  could not find function "gserialized_gist_sortsupport_2d" in file "/var/lib/jenkins/workspace/pg/rel/pg14w64/lib/postgresql/postgis-3.so"
18:57:57 -----------------------------------------------------------------------------
18:57:57  failed (Error encountered loading /var/lib/jenkins/workspace/pg/rel/pg14w64/share/postgresql/contrib/postgis-3.2/postgis_comments.sql: /var/lib/jenkins/workspace/postgis/tmp/3_3_pg14w64/regress_log)

I suspect the postgis-3.so must be coming from 3.1, cause I had changed debbie to build —with-library-minor-version in master and it's quite possible she did a run of 3.1 branch after 3.2, so the upgrade script is all confused.

I'll take out the —with-library-minor-version. We probably should have one bot that builds without this switch and that does upgrades.

Change History (2)

comment:1 by robe, 22 months ago

Committed a fix at [5d53f3436/git]

I'll close this if that fixes the issue.

comment:2 by robe, 22 months ago

Resolution: fixed
Status: newclosed

okay that seemed to fix the issue.

Note: See TracTickets for help on using tickets.