Re: pgsql: Ensure that a standby is able to follow a primary on a newer tim

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com>
Cc: Michael Paquier <michael(at)paquier(dot)xyz>, Fujii Masao <fujii(at)postgresql(dot)org>, pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: Re: pgsql: Ensure that a standby is able to follow a primary on a newer tim
Date: 2021-01-14 05:23:01
Message-ID: 1370181.1610601781@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com> writes:
> On 2021/01/14 13:59, Michael Paquier wrote:
>> florican is telling that this test has some stability problems:
>> https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=florican&dt=2021-01-14%2003%3A55%3A45

> My guess is that the requested WAL file was removed unfortunately by
> checkpoint because no replication slot is used and wal_keep_size is not set.
> So easy fix is to set wal_keep_size to 512MB or other in that test. Thought?

florican did pass this test on the v13 branch, so I agree it's probably
a timing issue not any deeper bug. Your theory seems plausible.

regards, tom lane

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Thomas Munro 2021-01-14 05:32:10 pgsql: Minor header cleanup for the new iovec code.
Previous Message Fujii Masao 2021-01-14 05:14:11 Re: pgsql: Ensure that a standby is able to follow a primary on a newer tim