An object-relational database system that boasts a vast set of features and a growing community. Complete with a solid architecture that has made it one of the more popular options, it provides reliability, data integrity, and correctness across the database.
Ranked in these QuestionsQuestion Ranking
Pro Open Source
Built by passionate developers, available for free, and is well supported by its active community.
Pro JSON support
JSON support allows for Postgres to transfer data as raw text and without attributes and markup overhead. This will result in new levels of speed, efficiency and flexibility for developers.
Pro Highly scalable
Continues to work well under low or heavy loads in order to meet the users' need.
Pro True ACID-compliance
Built in, so users won't have to worry about atomicity, consistency, isolation and the durability of the database.
Pro Multi-Version Concurrency Control (MVCC)
Postgres uses MVCC. For each user connected to the database the Postgres database shows a snapshot of the database at a particular instance. When the database needs to update an item it will add the newer version and mark the old version as obsolete. This allows the database to save overhead but requires a regulated sweep to delete the old, obsolete data.
Pro Multiple Language Interfaces
"There are interfaces for Java (JDBC), ODBC, Perl, Python, Ruby, C, C++, PHP, Lisp, Scheme, and Qt just to name a few."
Pro Supports migration from other major proprietary and open source databases
With the extensive SQL support and migration tools, Postgres users are easily able to migrate their databases over to the Postgres database with little effort.
Pro Object-Oriented Database
You can reuse existing approved design table and extend its capability by inheritance. You can reuse ancestor method byy declaring new trigger for descendant but reuse ancestor trigger procedure. You can add, remove or override column constraint making it differ from its ancestor. Applying OOP with database design help me reuse, extend, and encapsulate business logic and end up a rapid design, and less errants. PostgreSQL is a powerful RDBMS while its OOP is sufficient for OOP modular design. Especially its Open Source ,and free.
Pro Great query planner
Unlike MySQL, you generally don't spend time on hinting the query planner in order to make PostGres perform well.
Pro RETURNING option on INSERT queries
INSERT INTO table (field_1, field_2, field_3) VALUES (value_1, value_2, value_3) RETURNING id;
Con Vaccuuming can cause headaches
Con Overkill for simple setups
If a database will be doing many simple operations Postgres may be over-kill.