3 ms·
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 f
by rom16384 12y ago
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.
- mctx 12y agoI'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.
- sanderjd 12y agoHmm, was it "troublesome" in terms of performance building the index or doing the search or was there some other issue?
- rom16384 12y agoPart 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.
- sanderjd 12y agoInteresting, thanks for the info. What did you switch to? Were the queries significantly faster?