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 release includes some minor performance and UX improvements.
Release notes
0.4.1
Upgrading
Please make sure to run
cargo install cargo-pgx --version 0.4.1
and update all thepgx
extensionCargo.toml
'spgx*
versions to0.4.1
.What's Changed
Internal::get_or_insert_default
, and similar functions were doing some unnecessary allocations. Removing them improves the speed of these functions significantly. (Improve Internal perf #488)#[inline(always)]
onpgx::Aggregate
's memory context swapping code. (Improve Aggregate performance #487)cargo pgx status
will by default show the status of allpgx
managed PostgreSQLs, instead of the default if one exists in theCargo.toml
. (cargo pgx status
always defaults toall
#505)cargo pgx schema
was producing color codes outside of the normalxterm-256color
codes, this produced unpleasant output on some terminals (notably Mac'sterminal.app
). When the output ofcargo pgx schema
is a TTY it will now producexterm-256color
style codes, and use the user's terminal colors. This removes the need to specify if the user was using a light theme. (cargo pgx schema
uses XTERM colors #507)cargo pgx test
experiences acargo
related error, we don't report a full eyre error, we just report the cargo errors. (Cleanly error on cargo pgx test build failure #491)