Re: If SyncRepWaitForLSN() fails, would the postgres backend do a roll-back?

From: Tatsuo Ishii <ishii(at)postgresql(dot)org>
To: ruihaij(at)gmail(dot)com
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: If SyncRepWaitForLSN() fails, would the postgres backend do a roll-back?
Date: 2016-06-08 10:43:56
Message-ID: 20160608.194356.2193217335998729028.t-ishii@sraoss.co.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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?

I don't think the backend would roll back the transaction because when
SyncRepWaitForLSN() is called, the transaction has been already
committed. There's no way to roll back a transaction which has been
committed.

Best regards,
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese:http://www.sraoss.co.jp

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Thom Brown 2016-06-08 11:41:01 Re: gettimeofday is at the end of its usefulness?
Previous Message Rui Hai Jiang 2016-06-08 09:53:27 If SyncRepWaitForLSN() fails, would the postgres backend do a roll-back?