If SyncRepWaitForLSN() fails, would the postgres backend do a roll-back? - Mailing list pgsql-hackers

From Rui Hai Jiang
Subject If SyncRepWaitForLSN() fails, would the postgres backend do a roll-back?
Date
Msg-id CAEri+mL3JcGNfPOSJNZLLoRbzrANheugGVCK+fw-NiQ-=SboiA@mail.gmail.com
Whole thread Raw
Responses Re: If SyncRepWaitForLSN() fails, would the postgres backend do a roll-back?  (Tatsuo Ishii <ishii@postgresql.org>)
List pgsql-hackers
Hi,

I'm researching the synchronous replication. I see the backend of the Primary Server calls SyncRepWaitForLSN() to wait for the Standby Server to write the WAL records.

If some thing happens, such as network failure or disk failure, causes the Standby Server fail to receive WAL records or fail to write WAL records, would the backend of the Primary Server catch and handle this failure? Would the backend roll-back the transactions? Would the backend continue to work?

If the transactions at the Primary Server need rollback, I think SyncRepWaitForLSN() should return some information to the backend.

Thank you,
Rui Hai 

pgsql-hackers by date:

Previous
From: Kyotaro HORIGUCHI
Date:
Subject: Re: Rename synchronous_standby_names?
Next
From: Tatsuo Ishii
Date:
Subject: Re: If SyncRepWaitForLSN() fails, would the postgres backend do a roll-back?