[1] https://git.postgresql.org/gitweb/?p=postgresql.git;a=commit...
[1] https://git.postgresql.org/gitweb/?p=postgresql.git;a=commit...
There is semi-sync in MySQL as well, which ensures N replicas have received a write.
https://dev.mysql.com/doc/refman/5.7/en/server-system-variab...
You could ask the database to "COMMIT"; it receives the command and processes it, but does not manage to send you notification that it has managed.
There is a further failure state:
The master could be behind when it crashed. So you need to look at it's gtid executed set or re-image it before plugging it back in.
(Not a distributed systems guy; I work on the non HA+replication parts of the server)
Also, as sibling points out, semisync in MySQL seems to commit on the master first no matter what, while in PG quorum commit, no one commits until the required acks are received.