feat: bump oriole to latest#2028
Merged
Merged
Conversation
pgnickb
reviewed
Feb 3, 2026
5c83642 to
08e2c59
Compare
Collaborator
Author
|
next steps:
|
27b48ae to
bafcee8
Compare
This comment has been minimized.
This comment has been minimized.
8c674fe to
75b1041
Compare
to fix a bug with OrioleDB treating CREATE MATERIALIZED VIEW ... AS SELECT as if it were WITH NO DATA
9441aae to
48b2a55
Compare
Collaborator
Author
|
This PR has been tested in supadev for smoke tests, etc. it includes the oriole specific vm tests above as well, which will run any time a change is made to oriole inputs, and can be run locally |
hunleyd
approved these changes
Feb 20, 2026
encima
pushed a commit
that referenced
this pull request
Feb 23, 2026
* feat: bump oriole to latest * fix: update func interface inclusion on oriole * tests: rewind regres test * chore: bump version * oriole regres fix * fix: rm rewind tests * feat: use beta14 and 17_16 patchset * fix: update oriole to 00043a2881d0d2a3dfe7914e2a67694889c686b5 to fix a bug with OrioleDB treating CREATE MATERIALIZED VIEW ... AS SELECT as if it were WITH NO DATA * feat: using main commit * feat: bump to test * feat: rewind off by default * tests: passing rewind oriole teest * feat: release orioledb under rev 982e11ae62c9e00c0d74f9f8de31d99ff383fd02
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.
bumping to latest using our git commit sha capability, to get the latest features and fixes available now.
Adding a test
The test starts a Linux aarch64-linux VM with orioledb and the full Supabase initialization stack. Once that's ready, it switches to the OrioleDB 17 specialisation with rewind enabled (1280 main
buffers, 1200s max time, 100K max transactions).
Subtest 1 verifies the switch worked. It confirms the orioledb extension is installed, queries pg_settings to print all rewind-related config, asserts that orioledb.enable_rewind is on,
and prints the initial rewind queue and evicted lengths.
Subtest 2 does a basic rewind matching the bash script. It creates a table with 100 rows, captures the xid, oxid, and md5 hash in one query, then inserts 40 more rows to dirty the state.
It calls orioledb_rewind_to_transaction(xid, oxid) which crashes postgres. Systemd Restart=always brings it back. After restart it verifies the row count is back to 100 and the hash
matches the pre-rewind snapshot.
Subtest 3 does a rewind under buffer pressure. It creates a new table and inserts 5000 rows across 50 separate transactions, captures a checkpoint, then inserts 1000 more rows in 10
batches. It prints the rewind queue and evicted lengths to show the buffer state, then rewinds to the checkpoint. After restart it verifies the row count matches the checkpoint count
(5000).