-
Notifications
You must be signed in to change notification settings - Fork 367
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
multisearch slow #209
Comments
+1 |
I'm Having a similar issue, did you guys found the root cause? Or any optimization/workaround? Thx! |
Did you guys find a solution? |
I'm having a similar issue |
I ended up switching search to a Elasticsearch instance |
Had to do the same |
I'm wondering if there's a particular reason that the |
I am not using pg_search yet, but I was looking at the migration it created and wondering exactly the same thing. |
Not all pg_search scopes use That said, using a |
Struggling to get multisearch to work in a timely manner. I have approx 60k rows to search across, and results are taking 7-10 seconds.
My models look like:
My dev log shows:
Why a simple count query is taking 4 seconds is beyond me. I've also tried storing the searchable data in a tsv_vector column as mentioned in https://github.com/Casecommons/pg_search/wiki/Building-indexes but it made no difference. Can anyone help point me as to what I'm doing wrong?
Thanks
The text was updated successfully, but these errors were encountered: