Re:Postgres full text search is good enough
by rom16384 on Monday September 29, 2014 @05:06AM
(#8382136)
At least for our use case Postgres full text search wasn't good enough. Indexing and searching 1M records was troublesome, and its advanced queries weren't as flexible as we'd like, so after a while we started using Solr, and while it was better it still had its share of problems, so we are currently using ElasticSearch.
[ Parent
| on HN ]
Re:Postgres full text search is good enough
by mctx on Monday September 29, 2014 @05:16AM
(#8382154)
I've gone down the same route, from PostgreSQL search to ElasticSearch with usually pretty good results. A friend has strongly recommended Algolia, so I'll explore that for the next project that needs it.
Re:Postgres full text search is good enough
by sanderjd on Monday September 29, 2014 @02:39PM
(#8384396)
Hmm, was it "troublesome" in terms of performance building the index or doing the search or was there some other issue?
Re:Postgres full text search is good enough
by rom16384 on Monday September 29, 2014 @04:54PM
(#8385241)
Part of the problem was due to the Django package we used to interface with the Postgres search, it wasn't designed to handle large tables. I don't recall how long the index took to build (hours? a day?), but the queries themselves were slow due to their complexity and ranking using ts_rank.