4 ms·

* transactional DDL * comprehensive transaction model using different modes * PostGIS and lots of other great extensions * supports most of the current SQL s

* transactional DDL * comprehensive transaction model using different modes * PostGIS and lots of other great extensions * supports most of the current SQL standard and is clear on interpretation of edge-cases in the documentation * support for writing stored procedures in any major programming language * many useful functions regarding dates, sets, ranges, json, xml, ... * custom datatypes * extremely thought-out and standardized approach to development: if a feature is included it generally works well in interaction with everything else * syntax, semantics and performance are all very predictable * great documentation Regarding MySQL / MariaDB: MySQL optimized for performance first. Until 2010 the standard-storage-engine MyISAM didn't even support transactions. PostgreSQL always focused on correctness and stability and then made sure everything performed.

arkh 2y ago
> * custom datatypes Good in theory. But last time I checked the main libs to connect to pgsql, everything you get back from the database are strings. So you need something in your app to convert those strings to the equivalent data structures.
- ttfkam 2y ago
  You're thinking only in terms of application. Types in the db save storage space, allow for better validation than plain strings, can be correlated cleanly with other columns with the same type, etc. Yes, more drivers and libraries should support the more expansive data type list, but even just within the database itself there are multiple advantages.