Jeff Davis wrote:
> How does WAL shipping help synchronous replication?
The WAL is written _before_ commit, logging all the changes the
transaction wants to write to the disk. This makes it look very similar
to what is needed for synchronous replication.
Instead of waiting for confirmation from the disk, that your WAL has
been written, you would have to wait from the network to confirm that
the changes have been delivered via the network.
Regards
Markus
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
