- Notifications
You must be signed in to change notification settings - Fork58
PermalinkChoose a base ref {{ refName }}default Choose a head ref {{ refName }}default
Comparing changes
Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also orlearn more about diff comparisons.
Open a pull request
Create a new pull request by comparing changes across two branches. If you need to, you can also.Learn more about diff comparisons here.
base repository:postgrespro/rum
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
Uh oh!
There was an error while loading.Please reload this page.
base:66c26a9
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}defaultLoading
...
head repository:postgrespro/rum
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
Uh oh!
There was an error while loading.Please reload this page.
compare:9bf66af
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}defaultLoading
- 4commits
- 7files changed
- 1contributor
Commits on Feb 11, 2025
PGPRO-12044; PGPRO-11987: Temporary disable some rum tests.
To be solved in PGPRO-11987. Tags: rum
PGPRO-12044; Fix tests int8, altorder and altorder_hash for 32-bit pl…
…atforms. Caused by: - c01743aa4866e13da2c54e44010abc6d5f986363 (PostgreSQL) Show number of disabled nodes in EXPLAIN ANALYZE output. Tags: rum
Commits on Feb 20, 2025
PGPRO-12044: Add output variant for PG18 for contrib/rum/sql/security…
….sql test. Caused by: - 774171c4f640853b1cf8747a4762631d2f5d25be (PostgreSQL) Improve reporting of errors in extension script files. Tags: rum
Commits on Feb 24, 2025
PGPRO-12044: Fix output variants for 32-bit tests .
Caused by: - 161320b4b960ee4fe918959be6529ae9b106ea5a (PostgreSQL) Adjust EXPLAIN's output for disabled nodes Tags: rum
Loading
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:git diff 66c26a9...9bf66af
Uh oh!
There was an error while loading.Please reload this page.