PostgreSQL as Schemaless Database [pdf]
wiki.postgresql.org
PostgreSQL as Schemaless Database [pdf]
1–10 of 90 posts
Re: PostgreSQL as Schemaless Database [pdf]
#2When the benchmark shows postgres can do the same as mongo, only faster, then why aren't we seeing more hybrid solutions? Online retailers would be better off using relational storage for monetary transactions and time series, and json storage for document like data.
Re: PostgreSQL as Schemaless Database [pdf]
#3would it be possible to build an extension to expose a mongo compatible interface in postgres - essentially being able to use all the ORM/code built around mongo for postgres, seamlessly.
Re: PostgreSQL as Schemaless Database [pdf]
#4would it be possible to build an extension to expose a mongo compatible interface in postgres - essentially being able to use all the ORM/code built around mongo for postgres, seamlessly.
Yes, I don't think it would even be that difficult if you used plv8js, but it would (probably?) be relatively slow.
Re: PostgreSQL as Schemaless Database [pdf]
#5Well that's Monday's afternoon decided !
Re: PostgreSQL as Schemaless Database [pdf]
#6This is pretty much the reason we're using Postgres for our document storage. Admittedly, our doc store isn't really extensive and it's mostly for internal use (with limited client access), but we just didn't see why it was necessary to go with a new database when the existing stack worked well.
YMMV, but we've yet to come across an instance where a pure document DB was necessary or desired, even to store documents (which from my perspective seems nothing more than a flattened EAV model).
Re: PostgreSQL as Schemaless Database [pdf]
#7When the benchmark shows postgres can do the same as mongo, only faster, then why aren't we seeing more hybrid solutions? Online retailers would be better off using relational storage for monetary transactions and time series, and json storage for document like data.
Maybe sharding?
Re: PostgreSQL as Schemaless Database [pdf]
#8I want to admit that conclusion in presentation can be interpreted vise versa: MongoDB almost is fast as PostgreSQL. Also, notice that comparsion was done with Mongo 2.2, in 2.4 JS engine was changed to V8, so there is a lot of speed improvements. And compare PG have 18 years of development vs 5 of MongoDB. So what I want to say? Difference is not so big after all.
Re: PostgreSQL as Schemaless Database [pdf]
#9This is pretty much the reason we're using Postgres for our document storage. Admittedly, our doc store isn't really extensive and it's mostly for internal use (with limited client access), but we just didn't see why it was necessary to go with a new database when the existing stack worked well. YMMV, but we've yet to come across an instance where a pure document DB was necessary or desired, even to store documents (…
Do you have any thoughts on expression indexes? Assumed I would have to pull out fields from the document to index reasonably on pgsql, but this presentation at least shows that simple expression indexes perform well. I wonder about compound, nested, etc.
Re: PostgreSQL as Schemaless Database [pdf]
#10Where is taligent when we need him? MongoDB is pretty impressive considering its age to the market, but I'd still go with the relational version of PostgreSQL anyday. Not because of the benchmarks, but in general, most use-cases are covered well enough by our relational db's like MySQL and PostgreSQL. The most expensive mistake one could make is using a NoSQL db where an SQL db fits perfectly. I admittedly made this mistake and learnt a LOT. Now, these benchmarks are just some extra spice for sticking with my lovely PostgresSQL :)