feat: update orioledb to beta16#2232
Conversation
defdc4c to
01cb290
Compare
This comment was marked as outdated.
This comment was marked as outdated.
PostgreSQL Package Dependency Analysis: PR #2232
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 |
319626b to
a55b88e
Compare
a55b88e to
803cb97
Compare
0a70a4f to
5ca951c
Compare
|
added do not merge and convert to draft just until we can get tests run on this. then we can release asap |
5ca951c to
46315f1
Compare
13e8473 to
f0a0ee0
Compare
f0b9480 to
0e09b2a
Compare
|
Smoke tests pass except one: |
samrose
left a comment
There was a problem hiding this comment.
@za-arthur thank you for the diligence on this release.
74b707d to
a37413e
Compare
| find $out/share/postgresql/extension -name "*.sql" \ | ||
| -exec sed -Ei '/^CREATE TABLE\b/,/^\);$/ s/^\);$/) USING heap;/' {} + | ||
There was a problem hiding this comment.
can we upstream this instead?
There was a problem hiding this comment.
this applies to all db versions not only oriole, so pg_cron sql diverges from upstream. we shoud avoid this.
There was a problem hiding this comment.
the regex is fragile too, could break with upstream format change
There was a problem hiding this comment.
@brainrake this was actually leftover from #2242...
Thanks for noticing this!
I also created a PR to make a fix on pg_cron side: citusdata/pg_cron#435
|
nix changes look ok |
|
orioledb PG base is updated 17.6 → 17.9 |
a37413e to
49f18db
Compare
What kind of change does this PR introduce?
orioledbfrombeta14tobeta16https://github.com/orioledb/orioledb/releases/tag/beta16
Additional context
Add any other context or screenshots.
Action Items
Extensions compatibility testing
pg_net- execute HTTP requestspg_graphql- execute queries and mutationsBackup Testing
Follow the testing steps steps for all the following cases:
Testing steps
supa db-stats gather -p <project_ref>supa db-stats verifyagainst the project and the previously saved file