-
-
Notifications
You must be signed in to change notification settings - Fork 272
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Prep 0.2.0-beta.2 #261
Merged
Merged
Prep 0.2.0-beta.2 #261
Conversation
This file contains 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
A user reported experiencing duplicate entries in builds using a Vec, so we now use a HashSet to ensure uniqueness. Signed-off-by: Ana Hobden <operator@hoverbear.org>
Signed-off-by: Ana Hobden <operator@hoverbear.org>
Signed-off-by: Ana Hobden <operator@hoverbear.org>
* feat: enable aarch64-darwin nix support Signed-off-by: Ana Hobden <operator@hoverbear.org>
- we were also missing a few `#[no_mangle]`s - ignore warnings about i128 not being ffi safe - `direct_function_call()` now expects an `extern "C"` function
This fixes issue #241. # Conflicts: # Cargo.lock # Cargo.toml # cargo-pgx/Cargo.toml # cargo-pgx/src/templates/cargo_toml # pgx-macros/Cargo.toml # pgx-pg-sys/Cargo.toml # pgx-tests/Cargo.toml # pgx-utils/Cargo.toml # pgx/Cargo.toml
* fix: Repair pgx-tests from root on darwin Signed-off-by: Ana Hobden <operator@hoverbear.org> * chore: add newline Signed-off-by: Ana Hobden <operator@hoverbear.org>
* support PostgreSQL 14 * include pg14 in CI tests * need pg14 in the Cargo.toml template for new pgx progjects * complete cargo-pgx support for pg14 * fix issue around shmem initialization * another feature for pg14
Co-authored-by: Jan Cristina <jan.cristina@starmind.com> Co-authored-by: Ana Hobden <operator@hoverbear.org>
Signed-off-by: Ana Hobden <operator@hoverbear.org>
* Fix issues with error handling across FFI boundaries This also makes a few functions unsafe, so we had to litter parts of the code with unsafe{} blocks. The primary user-facing change here is if users are using `pgx::direct_function_call()` to call Rust-based functions with the `#[pg_extern]` annotation, those functions now need to be called using `pgx::direct_pg_extern_function_call()`. In general, this is yet another follow-up to issue #241. * bump version to 0.1.25
* chore: improve toposort error Signed-off-by: Ana Hobden <operator@hoverbear.org> * chore: pretty print that toposort error Signed-off-by: Ana Hobden <operator@hoverbear.org> * fix: use unaliased name in positioning refs Signed-off-by: Ana Hobden <operator@hoverbear.org> Co-authored-by: Ana Hobden <operator@hoverbear.org>
… dependencies from github
usamoi
pushed a commit
to tensorchord/pgrx
that referenced
this pull request
Mar 6, 2025
* fix: dedupe fns_to_call (pgcentralfoundation#236) A user reported experiencing duplicate entries in builds using a Vec, so we now use a HashSet to ensure uniqueness. Signed-off-by: Ana Hobden <operator@hoverbear.org> * chore: update some dependencies (pgcentralfoundation#229) Signed-off-by: Ana Hobden <operator@hoverbear.org> * chore: ensure GitHub can blend (pgcentralfoundation#237) Signed-off-by: Ana Hobden <operator@hoverbear.org> * feat: Enable aarch64-darwin nix support (pgcentralfoundation#242) * feat: enable aarch64-darwin nix support Signed-off-by: Ana Hobden <operator@hoverbear.org> * resolve issue pgcentralfoundation#241: pg_extern functions need to be `extern "C"`. - we were also missing a few `#[no_mangle]`s - ignore warnings about i128 not being ffi safe - `direct_function_call()` now expects an `extern "C"` function * bump version to 0.1.23 * update generated bindings from macos * fix: Fixup Darwin linking issues (pgcentralfoundation#244) * fix: Repair pgx-tests from root on darwin Signed-off-by: Ana Hobden <operator@hoverbear.org> * chore: add newline Signed-off-by: Ana Hobden <operator@hoverbear.org> * feat: pg14 support (pgcentralfoundation#245) * support PostgreSQL 14 * include pg14 in CI tests * need pg14 in the Cargo.toml template for new pgx progjects * complete cargo-pgx support for pg14 * fix issue around shmem initialization * another feature for pg14 * fix issue with exported symbol for shared memory support * bump version to 0.1.24 * slice-into-datum (pgcentralfoundation#239) Co-authored-by: Jan Cristina <jan.cristina@starmind.com> Co-authored-by: Ana Hobden <operator@hoverbear.org> * fix a few issues around pg14 support * chore: update dependencies (pgcentralfoundation#248) Signed-off-by: Ana Hobden <operator@hoverbear.org> * Add link to new blog post (pgcentralfoundation#249) * Fix issues with error handling across FFI boundaries (pgcentralfoundation#250) * Fix issues with error handling across FFI boundaries This also makes a few functions unsafe, so we had to litter parts of the code with unsafe{} blocks. The primary user-facing change here is if users are using `pgx::direct_function_call()` to call Rust-based functions with the `#[pg_extern]` annotation, those functions now need to be called using `pgx::direct_pg_extern_function_call()`. In general, this is yet another follow-up to issue pgcentralfoundation#241. * bump version to 0.1.25 * Better debug output when entity graph is cyclic. (pgcentralfoundation#260) * chore: improve toposort error Signed-off-by: Ana Hobden <operator@hoverbear.org> * chore: pretty print that toposort error Signed-off-by: Ana Hobden <operator@hoverbear.org> * fix: use unaliased name in positioning refs Signed-off-by: Ana Hobden <operator@hoverbear.org> Co-authored-by: Ana Hobden <operator@hoverbear.org> * bump version to 0.2.0-beta.2 * upgrade dependencies * update comments * hack the sample's Cargo.toml file to use this specific version of pgx dependencies from github * remove old versions of postgres before we explicitly install pg13 * fix type-o * fix this test yet again. Co-authored-by: Ana Hobden <operator@hoverbear.org> Co-authored-by: jcrist1 <jan.cristina@gmail.com> Co-authored-by: Jan Cristina <jan.cristina@starmind.com> Co-authored-by: Ryan Lambert <rustprooflabs@users.noreply.github.com>
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.
No description provided.