Apply all 2.2 upgrades prior to running 2.3.0 upgrade If users are expected to run all of the 2.2 upgrade scripts, then let's make it easy for them. As PostgreSQL 9.1 does not include the \ir "include relative path" command, we have to pause at the beginning of the upgrade process to ensure that the user is running the script from the right directory. Signed-off-by: Dan Scott <dscott@laurentian.ca> Signed-off-by: Lebbeous Fogle-Weekley <lebbeous@esilibrary.com>
After upgrade, list records with missing or incorrect 901$c This is a common cause of pain for upgrades. Let's try to identify the problem early (even if it takes forever on a site with 3 million bibs) and offer advice on correcting the problem if it is flagged. Signed-off-by: Dan Scott <dscott@laurentian.ca> Signed-off-by: Lebbeous Fogle-Weekley <lebbeous@esilibrary.com>
Apply the 0715 update during the 2.3.0 upgrade Per LP# 1057183, the 0715 update should have been applied during the 2.1-2.2 upgrade, but appears not to have been - and that ends up causing problems during the 2.2-2.3 upgrade. Thus we prophylactically attempt to apply it again. Signed-off-by: Dan Scott <dscott@laurentian.ca> Signed-off-by: Lebbeous Fogle-Weekley <lebbeous@esilibrary.com>
Add an explicit "set eg_version" at start of upgrade script Thanks to Robert Soulliere for raising this issue in LP# 1057113! Signed-off-by: Dan Scott <dscott@laurentian.ca> Signed-off-by: Lebbeous Fogle-Weekley <lebbeous@esilibrary.com>
Add the 2.2-2.3.0 upgrade script Cloned from b9a480e7f640e7. Signed-off-by: Dan Scott <dscott@laurentian.ca> Signed-off-by: Lebbeous Fogle-Weekley <lebbeous@esilibrary.com>