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

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: pgsql: Ensure that a standby is able to follow a primary on a newer tim
Дата
Msg-id 1370181.1610601781@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Re: pgsql: Ensure that a standby is able to follow a primary on a newer tim  (Fujii Masao <masao.fujii@oss.nttdata.com>)
Ответы Re: pgsql: Ensure that a standby is able to follow a primary on a newer tim
Список pgsql-committers
Fujii Masao <masao.fujii@oss.nttdata.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



В списке pgsql-committers по дате отправления:

Предыдущее
От: Fujii Masao
Дата:
Сообщение: Re: pgsql: Ensure that a standby is able to follow a primary on a newer tim
Следующее
От: Thomas Munro
Дата:
Сообщение: pgsql: Minor header cleanup for the new iovec code.