Re: Standby recovers records from wrong timeline

Поиск
Список
Период
Сортировка
От Kyotaro Horiguchi
Тема Re: Standby recovers records from wrong timeline
Дата
Msg-id 20221021.174440.1955006618825535186.horikyota.ntt@gmail.com
обсуждение исходный текст
Ответ на Re: Standby recovers records from wrong timeline  (Kyotaro Horiguchi <horikyota.ntt@gmail.com>)
Ответы Re: Standby recovers records from wrong timeline  (Kyotaro Horiguchi <horikyota.ntt@gmail.com>)
Re: Standby recovers records from wrong timeline  (Ants Aasma <ants@cybertec.at>)
Список pgsql-hackers
At Fri, 21 Oct 2022 17:12:45 +0900 (JST), Kyotaro Horiguchi <horikyota.ntt@gmail.com> wrote in 
> latest works. It dones't consider the case of explict target timlines
> so it's just a PoC.  (So this doesn't work if recovery_target_timeline
> is set to 2 for the "standby" in the repro.)

So, finally I noticed that the function XLogFileReadAnyTLI is not
needed at all if we are going this direction.

Regardless of recvoery_target_timeline is latest or any explicit
imeline id or checkpoint timeline, what we can do to reach the target
timline is just to follow the history file's direction.

If segments are partly gone while reading on a timeline, a segment on
the older timelines is just a crap since it should be incompatible.

So.. I'm at a loss about what the function is for.

Please anyone tell me why do we need the behavior of
XLogFileReadAnyTLI() at all?

regards.

-- 
Kyotaro Horiguchi
NTT Open Source Software Center



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

Предыдущее
От: davinder singh
Дата:
Сообщение: Re: cross-platform pg_basebackup
Следующее
От: Kyotaro Horiguchi
Дата:
Сообщение: Re: fix stats_fetch_consistency value in postgresql.conf.sample