2.1-2.2 upgrade script safety checks

Bug #996089 reported by James Fournie
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Evergreen
Fix Released
High
Unassigned

Bug Description

OS: Ubuntu Lucid
DB: PG 9.1
EG: rel_2_2

Upgrade script contains this:

ALTER TABLE config.upgrade_log DROP COLUMN applied_to;
DROP FUNCTION evergreen.upgrade_list_applied_deprecates(TEXT);
DROP FUNCTION evergreen.upgrade_list_applied_supersedes(TEXT);

This produced errors on our upgrade. Instead I propose:

ALTER TABLE config.upgrade_log DROP COLUMN IF EXISTS applied_to;
DROP FUNCTION IF EXISTS evergreen.upgrade_list_applied_deprecates(TEXT);
DROP FUNCTION IF EXISTS evergreen.upgrade_list_applied_supersedes(TEXT);

Tags: pullrequest
Revision history for this message
James Fournie (jfournie) wrote :

Pushed a patch to working/user/jamesrf/lp996089

Changed in evergreen:
importance: Undecided → Medium
milestone: none → 2.2.0rc1
tags: added: pullrequest
Changed in evergreen:
importance: Medium → High
assignee: nobody → Lebbeous Fogle-Weekley (lebbeous)
status: New → In Progress
Revision history for this message
Lebbeous Fogle-Weekley (lebbeous) wrote :

In master and rel_2_2. Thanks again James!

Changed in evergreen:
assignee: Lebbeous Fogle-Weekley (lebbeous) → nobody
status: In Progress → Fix Committed
Changed in evergreen:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.