chore(release): bump to 0.4.0 with no-op PG migration - #123
Open
JoshDreamland wants to merge 2 commits into
Open
chore(release): bump to 0.4.0 with no-op PG migration#123JoshDreamland wants to merge 2 commits into
JoshDreamland wants to merge 2 commits into
Conversation
Contributor
There was a problem hiding this comment.
Pull request overview
This PR prepares the pg_stat_ch extension for the v0.4.0 release by updating the PGXN metadata version fields in META.json so the published version matches the upcoming tag.
Changes:
- Bump
META.jsontop-levelversionfrom0.3.11to0.4.0. - Bump
provides.pg_stat_ch.versionfrom0.3.11to0.4.0.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Per team decision: bump the extension's default_version alongside the 0.4.0 tag even though there's no SQL interface change this release, so ALTER EXTENSION has a defined migration path from 0.3 to 0.4 instead of a gap. - sql/pg_stat_ch--0.4.sql: identical to --0.3.sql (no function/type changes). Added rather than renaming 0.3's script, since 0.3 is a live, currently-installed version (unlike the 0.1 retirement precedent in eb3a5dd) — explicit VERSION '0.3' installs and the existing 0.1->0.3 upgrade path both still need it to exist. - sql/pg_stat_ch--0.3--0.4.sql: no-op incremental migration, with a comment noting what this release actually changes lives entirely on the ClickHouse side (the new events_raw schema + the use_unified_arrow_exporter opt-in GUC), not in this extension's SQL interface. - pg_stat_ch.control: default_version 0.3 -> 0.4. CMakeLists.txt's install rule globs sql/pg_stat_ch--*.sql, so no build-system changes needed to pick up the new files. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
JoshDreamland
changed the title
Contributor
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 4 out of 4 changed files in this pull request and generated no new comments.
Comments suppressed due to low confidence (1)
sql/pg_stat_ch--0.3--0.4.sql:4
- There is regression test coverage for extension upgrades up to 0.3 (test/regression/sql/upgrade.sql), but nothing exercises the new 0.3 → 0.4 update path. Adding a small regression test that runs
ALTER EXTENSION pg_stat_ch UPDATE TO '0.4'would help catch packaging/upgrade-script issues (e.g., missing script, script lookup failures) before release.
\echo Use "ALTER EXTENSION pg_stat_ch UPDATE TO '0.4'" to load this file. \quit
-- 0.4 is a no-op on the Postgres side: no functions, types, or other SQL
-- objects changed. The default_version bump exists purely so
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
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.
Prep work ahead of tagging
v0.4.0(minor release — unified Arrow exporter +use_unified_arrow_exporterGUC, events_raw ClickHouse schema unification).What changed
META.json:versionandprovides.pg_stat_ch.versionbumped 0.3.11 → 0.4.0 (PGXN reads this file for the published version, must match the tag).pg_stat_ch.control:default_versionbumped 0.3 → 0.4.sql/pg_stat_ch--0.4.sql: new, identical to--0.3.sql— no SQL interface changes this release, confirmed zero diff tosql/since v0.3.11.sql/pg_stat_ch--0.3--0.4.sql: new no-op incremental migration, per team decision to giveALTER EXTENSION UPDATEa defined path from 0.3 to 0.4 even though there's nothing to actually migrate. Comment explains that what's actually changing this release lives entirely on the ClickHouse side (newevents_rawschema, opt-in via GUC), not in the extension's own SQL interface.sql/pg_stat_ch--0.3.sqlis kept as-is (not renamed) since 0.3 is a live, currently-installed version — unlike the 0.1 retirement precedent, explicitVERSION '0.3'installs and the existing 0.1→0.3 upgrade path both still need it.CMakeLists.txt's install rule globs
sql/pg_stat_ch--*.sql, so no build-system changes needed.