Update Rust crate pgrx-tests to ~0.11.0 #3
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
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
renovate
bot
force-pushed
the
renovate/pgrx-tests-0.x
branch
3 times, most recently
from
db06da0
to
387c4f3
Compare
|
This can't be merged until https://github.com/coredb-io/trunk supports prgx version |
renovate
bot
force-pushed
the
renovate/pgrx-tests-0.x
branch
from
387c4f3
to
f098f18
Compare
renovate
bot
changed the title
renovate
bot
changed the title
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/pgrx-tests-0.x
branch
from
f098f18
to
4a9a9bc
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/pgrx-tests-0.x
branch
from
4a9a9bc
to
afac0ca
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/pgrx-tests-0.x
branch
from
afac0ca
to
bd793d8
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/pgrx-tests-0.x
branch
from
bd793d8
to
6726570
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/pgrx-tests-0.x
branch
from
6726570
to
5d078de
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/pgrx-tests-0.x
branch
from
5d078de
to
8009798
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/pgrx-tests-0.x
branch
from
8009798
to
3e56b6b
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/pgrx-tests-0.x
branch
from
3e56b6b
to
b04112e
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/pgrx-tests-0.x
branch
from
b04112e
to
138e060
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/pgrx-tests-0.x
branch
from
138e060
to
893942d
Compare
renovate
bot
force-pushed
the
renovate/pgrx-tests-0.x
branch
from
893942d
to
acc3f80
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/pgrx-tests-0.x
branch
from
acc3f80
to
676bdba
Compare
renovate
bot
changed the title
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/pgrx-tests-0.x
branch
from
676bdba
to
a68fdc9
Compare
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.
This PR contains the following updates:
~0.9.1->~0.11.0Release Notes
pgcentralfoundation/pgrx (pgrx-tests)
v0.11.4Compare Source
Welcome to pgrx v0.11.4!
This is a minor release to add some additional functionality to
cargo-pgrxto enable running tests in atypical CI configurations and the ability to turn off its colored output via theNO_COLORenvironment variable. This minor release also includes a small change that should measurably improve compilation times for all extensions.To update to this this, please run
cargo install cargo-pgrx --version 0.11.4 --lockedand ensure to update your extension'sCargo.tomlfile to use pgrx v0.11.4.What Changed
cargo-pgrxchangesPR #1652 was cherry-picked into this release to include the new
--runasand--pgdataarguments tocargo pgrx test.--runasuses the systemsudocommand to run the temporary Postgres cluster process as the specified user, and uses--pgdataas the location where the cluster's PGDATA directory should be initialized.cargo-pgrxnow understands theNO_COLORandFORCE_COLORenvironment variables supported by the upstream dependency it uses for generated colored output. See https://crates.io/crates/owo-colors for details. This is from PR #1664Compilation Times
pgrx generates a (very large) set of Rust bindings that represent the "rust version" of all the internal Postgres symbols (functions, globals, etc). In the case of functions, pgrx also generates wrapper functions so it can instrument calls with the proper guard rails. It turns out, simply annotating these wrapper functions with
#[inline]drastically improves compilation time as it allows the rust compiler to defer their compilation until the very end. Which ultimately means only the functions used by an extension get compiled -- the others are DCE'd. This came from PR #1616.Thanks!
Thanks to @usamoi for improving our compilation times, and shout out to @theory for his first contribution!
Full Changelog: pgcentralfoundation/pgrx@v0.11.3...v0.11.4
v0.11.3Compare Source
The pgrx 0.11.3 release addresses several UB risks of pgrx, updates its dependencies to address possible security risks on a few points, and includes considerable numbers of additional headers in the release. It should also now be easier to actually use cargo-pgrx on a mildly more interesting network configuration, though you may need to specify
--no-default-featureswith either--features native-tlsor--features rustlswhen youcargo install cargo-pgrx.New Bindings!
New bindings added thanks to
"...wait, that's UB?"
Two UB fixes!
Ergonomics
ereport!macro in https://github.com/pgcentralfoundation/pgrx/pull/1472Less transport-level security problems in cargo-pgrx
Together these should mean it's possible to actually use cargo-pgrx on whatever your network configuration is, but you might have to use
cargo install --no-default-features --features native-tlsto install with native-tls (which, on Linux, means OpenSSL). By default, you will use rustls.Many tiny dependency updates
These address some largely-hypothetical security risks, but one is particularly important: the bindgen update means we now should be compatible with some aarch64 builds that might have failed.
Full Changelog: pgcentralfoundation/pgrx@v0.11.2...v0.11.3
v0.11.2Compare Source
pgrx v0.11.2 is a minor release which
Oid::from_u32_uncheckedAPI... because it is actually possible to do via casting in a query, which makes it effectively impossible for us to not wind up providing it via some other safe API, since the source is also an easily-Copied type. Thus you can now simply useFrom::fromfor it. Thanks to @thomcc for this discovery, implemented by @workingjubilee in https://github.com/pgcentralfoundation/pgrx/pull/1374As usual,
cargo install cargo-pgrx --version 0.11.2 --lockedand be on your merry way!Thanks everyone!
Full Changelog: pgcentralfoundation/pgrx@v0.11.1...v0.11.2
v0.11.1Compare Source
Hello. Welcome to pgrx v0.11.1, a bugfix release that hopefully addresses a very annoying persistent problem for users, especially ones that were trying to use pgrx with Postgres 16! My (@workingjubilee)'s changes in
b992f55now steer bindgen towards including the exact compiler-header directory that we require, instead of relying on clang-sys to guess the right directory in ways that can go horribly wrong. Unfortunately, this may make our build step more brittle in certain cases. Please report issues as they arise, so that we can continue to refine our build system, and eventually fix this in bindgen proper!This new behavior can still be disabled by setting
PGRX_BINDGEN_NO_DETECT_INCLUDES, as it is still a form of autodetecting includes, but if this release fixes your build that was previously relying on that or any other easily-removed hack, please let us know!Also, thanks to @LuminousMonkey, you can now use pgrx on illumos, an operating system descended from Solaris, with no changes to your source code!
Full Changelog: pgcentralfoundation/pgrx@v0.11.0...v0.11.1
v0.11.0Compare Source
Welcome to pgrx v0.11.0. It's a new "major" release with some new features, a faster "build.rs", and some bugfixes.
As always, please update by running
cargo install cargo-pgrx --version 0.11.0 --lockedand update your extension crateCargo.tomlfiles accordingly.What's Changed
Faster Buildings
@workingjubilee did some work to improve build times. As measured on their computer against
cargo check, it's roughly a quarter faster. In doing so, the generated "bindings.rs" files look a little different and our "build.rs" has been cleaned up a bit.is_for_releaseonce by @workingjubilee in https://github.com/pgcentralfoundation/pgrx/pull/1315Pure Rust implementation for
PgList@workingjubilee did a tremendous amount of work creating a proper wrapper around Postgres' internal
Listtype, calledPgList.Some background here is that we intend to add the "dynamic function call" work (see below) to PL/Rust. In doing that work, use of Postgres'
Listtype is pretty important and pgrx' existing implementation was a) mostly in the cshim, and b) just not very-good-and-sound. Considering (b) and also that PL/Rust isn't able to use anything from pgrx' chsim (a), @workingjubilee set out to make a proper Rust wrapper/implementation of Postgres'Listtype.Note: As part of this,
NodeTagis now a properenum, which requires a small migration which is mostly satisfied by a regex-based find-replace ofNodeTag_T_[A-Za-z]*withNodeTag::T_$1.More Bindings
We've added more Postgres internals headers to the
pgrx-pg-syscrate:Dynamic Function Calling
pgrx now allows calling any SQL-defined function (ie, via
CREATE FUNCTION) in a (mostly) Rusty way with the new dynamic function calling support. Some documentation around this feature can be found in the sources, here and in the unit tests.As mentioned above, this feature will be exposed in PL/Rust soon. However, it's still an extremely powerful feature for pure pgrx extensions as it allows calling another function directly, with runtime type safety checks, without incurring any Spi overhead.
cargo pgrx install --sudoSometimes
cargo-pgrx installcan be tough to work with if targeting a package manager-managed Postgres installation as the various extension directories are owned by root.cargo pgrx install --sudofixes that by copying the files as root. The build, which is typically done as a regular user, is still run by that user -- only the file copying is run withsudo.cargo pgrx install --sudoby @eeeebbbbrrrr in https://github.com/pgcentralfoundation/pgrx/pull/1322Miscellaneous Work
Thanks!
Thanks to all the contributors! We appreciate the PRs and testing. And we especially like hearing about what you're building with pgrx.
Full Changelog: pgcentralfoundation/pgrx@v0.10.2...v0.11.0
v0.10.2Compare Source
Welcome to pgrx v0.10.2!
In pgrx v0.10.0, as part of a refactoring step in order to make refactoring easier in the future, without things like losing track of random functions, we... omitted a few functions! These depended on the cshim, but were not direct bindings, themselves. Oops. They're back now in
pgrx::pg_sys.cargo pgrxworks now for Postgres 16 on macOSInstalling extensions on macOS for Postgres 16 had problems due to recent changes to Postgres defaults. We have fixed this and expanded our test coverage for macOS to reduce the odds of this happening in the future, thanks to @bayandin in https://github.com/pgcentralfoundation/pgrx/pull/1300
composites compose better
There were some problems with composite types and arrays, and specifically arrays of composite types in composite types. These are the sorts of things that cause edge cases in PgHeapTuple. They should now be appropriately supported, however, thanks to @eeeebbbbrrrr in https://github.com/pgcentralfoundation/pgrx/pull/1303
#[pg_schema]will enable your bad ideasThe following should now work appropriately:
It does what you think it does. Since this can affect a global namespace in a way that makes it much easier to conflict with other extensions, it is best to avoid this. However, it is the sort of bad idea that extensions which "take over" the Postgres host to extensively redefine the host's capabilities, like ZomboDB does, may have to resort to in order to accomplish their goal. Thanks to @eeeebbbbrrrr in https://github.com/pgcentralfoundation/pgrx/pull/1302
Keep the bug reports coming
And thank you for reporting your issues!
v0.10.1Compare Source
This is pgrx v0.10.1. It includes support for Postgres v16 and since pg16 is now released,
cargo pgrx initwill now be able to download the latest version.As always, please install the latest cargo-pgrx with
cargo install cargo-pgrx --version 0.10.1 --lockedand update your Cargo.toml dependencies.What's Changed
#1295: Support the official Postgres v16 release
#1294: Add WAL recovery header bindings for pg15 and pg16
Full Changelog: pgcentralfoundation/pgrx@v0.10.0...v0.10.1
v0.10.0Compare Source
This is the final release of v0.10.0. Thanks everyone for the beta testing, pull requests, issues, and patience.
As always, install
cargo-pgrxwithcargo install cargo-pgrx --lockedand update your extension Cargo.toml files to use the0.10.0pgrx dependencies.This release includes support for Postgres 16RC1. Support for the previous betas has been removed. As such, a fresh
cargo pgrx initis required.What's Changed Since v0.10.0-beta.4
GetMemoryChunkContextport by @workingjubilee in https://github.com/pgcentralfoundation/pgrx/pull/1273pg_configisn't found. by @eeeebbbbrrrr in https://github.com/pgcentralfoundation/pgrx/pull/1271PostgresHashalso needEqby @workingjubilee in https://github.com/pgcentralfoundation/pgrx/pull/1264New Contributors
Changelog: pgcentralfoundation/pgrx@v0.10.0-beta.4...v0.10.0
v0.10.0's full set of changes throughout the entire beta period are:
pg_sys::Datuminto apgrx::Dateby @eeeebbbbrrrr in https://github.com/pgcentralfoundation/pgrx/pull/1177AnyNumericis no longer backed by Postgres-allocated memory by @eeeebbbbrrrr in https://github.com/pgcentralfoundation/pgrx/pull/1216#[pg_test]-generated tests. by @thomcc in https://github.com/pgcentralfoundation/pgrx/pull/1239Result<T, _>by @eeeebbbbrrrr in https://github.com/pgcentralfoundation/pgrx/pull/1241Fromimpls by @workingjubilee in https://github.com/pgcentralfoundation/pgrx/pull/1253cppflagsit needs (on macOS, anyway) by @thomcc in https://github.com/pgcentralfoundation/pgrx/pull/1247New Contributors
Full Changelog: pgcentralfoundation/pgrx@v0.9.8...v0.10.0
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.