- Notifications
You must be signed in to change notification settings - Fork15
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/pgsphere
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:1.5.1
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}defaultLoading
...
head repository:postgrespro/pgsphere
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:master
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}defaultLoading
- 12commits
- 19files changed
- 3contributors
Commits on May 27, 2024
Re-generate parser source files
vitcpp committedMay 27, 2024 Add TOK_ prefix to INT, FLOAT, SIGN token names to distinguist thesenames from macro directives under mingw64.
vitcpp committedMay 27, 2024
Commits on Jun 10, 2024
Now more carefully nulling out null inputs in epoch_prop.
This is so we do not invent values for pm, parallax, or rv. Weare actually a bit over-cautious and invalidate both PMs even ifonly one is missing. This is because PMs mix, and hence there are tracesof the invented 0 in the other component of the PM. Similarly,when the parallax is missing or bad, the RV would be heavily contaminated;in these cases, we copy through the original RV, as it may still be usefuland certainly will not be grossly wrong.(sorry about a few whitespace diffs introduced by killing trailing whitespacein sql/epochprop.sql and src/epochprop.c)
Issue#125: Add PostgreSQL 17 builds to CI workflow
This merge request addresses issue#125 by updating the GitHub Actions CI workflow to build and test on PostrgeSQL 17.
Commits on Oct 16, 2024
Update actions/upload-artifact version in CI workflow
This PR updates the version number on `actions/upload-artifact` in `.github/workflows/build-and-check.yml` in order to silence the following warning:> The following actions use a deprecated Node.js version and will be forced to run on node20: actions/upload-artifact@v3. For more info:https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/https://github.com/actions/upload-artifact says:> actions/upload-artifact@v3 is scheduled for deprecation on November 30, 2024. [Learn more.](https://github.blog/changelog/2024-04-16-deprecation-notice-v3-of-the-artifact-actions/) Similarly, v1/v2 are scheduled for deprecation on June 30, 2024. Please update your workflow to use v4 of the artifact actions. This deprecation will not impact any existing versions of GitHub Enterprise Server being used by customers.
Commits on Nov 11, 2024
Build and check workflow for MS Windows
vitcpp committedNov 11, 2024 - vitcpp committed
Nov 11, 2024 Add crushtest in build-and-check-windows-latest workflow
vitcpp committedNov 11, 2024 - vitcpp committed
Nov 11, 2024
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 1.5.1...master
Uh oh!
There was an error while loading.Please reload this page.