We're currently working on issues that are blocking Drupal 8 installation on postgresql. Please stop by the issue queue and tell us your opinion:
#2001350: Drupal 8 cannot be installed on Postgresql
The current issue summarized by Damien:
I suspect that we are hitting this now because PostgreSQL recently (in version 9, if I remember correctly) got support for transactional DDL. As a consequence the DDL statements that previously caused the previous (aborted) transaction to be cleared out do not anymore.
We should turn to PostgreSQL users. Given that PDO supports multi-statement queries, inserting a SAVEPOINT before every query will not have an impact on latency, which is a good thing, but might have an impact on the performance of execution of queries in general.
Note that adding a SAVEPOINT is what the psql command line tool does when ON_ERROR_ROLLBACK is enabled:
The on_error_rollback-on mode works by issuing an implicit SAVEPOINT for you, just before each command that is in a transaction block, and rolls back to the savepoint on error.
There are also smaller issues here and there that effect both postgresql and sqlite.
Please post comments directly on the issue queue and not here.