Update pgaudit and other six other extensions #864
Merged
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
theory
requested review from
ianstanton,
vrmiguel and
ChuckHend
as code owners
theory
changed the title
|
This pull request is automatically being deployed by Amplify Hosting (learn more). |
Update the following extension build scripts, build from PGXN where possible, and upgrade the versions: * pg_text_semver v1.2.1 * pg_timeit at specific commit * pg_tle v1.2.0 * pg_track_settings * pg_uuidv7 v1.6.0 * pg_wait_sampling v1.1.6 Add separate build configurations for pgaudit, which has different versions for different major Postgres releases, but keep the extension name the same. Teach the extensions workflow not to build it on the wrong major versions, just like with pg_hint_plan.
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.
Update the following extension build scripts, build from PGXN where possible, and upgrade the versions:
Add separate build configurations for pgaudit, which has different versions for different major Postgres releases, but keep the extension name the same. Teach the extensions workflow not to build it on the wrong major versions, just like with pg_hint_plan.