Because you don't have access to the DB directly, many of the built in search solutions aren't available on Heroku. Using built in FTS or things like tsearch will break taps for example, and are not supported. A few people have reports of getting them running, but it's not production quality. If you want to use search on Heroku, websolr is really the way to go.
Oren On Mon, Feb 8, 2010 at 10:21 PM, Mike <[email protected]> wrote: > I noticed that the documentation recommends using Solr for search: > http://docs.heroku.com/full-text-search > > However, Postgres has a built-in full text search capability that is > not discussed at all. I was wondering what the rationale is for the > recommendation of Solr? > > Would the performance offered by a Solr approach be significantly > greater or more scalable than using Postgres' built-in search? > > -- > You received this message because you are subscribed to the Google Groups > "Heroku" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]<heroku%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/heroku?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
