The patchset in question is an improvement of hstore[0] (typed hstore, nested hstore) and unification of json and hstore (by using the binary hstore format for both). There is no more detriment to the relational core than when hstore or XML were originally added. Also, next-GIN[1] by the same people[2], not sure it's part of the patch mentioned.
[0] [PDF warning] http://www.sai.msu.su/~megera/postgres/talks/hstore-dublin-2...
[1] [PDF warning] http://www.sai.msu.su/~megera/postgres/talks/Next%20generati...
[2] Who previously contributed GiST and GIN, FTS, ltree or intarray
https://commitfest.postgresql.org/action/patch_view?id=1357 https://commitfest.postgresql.org/action/patch_view?id=1382
Yes, and it will. In fact the best post-relational features of PostgreSQL work best when used in a relational way.
> While I don't mind seeing some non relational additions like JSON, it shouldn't be detrimental to Postgres relational core.
As I usually tell people "Good object-relational design is usually good object-oriented design and good relational design, and that makes it really, really hard."
> It's not a pissing contest : if MongoDB is more popular than Postgres for non relational (NoSql) data so what ?
I would agree. The fact is that for the last 10 years, PostgreSQL has been the choice of open source rdbms's in business apps for the last 12 years and I don't see that changing.
> It's not like Postgres is a commercial product and need wider adoption to keep the parent company afloat.
Mindshare is important though.
While I don't mind seeing some non relational additions like JSON, it shouldn't be detrimental to Postgres relational core.
It's not a pissing contest : if MongoDB is more popular than Postgres for non relational (NoSql) data so what ?
It's not like Postgres is a commercial product and need wider adoption to keep the parent company afloat.