chore(deps): update dependency tensorchord/pgvecto.rs to v0.2.1 #16
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.
This PR contains the following updates:
v0.2.0
->v0.2.1
Release Notes
tensorchord/pgvecto.rs (tensorchord/pgvecto.rs)
v0.2.1
Compare Source
Improvements
NULL
can now be safely inserted into vector columns without error. They will be skipped duringpgvecto.rs
index creation, but exist in the table. A query on a vector column will never return a result containing aNULL
.SIGQUIT
instead ofSIGHUP
to trigger a peaceful exit, sinceSIGHUP
is defined as configure reload byPostgres
.v0.1.10
tov0.2.0
is broken. Users can now upgrade directly tov0.2.1
if they are currently usingv0.1.10
.Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.