Skip to content

cargo-pgrx: add --valgrind flag to cargo pgrx regress - #2290

Merged
eeeebbbbrrrr merged 1 commit into
pgcentralfoundation:developfrom
philippemnoel:add-valgrind-flag-to-regress
May 31, 2026
Merged

cargo-pgrx: add --valgrind flag to cargo pgrx regress#2290
eeeebbbbrrrr merged 1 commit into
pgcentralfoundation:developfrom
philippemnoel:add-valgrind-flag-to-regress

Conversation

@philippemnoel

@philippemnoel philippemnoel commented May 15, 2026

Copy link
Copy Markdown
Contributor

Summary

cargo pgrx start and cargo pgrx run already accept --valgrind, and the underlying start_postgres already knows how to launch Postgres under valgrind. But the flag was not exposed on cargo pgrx regressFrom<&Regress> for Run hardcoded valgrind: false, so there was no way to run the regression suite under valgrind without manually starting Postgres beforehand.

This adds --valgrind to Regress and propagates it through to Run. No new mechanism — just plumbing.

$ cargo pgrx regress --valgrind

Test plan

  • cargo check -p cargo-pgrx passes
  • cargo pgrx regress --help shows the new --valgrind flag
  • cargo pgrx regress --valgrind runs the regression suite under valgrind end-to-end

`cargo pgrx start` and `cargo pgrx run` already accept `--valgrind` and
the underlying `start_postgres` already knows how to launch Postgres
under valgrind, but the flag was not exposed on `cargo pgrx regress`:
`From<&Regress> for Run` hardcoded `valgrind: false`, so there was no
way to run the regression suite under valgrind without manually
starting Postgres first.

This adds the flag to `Regress` and propagates it through to `Run`.
@philippemnoel

Copy link
Copy Markdown
Contributor Author

The "verify package can build / ubuntu" run will be fixed once #2292 is merged

@eeeebbbbrrrr
eeeebbbbrrrr merged commit 2cd0d14 into pgcentralfoundation:develop May 31, 2026
14 of 15 checks passed
eeeebbbbrrrr added a commit that referenced this pull request May 31, 2026
Welcome to pgrx v0.18.1. This is a minor release but fixes important
build problems on aarch64 Linux introduced in v0.18.0.

As always, install the cli tool with `cargo install cargo-pgrx --version
0.18.1 --locked` and make sure to update your extension's to depend on
`=0.18.1`.


## What's Changed
* upgrade dependencies, including moving rust to 1.96.0 by @eeeebbbbrrrr
in #2296
* cargo-pgrx: inject `-Wl,--no-gc-sections` to keep `.pgrxsc` sections
on aarch64 Linux by @eeeebbbbrrrr in
#2280
* feat: include `rewrite/rewriteManip.h` by @isdaniel in
#2295
* Use `zip` instead of deprecated `zip-extract` by @cbandy in
#2294 (also by
@Natureshadow)
* cargo-pgrx: add `--valgrind` flag to `cargo pgrx regress` by
@philippemnoel in #2290
* cargo-pgrx: build Postgres in parallel during `cargo pgrx init` by
@philippemnoel in #2291
* ci: pass `--locked` to `cargo install --path cargo-pgrx` by
@philippemnoel in #2292
* Fix README version range inconsistency (17 → 18) by @hobostay in
#2287
* fix: don't allocate for static strings in `ereport!` by @gruuya in
#2282
* can `cargo clippy --allow-dirty --fix -- -Wclippy::use_self` by
@adamnemecek in #2283
* feature: teach `cargo pgrx schema` how to emit just the SQL for named
entities by @eeeebbbbrrrr in
#2293
* Fix "PostgresSQL" typo to "PostgreSQL" in test code by @hobostay in
#2286

## New Contributors
* @hobostay made their first contribution in
#2287
* @adamnemecek made their first contribution in
#2283
* @Natureshadow 

**Full Changelog**:
v0.18.0...v0.18.1
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.

2 participants