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

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: TAKATSUKA Haruka <harukat(at)sraoss(dot)co(dot)jp>
Cc: pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #15402: Hot standby server with archive_mode=on keeps initial WAL segments
Date: 2018-09-28 03:02:08
Message-ID: 20180928030208.GC1500@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

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

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message TAKATSUKA Haruka 2018-09-28 03:20:03 Re: BUG #15402: Hot standby server with archive_mode=on keeps initial WAL segments
Previous Message Tom Lane 2018-09-27 20:15:32 Re: BUG #15408: Postgresql bad planning with multicolumn gist and search with empty results