docs: PostgreSQL User for Schema Upgrades #991
Merged
Conversation
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
Explicitly state that the "icingadb" PostgreSQL database user must be used for schema upgrades. The PostgreSQL database user applying a schema upgrade is the table owner of newly create tables. When applying an Icinga DB schema upgrade not as the "icingadb" user, but as "postgres", newly created tables would not be accessible for the "icingadb" user, resulting in Icinga DB and Icinga DB Web to fail. Reported in #987.
Al2Klimov
approved these changes
Jul 3, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Explicitly state that the "icingadb" PostgreSQL database user must be used for schema upgrades.
The PostgreSQL database user applying a schema upgrade is the table owner of newly create tables. When applying an Icinga DB schema upgrade not as the "icingadb" user, but as "postgres", newly created tables would not be accessible for the "icingadb" user, resulting in Icinga DB and Icinga DB Web to fail.
Reported in #987.
Screenshot of rendered docs