Change pgWAL AutoGrow events to warnings#4292
Merged
jmckulk merged 2 commits intoCrunchyData:mainfrom Sep 17, 2025
Merged
Conversation
WAL volumes growing could indicate an issue with backups that needs to be addressed. This event should be presented to users as a warning.
Unsetting PATH could lead to issues in some environments (nix) where tools (mktemp) aren't in a standard location. Keep path to avoid issues
64bf088 to
f253d4b
Compare
tjmoore4
approved these changes
Sep 17, 2025
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
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.
Checklist:
Type of Changes:
What is the current behavior (link to any open issues here)?
Some AutoGrow events for pgWAL volumes are displayed to the user as "Normal".
What is the new behavior (if this is a feature change)?
Any AutoGrow events related to pgWAL are now warnings to the user.
Other Information:
Growth of the pgWAL volume could be a symptom of an issue with cluster backups. Instead of treating this as a normal event we want to warn users that this could potentially be a problem.