Re: base backup vs. concurrent truncation

Поиск
Список
Период
Сортировка
От Aleksander Alekseev
Тема Re: base backup vs. concurrent truncation
Дата
Msg-id CAJ7c6TP-=S6D=uvYre_x7ZCfHKH+n1MOAAMB6R4vVcn7piSjBA@mail.gmail.com
обсуждение исходный текст
Ответ на base backup vs. concurrent truncation  (Robert Haas <robertmhaas@gmail.com>)
Ответы Re: base backup vs. concurrent truncation  (Aleksander Alekseev <aleksander@timescale.com>)
Список pgsql-hackers
Hi,

Just a quick observation:

> basebackup.c's theory about relation truncation is that it doesn't
> really matter because WAL replay will fix things up. But in this case,
> I don't think it will, because WAL replay relies on the above
> invariant holding.

Assuming this is the case perhaps we can reduce the scenario and
consider this simpler one:

1. The table is truncated
2. The DBMS is killed before making a checkpoint
3. We are in recovery and presumably see a pair of 0.5 Gb segments

Or can't we?

-- 
Best regards,
Aleksander Alekseev



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

Предыдущее
От: Robert Haas
Дата:
Сообщение: Re: Minor code de-duplication in fe-connect.c
Следующее
От: Aleksander Alekseev
Дата:
Сообщение: Re: base backup vs. concurrent truncation