You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The first issue is that pg_search has rather unsophisticated query processing (or made theirs less sophisticated at some point), which is defined here . This basically turns phrases into AND queries and doesn't support things like turning "quoted phrases" into Postgres's <-> (is next to) query operator.
pg_search is kinda-sorta-maintained (going off of issues and pull requests), so what I'm thinking we might want to do is to either fork or monkey-patch it and replace the tsquery function with something more sophisticated that understands "exact phrases" and puts in &s only when there's not an | or some other symbol in there.
We also have the question of whether to sort search results by date any more than we already do.
In any case, this is here so my research doesn't get lost and we remember to get back to this eventually.
The text was updated successfully, but these errors were encountered:
The first issue is that pg_search has rather unsophisticated query processing (or made theirs less sophisticated at some point), which is defined here . This basically turns phrases into AND queries and doesn't support things like turning "quoted phrases" into Postgres's <-> (is next to) query operator.
pg_search is kinda-sorta-maintained (going off of issues and pull requests), so what I'm thinking we might want to do is to either fork or monkey-patch it and replace the
tsquery
function with something more sophisticated that understands "exact phrases" and puts in &s only when there's not an | or some other symbol in there.We also have the question of whether to sort search results by date any more than we already do.
In any case, this is here so my research doesn't get lost and we remember to get back to this eventually.
The text was updated successfully, but these errors were encountered: