Skip to content
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

WIP. Initial code to automatically upgrade PG database extensions #53

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

justinclift
Copy link
Member

This is initial concept code (completely untested) for automatically upgrading the extensions in the database cluster.

It needs to be tested to make sure it works at all 😁, and we'll need to add some kind of proper testing as part of our CI as well.

@justinclift justinclift force-pushed the automatic_extension_upgrade_v1 branch from 1b9cfc8 to d844878 Compare October 10, 2024 09:11
@justinclift
Copy link
Member Author

Stumbled over something interesting today while looking at PostGIS properly for the first time (about to test it for a new project).

When upgrading PostGIS, the command to upgrade the PostGIS extensions can need to be run twice. I think it's something along the lines of the first one doing the main PostGIS extension itself, then the follow up one upgrades some optional PostGIS extensions that depend upon the first one:

https://www.cybertec-postgresql.com/en/upgrade-postgresql-postgis-together/#use-postgis-extensions-upgrade-to-finish-the-task

Looks like we'd optimally have some kind of detection for PostGIS needing to be upgraded, then handling it properly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant