Add make print-pgtle target for combined pg_tle install files - #94
Merged
jnasbyupgrade merged 2 commits intoSep 8, 2026
Merged
Conversation
`print-pgtle` prints the generated pg_tle registration SQL for each
extension to stdout instead of running it, letting a consumer build a
combined multi-extension install file without needing to know the
extension name or which `pg_tle/` version-range directory applies:
$(MAKE) --no-print-directory -C ../deps/cat_tools print-pgtle >> pgtle-all.sql
Depends on `pgtle` (regenerates SQL first, like `run-pgtle`). Selects
the directory via the new `PGXNTOOL_PGTLE_TARGET_VERSION` variable (an
actual pg_tle version like `1.5.2`) if set, otherwise via the installed
pg_tle version (same detection `run-pgtle` uses). Deliberately not
named bare `PGTLE_VERSION` or reusing `PGXNTOOL_PGTLE_VERSION`: the
former would reopen the issue Postgres-Extensions#78 collision with a CI job's env var of
that name, and the latter holds a range, not an exact version -- two
different concepts that would silently diverge if collapsed into one
variable.
`--no-print-directory` is required whenever this is invoked
recursively for stdout capture: GNU Make auto-prints "Entering
directory"/"Leaving directory" to stdout for recursive invocations,
which would otherwise corrupt the redirected file. Documented
prominently since it's easy to miss.
Documents the new target and variable in README.asc (+ regenerated
README.html).
Related changes in pgxntool-test:
- test/sequential/04-pgtle.bats: PGXNTOOL_PGTLE_TARGET_VERSION directory
selection, non-collision with bare PGTLE_VERSION, and a regression
test for the --no-print-directory requirement
- test/standard/pgtle-install.bats: DB-fallback and not-installed error
path coverage
Fixes Postgres-Extensions#21.
Co-Authored-By: Claude <noreply@anthropic.com>
|
Important Review skippedAuto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Advanced Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
1 task
… for the Postgres-Extensions#93 _PGXNTOOL_ rename
jnasbyupgrade
marked this pull request as ready for review
September 8, 2026 20:56
jnasbyupgrade
added a commit
to Postgres-Extensions/pgxntool-test
that referenced
this pull request
Sep 8, 2026
Companion tests for pgxntool's new `make print-pgtle` target (Postgres-Extensions/pgxntool#94). - `test/sequential/04-pgtle.bats`: `PGXNTOOL_PGTLE_TARGET_VERSION` selects and prints the matching `pg_tle/` directory's SQL exactly; an older target version maps to the correct older range; a bare `PGTLE_VERSION` env var does not leak into the new variable; a regression test proving `--no-print-directory` is required to avoid GNU Make's `Entering directory`/`Leaving directory` stdout pollution on recursive invocation. - `test/standard/pgtle-install.bats`: falls back to the installed pg_tle version when no target version is set; errors cleanly when pg_tle isn't installed and no target version is set. ## Companion PR pgxntool: Postgres-Extensions/pgxntool#94
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
Adds a
make print-pgtletarget that prints the generated pg_tle registration SQL for each extension to stdout instead of running it, so a consumer can build a combined multi-extension install file:pgtle(regenerates SQL first, likerun-pgtle).PGXNTOOL_PGTLE_TARGET_VERSIONvariable (an actual pg_tle version like1.5.2, not a range) selects the directory; falls back to the installed pg_tle version if unset.PGTLE_VERSION(would reopen the pgtle.sh: Makefile's PGTLE_VERSION variable silently collides with a consumer's same-named env var #78 collision) or reusingPGXNTOOL_PGTLE_VERSION(that holds a range, a different concept).Entering directory/Leaving directoryto stdout on recursive invocation, corrupting a redirected combined file unless--no-print-directoryis passed. Called out prominently in README.asc and base.mk.Companion PR
pgxntool-test: Postgres-Extensions/pgxntool-test#73
Test plan
Fixes #21.