You're right. I think in general the quorum commit in Postgres is a bit lower level, in the sense that it is less opinionated and allows you to configure the quorum (essentially enabling both semisync and synchronous).
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.
That's not what semi-sync does. Semi-sync commits the write to the master and then blocks on returning a result to the client until N replicas have received a write OR a timeout is reached. There is no ability to roll back the write on the master once it is committed.
[1] https://git.postgresql.org/gitweb/?p=postgresql.git;a=commit...