Maintain Control Numbers function should be schema-qualified

Bug #1714026 reported by Chris Sharp on 2017-08-30
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Evergreen
High
Unassigned

Bug Description

Currently, the maintain_control_numbers function is not schema-qualified, which makes it land in the public schema by default. For upgraded installations where there may be an evergreen.maintain_control_numbers function, this results in a situation where the older wrong function is in the search_path before the correct one (default search_path is "$user", public).

Branch on the way.

Evergreen 2.12.4
OpenSRF 2.5.0
Postgresql 9.4
Ubuntu 14.04 LTS

Galen Charlton (gmc) on 2017-09-21
Changed in evergreen:
milestone: none → 3.0-rc
importance: Undecided → High
status: New → Confirmed
Bob Wicksall (bwicksall) wrote :

I ran into this upgrading from 2.10.4 to 3.0 beta1. In the middle of 2.12.5-3.0-beta1-upgrade-db.sql I was getting the following error:

psql:version-upgrade/2.12.5-3.0-beta1-upgrade-db.sql:2537: ERROR: Cannot decode string with wide characters at /usr/lib/x86_64-linux-gnu/perl/5.20/Encode.pm line 217.
CONTEXT: PL/Perl function "maintain_control_numbers"
psql:version-upgrade/2.12.5-3.0-beta1-upgrade-db.sql:2539: ERROR: current transaction is aborted, commands ignored until end of transaction block

I applied Chris Sharp's patch. I still have bad data but I'm getting more meaningful errors and warnings.

I also confirmed that the duplicate maintain_control_numbers function exists in our 2.10 instance.

Galen Charlton (gmc) on 2017-09-26
tags: added: pullrequest
Galen Charlton (gmc) wrote :

Pushed to master for inclusion in 3.0-rc. Thanks, Chris!

Changed in evergreen:
status: Confirmed → Fix Committed
Changed in evergreen:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers