Sam/sync versions #925
Merged
Sam/sync versions #925
Conversation
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
…wrappers includes experimental integration of orioledb and patched psql 16 for orioledb
Closed
9be266f to
2fe314d
Compare
olirice
approved these changes
Apr 1, 2024
run the sync util on the nix expressions, and then build and test against those versions as synced from ansible/vars.yml paring down to psql 15.6 + extensions/wrappers (put aside oriole and psql 16 for now, will bring back when ready)
olirice
approved these changes
Apr 1, 2024
soedirgo
approved these changes
Apr 2, 2024
darora
approved these changes
Apr 3, 2024
damonrand
pushed a commit
to cepro/postgres
that referenced
this pull request
Jun 15, 2025
* feat: integrating a parallel nix-based build of supabase psql, exts, wrappers includes experimental integration of orioledb and patched psql 16 for orioledb * docs: updating docs to correspond with new location * feat: clearing out commented out citus references in the nix implementation * chore: fmt * chore: update maintainer gh username * feat: update pgvector to 0.6.0 * feat: include nix specific ci (may require env vars configured in repo settings) * fix: deprecate justfile * feat: wip update versions from ansible vars data * chore: stashing progress * feat: WIP tooling that will update versions, source and cargovendor sha * feat: more work toward versions sync * fix: gh action targets * fix: conform name * feat: bring all exts into local/native build (no more upstream) run the sync util on the nix expressions, and then build and test against those versions as synced from ansible/vars.yml paring down to psql 15.6 + extensions/wrappers (put aside oriole and psql 16 for now, will bring back when ready)
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.
What kind of change does this PR introduce?
This PR introduces a
/nixfolder in this repo, plus aflake.nixandflake.lockthat facilitate using the Nix package management system to package supabase/postgres, and all of our extensions and wrappers. A user will need nix installed on their machine. As of 4/1/2024 the package set only builds on target machines (x86_64-linuxandaarch64-linux), however work is under way to also support building and using directly onaarch64-darwin(macOs). As of 4/1/2024, versions of packages and extensions are synced from/ansible/vars.ymlvia a utility that can be run by executingnix run .#sync-exts-versions(you must have nix installed and be on the supportedx86_64-linuxandaarch64-linuxfor this command to work). The short term goal is to sync these versions as they are updated by our infrastructure and postgres teams, then to see the nix packaged versions build successfully in parallel over time, along with tests of the nix packaged versions passing.The supabase/postgres repo will continue to source it's dependencies from ansible for the short term, while we stabilize this nix build.
This pr also updates postgres to 15.6
Next steps
Forthcoming PR's will include:
Impact on users of this repo
As of this PR, there is no impact on users of the repo.