chore(deps): update dependency postgresql-18-pg-ivm - #334
Merged
Conversation
Signed-off-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
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.
This PR contains the following updates:
1.13→1.151.13-1.pgdg12+1→1.15-1.pgdg12+11.13-1.pgdg13+1→1.15-1.pgdg13+1Release Notes
sraoss/pg_ivm (postgresql-18-pg-ivm)
v1.15: pg_ivm 1.15 (2026-06-30)What's Changed
New features
Add IMMV metadata restore support for pg_dump and pg_upgrade by @yugo-n in #169
After restoring a database from pg_dump or upgrading PostgreSQL using pg_upgrade, IMMVs no longer need to be dropped and recreated manually. The new pg_ivm_dump_metadata utility and restore_immv() function restore the metadata required by pg_ivm, allowing incremental maintenance to continue without recreating the IMMVs.
Bug fixes
Fix incorrect maintenance when the same table is modified multiple times by triggers by @yugo-n in #162
Previously, if a table was modified multiple times by user-defined or RI triggers, incremental maintenance could produce inconsistent results or lead to duplicate key violations.
Fix segfault during outer-join views maintenance by @yugo-n in #167
This bug was introduced in v1.14.
Full Changelog: sraoss/pg_ivm@v1.14...v1.15
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.