docs: add PostgreSQL v16 to v18 migration guide for v7.0.0#51
Merged
mlodic merged 2 commits intointelowlproject:mainfrom Feb 9, 2026
Merged
docs: add PostgreSQL v16 to v18 migration guide for v7.0.0#51mlodic merged 2 commits intointelowlproject:mainfrom
mlodic merged 2 commits intointelowlproject:mainfrom
Conversation
This was referenced Feb 7, 2026
mlodic
requested changes
Feb 8, 2026
| docker container rm intelowl_postgres_16 | ||
| ``` | ||
| 7. (Optional) Remove the old PostgreSQL volume: | ||
| ```bash |
Member
There was a problem hiding this comment.
note here what would the consequence (removing the backup)
Member
There was a problem hiding this comment.
also, this is better to put at the end, after having checked everything works properly
Contributor
Author
There was a problem hiding this comment.
- Added a explicit warning about the consequence of removing the old volume (permanent deletion of the backup).
- Reordered the steps to move the old volume removal to the very end of the process.
| Below you can find the additional process required to upgrade from each major versions. | ||
| </div> | ||
|
|
||
| #### Updating to >=7.0.0 from a 6.x.x version |
Member
There was a problem hiding this comment.
please add note that the 7.0.0 version does not exist yet, we will remove it later
Contributor
Author
There was a problem hiding this comment.
Added a note clarifying that v7.0.0 is not yet officially released.
Contributor
Author
|
Hi @mlodic, I've updated the documentation guide to address your feedback:
|
mlodic
approved these changes
Feb 9, 2026
27 tasks
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.
Add PostgreSQL v16 to v18 migration guide for v7.0.0. Closes intelowlproject/IntelOwl#3272
Description
This PR adds a comprehensive 12-step migration guide for users upgrading from IntelOwl v6.x.x (PostgreSQL 16) to v7.0.0 (PostgreSQL 18).
The guide walks users through:
postgres_data_v18volume.Related IntelOwl PR: intelowlproject/IntelOwl#3292
Checklist
main_Available from version > 6.0.0_(This documentation is for v7.0.0)mainbranch and do not open this PR. (This is a new migration guide, so a PR is appropriate).