-
-
Notifications
You must be signed in to change notification settings - Fork 176
chore: update upgrade scripts #533
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
…refactoring; fixes
|
||
echo "Re-enabling extensions" | ||
if [ -f $POST_UPGRADE_EXTENSION_SCRIPT ]; then | ||
run_sql -f $POST_UPGRADE_EXTENSION_SCRIPT |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
might be good to run these scripts through shellcheck -- it'd probably get mad about all the non-quoted variables
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good point! Added a shellcheck workflow to help keep the admin_api_scripts folder in check
|
||
# Make latest libpq available to pg_upgrade | ||
mkdir -p /usr/lib/postgresql/lib/aarch64 | ||
if [ ! -L /usr/lib/postgresql/lib/aarch64/libpq.so.5 ]; then |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
hmm do we block upgrades on the older x86 instances at some early stage?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not an explicit one - it's tied down to version eligibility since the last version supporting x86 was 12.5.
Will add additional checks in the admin cli and upcoming API support
What kind of change does this PR introduce?