Fix setting pg_trgm.similarity_threshold on new connection #1084
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.
Trello Card Link
https://trello.com/c/B8dTGjQO/1706-determine-why-some-search-results-in-api-are-not-returning-successfully-https-discoveryprovideraudiusco-v1-tracks-searchquery3la
Description
Sets (resets) pg_trgm.similarity_threshold every time the session manager engine creates a new connection. The setting persists across connections (which I had misunderstood before). Once set on the connection, any session that uses the connection will have the setting.
Services
Does it touch a critical flow like Discovery indexing, Creator Node track upload, Creator Node gateway, or Creator Node file system?
Delete an option.
How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide repro instructions & any configuration.
Include log analysis if applicable.
Repro of bug (before change)
SHOW pg_trgm.similarity_threshold
every time the search endpoint would hit.Rolled out this code change & repeated 1-5 and #6 returned successfully