-
Notifications
You must be signed in to change notification settings - Fork 1
Comparing changes
Open a pull request
base repository: tensorchord/pgrx
base: v0.12.9
head repository: tensorchord/pgrx
compare: master
Commits on Oct 27, 2024
-
Configuration menu - View commit details
-
Copy full SHA for 77c6961 - Browse repository at this point
Copy the full SHA 77c6961View commit details -
use
allowlist_file
for bindgen (pgcentralfoundation#1922)Some platform definitions make bindgen unhappy (pgcentralfoundation#1882, rust-lang/rust-bindgen#2803 when compiling for x86_64-windows-msvc, `serialization error at builtin definitions: Cannot serialize type kind Opaque` when compiling for x86_64-windows-gnu on my machine), and `allowlist_file` could ensure that it does not happen.
Configuration menu - View commit details
-
Copy full SHA for 039c24f - Browse repository at this point
Copy the full SHA 039c24fView commit details
Commits on Oct 28, 2024
-
Configuration menu - View commit details
-
Copy full SHA for ae0335b - Browse repository at this point
Copy the full SHA ae0335bView commit details
Commits on Oct 29, 2024
-
add
pg_config --libdir
to linker search path (pgcentralfoundation#1932Configuration menu - View commit details
-
Copy full SHA for 7969a47 - Browse repository at this point
Copy the full SHA 7969a47View commit details
Commits on Nov 2, 2024
-
fix a deadlock in
cargo pgrx install
duringget_git_hash()
(pgcen……tralfoundation#1935) I can't quite explain why, but this function was deadlocking with this backtrace: ``` * thread pgcentralfoundation#1, name = 'cargo-pgrx', stop reason = signal SIGSTOP * frame #0: 0x00007fbe1eeb288d libc.so.6`syscall at syscall.S:38 frame pgcentralfoundation#1: 0x000055aee526c5d3 cargo-pgrx`std::sys::sync::mutex::futex::Mutex::lock_contended::h6389e2305b0b005c [inlined] std::sys::pal::unix::futex::futex_wait::h30abf43e2d55aa33 at futex.rs:67:21 frame pgcentralfoundation#2: 0x000055aee526c590 cargo-pgrx`std::sys::sync::mutex::futex::Mutex::lock_contended::h6389e2305b0b005c at futex.rs:57:13 frame pgcentralfoundation#3: 0x000055aee4157835 cargo-pgrx`std::sync::mutex::Mutex$LT$T$GT$::lock::h4d2bb65800cc6fd3 at futex.rs:29:13 frame pgcentralfoundation#4: 0x000055aee41577ed cargo-pgrx`std::sync::mutex::Mutex$LT$T$GT$::lock::h4d2bb65800cc6fd3(self=0x000055aee6926c20) at mutex.rs:317:24 frame pgcentralfoundation#5: 0x000055aee406c779 cargo-pgrx`cargo_pgrx::command::install::get_git_hash::ha84d504db9d1bba8(manifest_path=0x00007ffdc43b83b0) at install.rs:507:9 frame pgcentralfoundation#6: 0x000055aee406d6e9 cargo-pgrx`cargo_pgrx::command::install::filter_contents::h8c710847129ba6be(manifest_path=0x00007ffdc43b8d10, input=String @ 0x00007ffdc43b8940) at install.rs:541:46 ```
Configuration menu - View commit details
-
Copy full SHA for 7de7210 - Browse repository at this point
Copy the full SHA 7de7210View commit details -
Configuration menu - View commit details
-
Copy full SHA for 2409ce2 - Browse repository at this point
Copy the full SHA 2409ce2View commit details -
Configuration menu - View commit details
-
Copy full SHA for 8048ab3 - Browse repository at this point
Copy the full SHA 8048ab3View commit details
Commits on Nov 9, 2024
-
lock patch version of pgrx-bindgen (pgcentralfoundation#1939)
The typo makes my extension using v0.12.7 pulling pgrx-bindgen v0.12.8.
Configuration menu - View commit details
-
Copy full SHA for 7b68a18 - Browse repository at this point
Copy the full SHA 7b68a18View commit details
Commits on Nov 13, 2024
-
Allow creating Oid from a u32 in a const context (pgcentralfoundation…
…#1943) This adds a `const fn` to create an `Oid` from a `u32`. `Oid::from_u32_unchecked` is the only way to do that currently, but it's deprecated and its successor `From::from` is non-const.
Configuration menu - View commit details
-
Copy full SHA for 6c9a85f - Browse repository at this point
Copy the full SHA 6c9a85fView commit details
Commits on Nov 15, 2024
-
Configuration menu - View commit details
-
Copy full SHA for 68c4970 - Browse repository at this point
Copy the full SHA 68c4970View commit details
Commits on Nov 19, 2024
-
Add utils/acl.h (pgcentralfoundation#1945)
Add useful ACL management functions
Configuration menu - View commit details
-
Copy full SHA for 6129d66 - Browse repository at this point
Copy the full SHA 6129d66View commit details
Commits on Nov 20, 2024
-
fix warnings (pgcentralfoundation#1948)
1. `unexpected_cfgs` warnings are emitted for extension crates by latest nightly rustc, and it's annoying (`pgrx_embed` in `pgrx_embed`, and `Pg_magic_func` if extension does not support all postgres major versions) 2. `PanicInfo` warnings are emitted by latest stable rustc while using local pgrx as a patch 3. `static_mut_refs` warnings are emitted by latest nightly rustc while using local pgrx as a patch
Configuration menu - View commit details
-
Copy full SHA for 49227e7 - Browse repository at this point
Copy the full SHA 49227e7View commit details -
Add catalog/catalog.h (pgcentralfoundation#1946)
Useful functions for catalog naming conventions and other hard-wired knowledge
Configuration menu - View commit details
-
Copy full SHA for 1efdfee - Browse repository at this point
Copy the full SHA 1efdfeeView commit details -
Check wakeup_flags from
wait_latch
function to exit on `WL_POSTMAST……ER_DEATH` (pgcentralfoundation#1938) There are some cases when the `wait_latch` loop in background worker is not being interrupted after the postmaster was exited. It can be reproduced by running postgres directly using `/opt/homebrew/opt/postgresql@17/bin/postgres -D /opt/homebrew/var/postgresql@17` and after the background worker will be started you will need to send `SIGKILL` to the postmaster process. (the issue is not reproducible when managing postgres via `pg_ctl`, I have encountered this issue during local development as homebrew service runs postgres directly using `postgres` binary) Then you can see that the postgres will be exited, but background worker process will remain active. > Make sure the WL_POSTMASTER_DEATH flag is set when calling that function, and verify the return code for a prompt exit in the emergency case that postgres itself has terminated. (see pgcentralfoundation#1938 for an example)
Configuration menu - View commit details
-
Copy full SHA for 7ca80af - Browse repository at this point
Copy the full SHA 7ca80afView commit details -
Changed args of prepare methods to be slices (pgcentralfoundation#1933)
Since there's an opportunity to break more things for `0.13` I decided to improve the `prepare` and `prepare_mut` methods as well. The motivation for that is the same as for pgcentralfoundation#1858, `&[]` requires no heap allocations on the heap if there's a fixed set of arguments.
Configuration menu - View commit details
-
Copy full SHA for c1e5dd9 - Browse repository at this point
Copy the full SHA c1e5dd9View commit details
Commits on Nov 21, 2024
-
Updating readme.me (pgcentralfoundation#1949)
Updating readme for financial donations as well as encouraging people to join the Discord server
Configuration menu - View commit details
-
Copy full SHA for f1da6d9 - Browse repository at this point
Copy the full SHA f1da6d9View commit details
Commits on Nov 22, 2024
-
Introduce a blocklist of "yanked" Postgres versions (pgcentralfoundat…
…ion#1950) Due to the out-of-band release set described here: https://www.postgresql.org/about/news/postgresql-172-166-1510-1415-1318-and-1222-released-2965/, we should refuse to compile on the prior point releases mentioned in this press release.
Configuration menu - View commit details
-
Copy full SHA for a0ecc8f - Browse repository at this point
Copy the full SHA a0ecc8fView commit details
Commits on Nov 25, 2024
-
Added
oids_of!
macro (pgcentralfoundation#1879)That's an improvement for SPI making it less cumbersome. Just to feel the difference look at the tests. Who would really want to write something like `PgBuiltInOids::INT4OID.oid()` instead of just telling a Rust type?
Configuration menu - View commit details
-
Copy full SHA for eda7549 - Browse repository at this point
Copy the full SHA eda7549View commit details
Commits on Dec 9, 2024
-
Configuration menu - View commit details
-
Copy full SHA for 1f1dda3 - Browse repository at this point
Copy the full SHA 1f1dda3View commit details -
Configuration menu - View commit details
-
Copy full SHA for 41516d7 - Browse repository at this point
Copy the full SHA 41516d7View commit details -
Configuration menu - View commit details
-
Copy full SHA for 56af59f - Browse repository at this point
Copy the full SHA 56af59fView commit details
Commits on Dec 22, 2024
-
Configuration menu - View commit details
-
Copy full SHA for 4141830 - Browse repository at this point
Copy the full SHA 4141830View commit details -
Configuration menu - View commit details
-
Copy full SHA for d4bfc4b - Browse repository at this point
Copy the full SHA d4bfc4bView commit details -
Configuration menu - View commit details
-
Copy full SHA for 5b80a47 - Browse repository at this point
Copy the full SHA 5b80a47View commit details
Commits on Feb 11, 2025
-
Configuration menu - View commit details
-
Copy full SHA for 5b87eca - Browse repository at this point
Copy the full SHA 5b87ecaView commit details
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 v0.12.9...master