Re: BUG #15402: Hot standby server with archive_mode=on keeps initial WAL segments

TAKATSUKA Haruka <harukat@sraoss.co.jp>

From: TAKATSUKA Haruka <harukat@sraoss.co.jp>
To: Michael Paquier <michael@paquier.xyz>
Cc: pgsql-bugs@lists.postgresql.org
Date: 2018-09-28T03:57:37Z
Lists: 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



Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →
  1. Fix WAL recycling on standbys depending on archive_mode