Re: BUG #15402: Hot standby server with archive_mode=on keepsinitial WAL segments - Mailing list pgsql-bugs

From TAKATSUKA Haruka
Subject Re: BUG #15402: Hot standby server with archive_mode=on keepsinitial WAL segments
Date
Msg-id 20180928125737.7d1456212db975767fb292e3@sraoss.co.jp
Whole thread Raw
In response to Re: BUG #15402: Hot standby server with archive_mode=on keepsinitial WAL segments  (Michael Paquier <michael@paquier.xyz>)
List pgsql-bugs
Thanks for your PostgreSQL work!

Haruka Takatsuka


On Fri, 28 Sep 2018 12:02:08 +0900
Michael Paquier <michael@paquier.xyz> wrote:

> On Thu, Sep 27, 2018 at 01:44:30PM +0900, Michael Paquier wrote:
> > I looked at this problem, and I completely agree.  From what I can see,
> > the restart point run on the standby creates a .ready file for the
> > oldest segment because there were no .done file present in it, so the
> > checkpointer thinks that it should mark the file with .ready, and then
> > makes it ready for archiving, which is never going to happen with
> > archive_mode = on.  All the newer segments are already marked with
> > .done, so they are getting recycled correctly.
> 
> I have spent a couple of hours on this problem, checked the behavior on
> all branches, and committed the fix.  Thanks for the report!
> --
> Michael



pgsql-bugs by date:

Previous
From: Michael Paquier
Date:
Subject: Re: BUG #15402: Hot standby server with archive_mode=on keepsinitial WAL segments
Next
From: Thomas Crayford
Date:
Subject: Re: "could not open file "pg_wal/…": No such file or directory" potential crashing bug due to race condition between restartpoint and recovery