drop unused fuzzystrmatch postgres extension - #3473
Merged
Merged
Conversation
syphar
force-pushed
the
obsolete-postgres
branch
from
August 26, 2026 11:19
f2b9288 to
2b9fe98
Compare
Collaborator
|
This PR was rebased onto a different main commit. Here's a range-diff highlighting what actually changed. Rebasing is a normal part of keeping PRs up to date, so no action is needed—this note is just to help reviewers. |
Member
Author
GuillaumeGomez
approved these changes
Aug 26, 2026
Member
|
Nice! |
GuillaumeGomez
temporarily deployed
to
github-pages
August 26, 2026 11:59 — with
GitHub Actions
Inactive
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.
we don't use that since we migrated to using the crates.io search api a couple of years ago.
This also means we don't need the custom
Dockerfile-postgres.I adapted the initial migration, and made the reverse migration a noop,
because otherwise our testing would fail creating the extension in the new docker postgres image, since we don't create that with
install_extensions.sqlany more.