We’ve been seeing a number of issues with the upgrade scripts for this release reported here on the blog, in IRC, as well as the ticket tracker. We’ve got a couple bits of news for those upgrading from codebases older than mid-August and those using versions of PostgreSQL older than 9.0:
- MBS-5473: This is the
ERROR: function controlled_for_whitespace(character varying) does not existmigration problem. Slaves with imports done before mid-August are missing a few stored procedures that are necessary for the upgrade. This has been fixed in the master branch as of commit 082e608c074641e2e8df2c0809d35421b02c7899 — to run the upgrade, run
git fetch origin, then
git checkout 082e608c074641e2e8df2c0809d35421b02c7899, then continue with step #6 of the original instructions. If you already started the upgrade but failed on the ‘merge-duplicate-credits’ script (as is likely, with this bug), don’t worry: at that point in the upgrade, restarting is not an issue.
- MBS-5475: This is the
ERROR: syntax error at or near “ORDER”migration problem. Unfortunately, this one’s more serious: on PostgreSQL 8.4, our upgrade scripts don’t work, as one uses a feature introduced in 9.0 (as previously mentioned) After some hours of investigation, it appears that this issue can’t be resolved reasonably; therefore, for 8.4 users the upgrade path is a data re-import using a recent (post-schema-change) codebase and a data dump from October 17th or later. We’d also recommend updating to PostgreSQL 9.x at the same time if that is possible.
Sorry again for the inconvenience.