Why not read its extensive documentation (<a href="http:&#x2F;&#x2F;www.postgresql.org&#x2F;docs&#x2F;9.5&#x2F;static&#x2F;" rel="nofollow">http:&#x2F;&#x2F;www.postgresql.org&#x2F;docs&#x2F;9.5&#x2F;static&#x2F;</a>), evaluate its capabilities vs. those of MongoDB with respect to your particular use case and decide for yourself?<p>SQL has never ever been meant for &quot;editing documents&quot;, doing so is certainly not considered &quot;basic functionality&quot; for anyone whose use case is best served by a RDBMS, and you&#x27;ll likely be displeased by the performance of such in Postgres (or any other RDBMS) if that is something you consider &quot;basic functionality&quot;.<p>(FWIW: what I&#x27;ve found to be the typical use case of JSON-in-SQL (or XML-in-SQL) is that of storing opaque JSON or XML blobs generated by some external service, which could perhaps benefit from indexed lookups within this data.  If you&#x27;re designing your main SQL database around JSON you&#x27;re probably doing something wrong.)