4 ms·
IMHO this seems like building a better apple by making it taste like an orange. This could definitely be useful for storing json from javascript frameworks like
by bramanga 13y ago
IMHO this seems like building a better apple by making it taste like an orange. This could definitely be useful for storing json from javascript frameworks like backbone/angular/ember, but I don't see how this is going to improve the lives of PostgreSQL users in general. Hopefully this leads to some weird cool emergent use case that make PostgreSQL way better than other databases, but I'm not sure at this point that it will. Does anybody have more context on the long-game for this approach? I'm not sure what the goal is for adding this feature.
- garenp 13y agoLook at some of the linked PDFs. It's the indexing technique and on-disk format that is an enabler for several notable use cases; personally, I'm looking forward to a time when I can use pg for full-text search without having to resort to another external system like Lucene or Sphinx. What it won't have is the query "smarts" like Lucene or Sphinx do today, but you need speed first.
- baudehlo 13y agoPg's built in full text search works amazingly well and has all the smarts. It's also faster than lucene.
- rpedela 13y agoHuh? Please come up with about ten references (one isn't enough) to back up those claims.
- jeltz 13y agoI do not think so, but it might be after the GIN optimization work is committed. After it they beat Sphinx in several benchmarks. http://www.sai.msu.su/~megera/postgres/talks/Next%20generation%20of%20GIN.pdf http://www.sai.msu.su/~megera/postgres/talks/Next%20generati...
- baudehlo 13y agoI didn't say it was faster than sphinx (yet) but it is definitely faster than lucene in all the benchmarks I've thrown at it.
- mml 13y agoI'm very excited to put my 3m documents into hstore, as they are currently in a horrible, unqueryable, unwritable (mostly) blobs of compressed, b64encoded serialized ruby hash structures (long story, predating nosql). This makes me very, very happy. Edit: I should point out why: -my document structures pretty much match 1:1 with hstore now (we have nested arrays of hashes) -i can query & report on the data with normal tools -i can update individual fields on my data (currently impossible) -i can do relational joins & such-like in the db (currently impossible) -i can have sensible transactions