Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fetch remote extension in ALTER EXTENSION UPDATE statements #11102

Merged
merged 1 commit into from
Mar 9, 2025

Conversation

tristan957
Copy link
Member

Previously, remote extensions were not fetched unless they were used in some other manner. For instance, loading a BM25 index in pg_search fetches the pg_search extension. However, if on a fresh compute with pg_search 0.15.5 installed, the user ran ALTER EXTENSION pg_search UPDATE TO '0.15.6' without first using the pg_search extension, we would not fetch the extension and fail to find an update path.

@tristan957 tristan957 requested review from a team as code owners March 5, 2025 21:24
@tristan957 tristan957 requested review from hlinnaka, MMeent and jcsp March 5, 2025 21:24
Copy link

github-actions bot commented Mar 5, 2025

If this PR added a GUC in the Postgres fork or neon extension,
please regenerate the Postgres settings in the cloud repo:

make NEON_WORKDIR=path/to/neon/checkout \
  -C goapp/internal/shareddomain/postgres generate

If you're an external contributor, a Neon employee will assist in
making sure this step is done.

@tristan957 tristan957 requested a review from ololobus March 5, 2025 21:27
Copy link

github-actions bot commented Mar 5, 2025

7887 tests run: 7502 passed, 0 failed, 385 skipped (full report)


Flaky tests (1)

Postgres 15

Code coverage* (full report)

  • functions: 32.8% (8708 of 26525 functions)
  • lines: 48.8% (74414 of 152468 lines)

* collected from Rust tests only


The comment gets automatically updated with the latest test results
cb5fb4f at 2025-03-07T20:34:59.514Z :recycle:

@tristan957
Copy link
Member Author

tristan957 commented Mar 6, 2025

Confirmed that this works on staging. I'll work on adding a regression test.

@ololobus ololobus requested a review from lubennikovaav March 6, 2025 16:22
@tristan957 tristan957 force-pushed the tristan957/remote-extensions branch from 4b63333 to b1a556d Compare March 6, 2025 20:58
@tristan957 tristan957 requested a review from a team as a code owner March 6, 2025 20:58
@tristan957 tristan957 force-pushed the tristan957/remote-extensions branch from b1a556d to 6d6a7b0 Compare March 6, 2025 20:59
Copy link
Contributor

@a-masterov a-masterov left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good

@tristan957 tristan957 force-pushed the tristan957/remote-extensions branch from 6d6a7b0 to 95b09a7 Compare March 7, 2025 18:56
Previously, remote extensions were not fetched unless they were used in
some other manner. For instance, loading a BM25 index in pg_search
fetches the pg_search extension. However, if on a fresh compute with
pg_search 0.15.5 installed, the user ran `ALTER EXTENSION pg_search
UPDATE TO '0.15.6'` without first using the pg_search extension, we
would not fetch the extension and fail to find an update path.

Signed-off-by: Tristan Partin <[email protected]>
@tristan957 tristan957 force-pushed the tristan957/remote-extensions branch from 95b09a7 to cb5fb4f Compare March 7, 2025 18:57
@tristan957 tristan957 added this pull request to the merge queue Mar 9, 2025
Merged via the queue into main with commit 1b8c428 Mar 9, 2025
99 checks passed
@tristan957 tristan957 deleted the tristan957/remote-extensions branch March 9, 2025 17:38
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.

5 participants