upgrade-postgres: clarify data cleanup link - #2215
Merged
alxndrsn merged 2 commits intoSep 17, 2026
Merged
Conversation
In the original implementation (getodk#343), old postgres data was cleaned up automatically if a specific flag file was present. This behaviour was changed (prior to release?) in a follow-up PR (getodk#395) to link to documentation instead. Over time, it's become less clear which part of the linked documentation is relevant. This PR aims to link more directly to the relevant documentation.
alxndrsn
commented
Sep 7, 2026
alxndrsn
marked this pull request as ready for review
September 7, 2026 10:21
lognaturel
approved these changes
Sep 15, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
In the original implementation (#343), old postgres data was cleaned up automatically if a specific flag file was present.
This behaviour was changed (prior to release?) in a follow-up PR (#395) to link to documentation instead.
Over time, it's become less clear which part of the linked documentation is relevant. This PR aims to link more directly to the relevant documentation.
What has been done to verify that this works as intended?
Why is this the best possible solution? Were any other approaches considered?
It took me a while to understand which part of the original link (https://docs.getodk.org/central-upgrade/) was relevant to upgrading postgres. The new link is https://docs.getodk.org/central-upgrade/#upgrading-to-central-v2023-2
How does this change impact users? Describe intentional behavior changes from code updates. What are the regression risks?
Hopefully gets them where they need to be quicker. Low risk of regression.
Does this change require updates to documentation? If so, please file an issue here and include the link below.
No.