I'm trying to wrap my head around Postgres' asynchronous replication. The way I'm reading the documentation, if the master goes down after data was committed, but before it's shipped to slaves, the slaves will never get that data (even after the master goes back up).
This, as I understand it, is different than MySQL's async replication, where the master resumes syncing it's binary log once it's brought back up (without any data loss).
Seems a bit crazy to me, so I wanted to make sure I was reading the docs properly.
To be clear, I'm not talking about data loss resulting in electing one of the slaves as the new master. Simply data loss with respect to the master going down before the WAL is shipped and it not being shipped once the master comes back up.