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

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: harukat(at)sraoss(dot)co(dot)jp, 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-26 03:52:05
Message-ID: 20180926035205.GJ1659@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Wed, Sep 26, 2018 at 03:26:50AM +0000, PG Bug reporting form wrote:
> A hot standby server with “archive_mode = on” keeps initial WAL segment
> files that copied by pg_basebackup. It shows the following status.
> 000000010000000000000042 will be kept forever in this case.

How did you find yourself in this situation? Did you take a base backup
from a primary which had .ready files in it, and those got copied to the
standby's data folder? We may want to study the possibility of
filtering things when taking a base backup instead.

> Though I understand renaming the .ready to .done manually can clean it,
> I would like to fix the server code like the following patch.
> I'd appreciate if you would consider that.

Your patch looks incorrect to me to begin with... What if archive_mode
is switched from "on" to "always" back-and-forth and there some of the
past segments which should be archived are not?
--
Michael

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message TAKATSUKA Haruka 2018-09-26 04:36:40 Re: BUG #15402: Hot standby server with archive_mode=on keeps initial WAL segments
Previous Message PG Bug reporting form 2018-09-26 03:26:50 BUG #15402: Hot standby server with archive_mode=on keeps initial WAL segments