feat: bump orioledb to beta18 - #2473
Merged
Merged
Conversation
pgnickb
force-pushed
the
nickb/test_release
branch
from
September 23, 2026 09:08
6c295b2 to
dc1e455
Compare
PostgreSQL Extension Dependency Analysis: PR #2473
SummaryNo extensions had dependencies with MAJOR version updates. Full Analysis ResultsPostgreSQL 15 Extension DependenciesPostgreSQL 17 Extension DependenciesOrioleDB 17 Extension DependenciesExtension: pg_cron
Raw Dependency TreeExtension: wrappers
Raw Dependency Tree |
PostgreSQL Package Dependency Analysis: PR #2473
SummaryNo packages had MAJOR version updates. Full Analysis ResultsPostgreSQL 15 Dependency ChangesExtracting PostgreSQL 15 dependencies...
Runtime Closure Size
Raw Dependency ClosurePostgreSQL 17 Dependency ChangesExtracting PostgreSQL 17 dependencies...
Runtime Closure Size
Raw Dependency Closure |
za-arthur
force-pushed
the
nickb/test_release
branch
from
September 24, 2026 09:45
b58b452 to
d0885ce
Compare
za-arthur
changed the title
za-arthur
changed the title
Collaborator
|
You might want to rebase on top of #2155 |
Contributor
Collaborator
|
#2155 upgrades to 17.11 and as such already handles wal2json an similar stuff. That PR is putting in new code to skip tests/configs for orioledb because orioledb in tree is <17.11. Some of those things you are doing in this PR so imo it would make sense to rebase so you target that PR and can integrate into that setup of configs/tests/... instead of doing similar here. #2155 is almost ready to be merged so make sense for you to rebase on top of it now vs later. |
Contributor
But that PR upgrades only tests, it doesn't upgrade postgres to 17.11. |
Collaborator
|
ah sorry about that I'm pushing the commits individually so CI runs and I see the expected failures for the regression tests before the upgrade "magically" fixes them :D. I'll push the last 2 commits that end up with upgraded PG and then avoid doing this again. |
Collaborator
|
Note the last couple of comments I made in the PR |
Contributor
Hm, I think we didn't have failures of hstore tests in this PR. |
Contributor
|
I only had to add |
za-arthur
marked this pull request as ready for review
September 24, 2026 17:34
za-arthur
force-pushed
the
nickb/test_release
branch
2 times, most recently
from
September 24, 2026 19:16
370e75e to
edd43e0
Compare
- Bump orioledb to beta18 - Fix Postgres 17.11 backward compatibility by adding wal2json to output_plugin_libraries
pgnickb
force-pushed
the
nickb/test_release
branch
from
September 25, 2026 07:19
edd43e0 to
f297acb
Compare
brainrake
requested changes
Sep 25, 2026
brainrake
left a comment
brainrake
left a comment
Collaborator
There was a problem hiding this comment.
Please remove this everywhere:
# orioledb-17 is pinned to 17.11+, which added output_plugin_libraries as an
# allow-list for logical decoding output plugins
A more generic way to add output_plugin_libraries would be useful, rather than mutating a templated managed postgresql.conf in-place from different call sites.
Contributor
@brainrake there is a more generic PR which handles this #2155 |
brainrake
approved these changes
Sep 25, 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
4 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.
What kind of change does this PR introduce?
Bump orioledb to
beta18:https://github.com/orioledb/orioledb/releases/tag/beta18
What is the current behavior?
Currently orioledb is
beta16.What is the new behavior?
Additional context
https://github.com/orioledb/orioledb/releases/tag/beta18