Skip to content
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

Prepare 0.4.1 #508

Merged
merged 1 commit into from
Mar 25, 2022
Merged

Prepare 0.4.1 #508

merged 1 commit into from
Mar 25, 2022

Conversation

Hoverbear
Copy link
Contributor

@Hoverbear Hoverbear commented Mar 25, 2022

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 the pgx extension Cargo.toml's pgx* versions to 0.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)
  • We now #[inline(always)] on pgx::Aggregate's memory context swapping code. (Improve Aggregate performance #487)
  • cargo pgx status will by default show the status of all pgx managed PostgreSQLs, instead of the default if one exists in the Cargo.toml. (cargo pgx status always defaults to all #505)
  • cargo pgx schema was producing color codes outside of the normal xterm-256color codes, this produced unpleasant output on some terminals (notably Mac's terminal.app). When the output of cargo pgx schema is a TTY it will now produce xterm-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)
  • If cargo pgx test experiences a cargo 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)
  • Documentation fixes. (README minor fixes #496)

@Hoverbear Hoverbear self-assigned this Mar 25, 2022
@Hoverbear Hoverbear changed the base branch from master to develop March 25, 2022 21:51
Signed-off-by: Ana Hobden <[email protected]>
@Hoverbear Hoverbear merged commit 0a473d2 into develop Mar 25, 2022
@eeeebbbbrrrr eeeebbbbrrrr deleted the prepare-0.4.1 branch June 20, 2023 18:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant