PostgreSQL is Engine Yard's New Default
engineyard.com
PostgreSQL is Engine Yard's New Default
1–10 of 21 posts
Re: PostgreSQL is Engine Yard's New Default
#2Awesome. Given that their services look Ruby-centric, maybe they could take over PL/Ruby and point out that this would allow people to write their stored procs in Ruby too.
Re: PostgreSQL is Engine Yard's New Default
#3Does anybody know how Postgres' fulltext search capabilities/performance compare to using something like ElasticSearch?
Re: PostgreSQL is Engine Yard's New Default
#4PostgreSQL is amazing, that is all.
Re: PostgreSQL is Engine Yard's New Default
#5Does anybody know how Postgres' fulltext search capabilities/performance compare to using something like ElasticSearch?
Postgresql is nowhere, NOWHERE near as powerful or as fast, but it'll work for the cases where you're doing simple search-interface bolt-ons to an existing product already using PGSQL.
Postgresql fulltext and ElasticSearch are ultimately solving two very different sorts of problems.
The only case I can think of where you would prefer to use PGSQL is if you some weird blending of normal relational data with the documents, but I think realistically you can sidestep that. We've been able to do pretty complicated queries against our ElasticSearch instances.
Re: PostgreSQL is Engine Yard's New Default
#6Does anybody know how Postgres' fulltext search capabilities/performance compare to using something like ElasticSearch?
From what I know its better than MySQL's full text and all its warts, but still not comparable to a lucene based search solution.
Re: PostgreSQL is Engine Yard's New Default
#7Does anybody know how Postgres' fulltext search capabilities/performance compare to using something like ElasticSearch?
The main problem is that it's a major PITA to sync a db and an external search service. So it's nice to have FTS built-in
Re: PostgreSQL is Engine Yard's New Default
#8After like an entire year (duh) I figured out how to have InnoDB transactions with MyISAM full-text search...
InnoDB master. MyISAM slaves.
Re: PostgreSQL is Engine Yard's New Default
#9Does anybody know how Postgres' fulltext search capabilities/performance compare to using something like ElasticSearch?
Postgresql cannot be fast as Lucene because of its not a "search engine". Postgresql full-text is fast enough for most cases but it doesn't have support for facet queries which is important for a search engine.
Re: PostgreSQL is Engine Yard's New Default
#10Does anybody know how Postgres' fulltext search capabilities/performance compare to using something like ElasticSearch?
Postgresql cannot be fast as Lucene because of its not a "search engine". Postgresql full-text is fast enough for most cases but it doesn't have support for facet queries which is important for a search engine.
[deleted]