Closed Bug 813136 Opened 13 years ago Closed 13 years ago

Upgrade Socorro production to 9.2: test runs and troubleshooting

Categories

(Data & BI Services Team :: DB: MySQL, task)

Product:
Data & BI Services Team
Component:
DB: MySQL
Platform:
x86_64
Linux
Type:
task
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: selenamarie, Unassigned)

References

Details

We are ready to start testing a migration to 9.2. A crucial part of the testing is verification that our stored procedures all run properly in a 9.2 environment. This is difficult to verify without using a copy of production data. Can set up a copy of stage somewhere to run a migration and then a full set of our cronjobs/stored procedures? The database volume takes about 1.1 TB currently.
Depends on: 805996
And the target is week of Dec 4 for a 9.0-9.2 upgrade in production.
From IRC: :mpressman was able to get 9.2 onto our dev system to start testing this week.
We have devdb (the local instance of Postgres currently running on port 4321) going with 9.2! Issues that have been addressed include: * Needing to run the UPDATE portion of the 'create extension citext unpackaged' locally * Needing to drop and recreate all VIEWS containing citext columns so that collation is honored * Needing to update monitor config to honor non-standard port (patch pending) * Decided to allow in-place upgrade, preserving 9.0 & 9.2 directories for now -- this will get merged into one directory when we install the new drives and have to copy all the data anyway Time required for upgrade is about 2 minutes for pg_upgrade command, and another 3-4 minutes to run post-upgrade CITEXT-related scripts.
This is complete, and findings were incorporated into the checklist for the stage upgrade.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Product: mozilla.org → Data & BI Services Team
You need to log in before you can comment on or make changes to this bug.