[loopbit]

Sure, if you only need full text search there's no need to use Solr or ElasticSearch.

I've never tried with PostgreSql, but I noticed the same drop in performance in MySql at the 1-2 million documents count, although full text search queries in MySql are slower (from what I remember, I haven't tested in a couple of years).

The power of Solr and other tools out there is all the other stuff you can do, like synonyms processing, faceting, range queries, etc, etc... as well as give you more flexibility on what data you load and how you process it. But if you don't need it, there's no reason to use a different tool.

[s3th]

There's no question that Solr and ElasticSearch have more capability than PostgreSQL alone, but you'd be surprised at what Postgres can do!

It's certainly more than just full text search. Check out this article [1] that talks about Postgres' support for stemming, ranking / boost, multiple languages, fuzzy search, and accent support.

[1] http://blog.lostpropertyhq.com/postgres-full-text-search-is-...

[loopbit]

You are right, I had assumed that it's capabilities were similar to MySql (don't ask me why).

Still, I would describe most of those features as 'basic', as you really need some support for all that to use full-text search in real life and I wonder how easy it is to add/remove stopwords or other tweaks like that.

Anyway, thank you very much for the link, very interesting! I've been looking at PostGIS as an option for a project I'm working on and using PostgreSql as the main db is getting more and more points... Thanks!