catchup/batch-05: Multi-version extensions wave 2 #7
Conversation
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
* feat: support multiple versions of the pgmq extension Build multiple versions of the pgmq extension on different PostgreSQL versions. Add test for the extensions and their upgrade on PostgreSQL 15 and 17. * chore: bump suffix to test * chore: bump version to release --------- Co-authored-by: Sam Rose <[email protected]>
…1825) pg_regress tests are failing because the helper function pgmq._extension_exists() is missing in the 1.5.0 to 1.5.1 migration script. This change adds the missing function to the migration script.
…ase#1757) * feat: multiple versions for the pg_jsonschema extension Build multiple versions of the pg_jsonschema extension to on different PostgreSQL versions. Add test for the extensions and their upgrade on PostgreSQL 15 and 17. * fix: centralize bindgen hook override for pgrx extensions Move the bindgen hook fix for ARM NEON vector ABI issues from pg_graphql to mkPgrxExtension, making it available to all pgrx-based extensions. This fix applies to pgrx versions 0.6.1 through 0.11.2 when building on aarch64-linux. * fix: missing dependency on macOS for pg_jsonschema * chore: bump to release --------- Co-authored-by: Sam Rose <[email protected]>
* fix(pgmq): replace drop_queue function if exists We introduced a patch to override pgmq.drop_queue(TEXT) to conditionally drop objects only if they are part of the extension in `ansible/ansible/files/postgresql_extension_custom_scripts/pgmq/after-create.sql` . This script might have been installed on installations with existing 1.4.4 extensions. When the user tries to upgrade pgmq from 1.4.4 to 1.5.1, the upgrade process will fail because the upgrade script doesn't expect `pgmq.drop_queue(TEXT)` to exist. This change introduce the a patch to the pgmq extension to use `CREATE OR REPLACE FUNCTION` instead of `CREATE FUNCTION` for `pgmq.drop_queue(TEXT)` in the upgrade script from 1.4.5 to 1.5.0. * feat: test that the pgmq extension works well with the after create script We create a new custom nixos test for the pgmq extension to test that the extension works well with the after-create.sql script present in `ansible/files/postgresql_extension_custom_scripts/pgmq/after-create.sql`. * chore: bump versions to release post-rebase --------- Co-authored-by: Sam Rose <[email protected]>
* feat(wrappers): add versions 0.4.5, 0.4.6, and 0.5.0 * feat(wrappers): add versions 0.4.3, 0.4.4, 0.5.5 * feat(wrappers): add versions 0.3.0, 0.4.1, 0.4.2 * chore: add release suffix for testing * chore: bump version for release --------- Co-authored-by: Sam Rose <[email protected]>
…ase#1684) * feat: support multiple versions of the plpgsql_check extension Build multiple versions of the plpgsql_check extension on different PostgreSQL versions. Add test for the extensions and their upgrade on PostgreSQL 15 and 17. * tests: refactor to use the default nixos tests * fix(plpgsql-check): add missing upgrade path files between versions Generate empty SQL files for version-to-version upgrade paths to satisfy PostgreSQL extension upgrade requirements. * feat: requires switch version script due to shared_preload * fix: test with plpgsql_check extension --------- Co-authored-by: Sam Rose <[email protected]>
…1688) * feat: support multiple versions of the pg_repack extension Build multiple versions of the pg_repack extension on different PostgreSQL versions. Add test for the extensions and their upgrade on PostgreSQL 15 and 17. * chore: bump to test * tests: basic test for repack * chore: bump to release --------- Co-authored-by: Sam Rose <[email protected]>
) * feat: support multiple versions of the pgroonga extension Build multiple versions of the pgroonga extension on different PostgreSQL versions. Add test for the extensions and their upgrade on PostgreSQL 15 and 17. * refactor(nix): make sure ext contains only extensions Moved sfcgal and mecab-naist-jdic from nix/ext to nix/packages. * feat: resolve a few issues with tests and integration with tooling * fix: make sure that docker image has full/correct groonga/pgroonga handling * chore: bump version to release --------- Co-authored-by: Sam Rose <[email protected]>
…#1755) * feat: multiple versions for the pg_hashids extension Build multiple versions of the pg_hashids extension on different PostgreSQL versions. Add test for the extensions and their upgrade on PostgreSQL 15 and 17. * feat: use default nixos extension test And run pg_regress tests for pgtap as part of the unified extension tests * chore: bump version to release --------- Co-authored-by: Sam Rose <[email protected]>
* feat: support multiple versions of the plv8 extension Build multiple versions of the plv8 extension on different PostgreSQL versions. Add test for the extensions and their upgrade on PostgreSQL 15 and 17. * Fix coffeejs & livescript extensions * Avoid upgrade issue Port plv8/plv8#552 on version 3.1.x Upgrade process between 3.1.4 and 3.1.5 fails with a segfault when running ALTER EXTENSION plv8 UPDATE TO '3.1.5'. To avoid relying on the upgrade code, we replace the upgrade process by dropping the extension first and then install the new version. * feat: rebase nixos tests Use extension test library Test postgresql 15 only Add pg_regress tests * fix: remove plv8 from postgres 17 regress tests * chore: bump 1 more to get in line behind wrappers update --------- Co-authored-by: Sam Rose <[email protected]>
* feat: multiple versions for the vault extension Build multiple versions of the vault extension on different PostgreSQL versions. Add test for the extensions and their upgrade on PostgreSQL 15 and 17. * fix: nixos tests for pg_repack, pgroonga, and plpgsql_check to use the supabase_admin user We switched to using the supabase_admin user for our Postgres tests instead of the default postgres user. This change updates the authentication methods and user management in the NixOS test configurations for the pg_repack, pgroonga, and plpgsql_check extensions. * fix: nixos test for plv8 extension to use the supabase_admin user We switched to using the supabase_admin user for our Postgres tests instead of the default postgres user. This change updates the authentication methods and user management in the NixOS test configurations for the plv8 extension. * chore: bump one more --------- Co-authored-by: Sam Rose <[email protected]>
* feat: multiple versions for the pgaudit extension Build multiple versions of the pgaudit extension on different PostgreSQL versions. Add test for the extensions and their upgrade on PostgreSQL 15 and 17. * chore: add release suffix for testing * feat: include migrations on newer version, for all previous * fix: postgres integration tests * fix: strip suffix on passthru * fix: just use the the name * fix: try without list * Fix pgaudit upgrade * fix: migration handling --------- Co-authored-by: Sam Rose <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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
Upstream commits
6e3ae5b6feat: multiple versions of pgmq extension (feat: support multiple versions of the pgmq extension supabase/postgres#1668)39f9a0e0fix(pgmq): add missing helper function (fix(pgmq): add missing helper function in migration script supabase/postgres#1825)e67b4782feat: multiple versions of pg_jsonschema extension (feat: support multiple versions of the pg_jsonschema extension supabase/postgres#1757)bbfc14b7fix(pgmq): replace drop_queue function if exists (fix(pgmq): replace drop_queue function if exists supabase/postgres#1828)d99dc846feat(wrappers): support more versions (feat(wrappers): support more versions supabase/postgres#1831)9bb2878ffeat: multiple versions of plpgsql_check extension (feat: support multiple versions of the plpgsql_check extension supabase/postgres#1684)0fc42a55feat: multiple versions of pg_repack extension (feat: support multiple versions of the pg_repack extension supabase/postgres#1688)52deb6f6feat: multiple versions of pgroonga extension (feat: support multiple versions of the pgroonga extension supabase/postgres#1677)3433882afeat: multiple versions of pg_hashids extension (feat: support multiple versions of the pg_hashids extension supabase/postgres#1755)8ac1c905feat: multiple versions of plv8 extension (feat: support multiple versions of the plv8 extension supabase/postgres#1676)3b2b18a3feat: multiple versions for vault extension (feat: multiple versions for the vault extension supabase/postgres#1661)704e04eefeat: multiple versions of pgaudit extension (feat: support multiple versions of the pgaudit extension supabase/postgres#1758)Fork customizations preserved
kilobase.nixandpg_failover_slots.nixin extension listsbuildPgrxExtension_0_15_0in overlaysBatch 5 of 14 — upstream catch-up series
🤖 Generated with Claude Code