Skip to content

feat: bump oriole to latest#2028

Merged
samrose merged 13 commits into
developfrom
sam/oriole-latest
Feb 20, 2026
Merged

feat: bump oriole to latest#2028
samrose merged 13 commits into
developfrom
sam/oriole-latest

Conversation

@samrose
Copy link
Copy Markdown
Collaborator

@samrose samrose commented Jan 30, 2026

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).

Comment thread nix/tests/expected/z_orioledb-17_rewind.out Outdated
Comment thread nix/tests/sql/z_orioledb-17_rewind.sql Outdated
@samrose
Copy link
Copy Markdown
Collaborator Author

samrose commented Feb 7, 2026

next steps:

  • build image to test
  • test rewind in local infra
  • remove regress test for rewind

@samrose samrose force-pushed the sam/oriole-latest branch 3 times, most recently from 27b48ae to bafcee8 Compare February 12, 2026 14:58
@blacksmith-sh

This comment has been minimized.

@samrose samrose force-pushed the sam/oriole-latest branch 3 times, most recently from 8c674fe to 75b1041 Compare February 19, 2026 16:56
@samrose samrose marked this pull request as ready for review February 20, 2026 03:45
@samrose samrose requested review from a team as code owners February 20, 2026 03:45
@samrose
Copy link
Copy Markdown
Collaborator Author

samrose commented Feb 20, 2026

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

@samrose samrose added this pull request to the merge queue Feb 20, 2026
Merged via the queue into develop with commit 550d9fd Feb 20, 2026
42 checks passed
@samrose samrose deleted the sam/oriole-latest branch February 20, 2026 19:52
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
hunleyd added a commit that referenced this pull request Feb 25, 2026
* 'develop' of github.com:supabase/postgres:
  feat: bump PostgREST to 14.5 (#2057)
  feat: bump oriole to latest (#2028)
  fix: bump AMI version (#2059)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants