Date: Mon, 15 Jun 2020 16:35:11 +0530
From: Manojkumar S <manojkumar.krishnamurthy@zohocorp.com>
To: "pgsql-novice" <pgsql-novice@postgresql.org>
Cc: "Srivathson KK" <srivathson.k@zohocorp.com>
Message-Id: <172b7a791bd.121388bfb22150.5969883832378040935@zohocorp.com>
In-Reply-To: 
Subject: ".partial" WAL file missing while promoting database in streaming
 replication.
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_78693_1816060714.1592219111870"
Importance: Medium
User-Agent: Zoho Mail
Precedence: bulk

------=_Part_78693_1816060714.1592219111870
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit

Hello,


OS : Windows and Linux

Version : 10.7 and 11.7

Topic : Streaming Replication


I use streaming replication in async mode. When master gets down, slave will be promoted using a trigger file. During this process, a ".partial" file
 will be created and a WAL file with the same ID will be created in a 
different timeline in slave (to be promoted as master). When master comes back as slave, it will be synced to the current master. This is 
the normal procedure as far as I understood. 


But in some cases, ".partial" file is not getting created and peer DB which comes back as slave is unable to sync whenever this happens.. So, basically databases go out of sync when the ".partial" file is not 
created . Please suggest if this happens in any scenario and how to 
overcome this. 


Thanks and Regards,

Manoj Kumar.
------=_Part_78693_1816060714.1592219111870
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"><html><head><meta content="text/html;charset=UTF-8" http-equiv="Content-Type"></head><body ><div style="font-family: Verdana, Arial, Helvetica, sans-serif; font-size: 10pt;"><div>Hello,<br></div><div><br></div><div>OS : Windows and Linux<br></div><div>Version : 10.7 and 11.7<br></div><div>Topic : Streaming Replication<br></div><div><br></div><div><div>I use streaming replication in async mode. When master gets down, slave will be promoted using a trigger file. During this process, a ".partial" file
 will be created and a WAL file with the same ID will be created in a 
different timeline in slave (to be promoted as master). When master comes back as slave, it will be synced to the current master. This is 
the normal procedure as far as I understood. <br></div><div><br></div><div>But in some cases, ".partial" file is not getting created and peer DB which comes back as slave is unable to sync whenever this happens.. So, basically databases go out of sync when the ".partial" file is not 
created . Please suggest if this happens in any scenario and how to 
overcome this. <br></div><div><br></div></div><div>Thanks and Regards,<br></div><div>Manoj Kumar.<div class="yj6qo"><br></div><div class="adL"><br></div></div><div><br></div></div><br></body></html>
------=_Part_78693_1816060714.1592219111870--