From: | TAKATSUKA Haruka <harukat(at)sraoss(dot)co(dot)jp> |
---|---|
To: | Michael Paquier <michael(at)paquier(dot)xyz> |
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:57:37 |
Message-ID: | 20180928125737.7d1456212db975767fb292e3@sraoss.co.jp |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Thanks for your PostgreSQL work!
Haruka Takatsuka
On Fri, 28 Sep 2018 12:02:08 +0900
Michael Paquier <michael(at)paquier(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Thomas Crayford | 2018-09-28 12:02:42 | Re: "could not open file "pg_wal/…": No such file or directory" potential crashing bug due to race condition between restartpoint and recovery |
Previous Message | Michael Paquier | 2018-09-28 03:32:43 | Re: BUG #15402: Hot standby server with archive_mode=on keeps initial WAL segments |