Re: replication_timeout does not seem to be working

>If no reply is returned from the standby in replication_timeout, the master
thinks
>that the connected standby is inactive, and terminates the replication
connection.
>This is useful for the master to detect a standby crash or network outage.

After that master commit current transaction with "local" synchronous_commit
or rollback?

And why I setup this parameter replication_timeout = 2s and my wal's thread
(on master and server are restarted within 2s)?

--
View this message in context:
http://postgresql.1045698.n5.nabble.com/replication-timeout-does-not-seem-to-be-working-tp4620827p4726014.html
Sent from the PostgreSQL - admin mailing list archive at Nabble.com.