Re: Changing WAL Header to reduce contention duringReserveXLogInsertLocation()

Поиск
Список
Период
Сортировка
От Michael Paquier
Тема Re: Changing WAL Header to reduce contention duringReserveXLogInsertLocation()
Дата
Msg-id 20180328022743.GH1105@paquier.xyz
обсуждение исходный текст
Ответ на Re: Changing WAL Header to reduce contention during ReserveXLogInsertLocation()  (Robert Haas <robertmhaas@gmail.com>)
Ответы Re: Changing WAL Header to reduce contention during ReserveXLogInsertLocation()  (Andrew Dunstan <andrew.dunstan@2ndquadrant.com>)
Список pgsql-hackers
On Tue, Mar 27, 2018 at 10:09:59PM -0400, Robert Haas wrote:
>> I have to agree with Tom here.  If you force pg_rewind to replay more
>> WAL records from a checkpoint older than the checkpoint prior to where
>> WAL has forked at promotion then you have a risk of losing data.
>
> Oh!  I see now.  Good point.

Something that would address the issue would be to enforce a segment
switch after each checkpoint, but that's a high price to pay on mostly
idle systems with large WAL segments, which is not appealing either, and
this even if the checkpoint skip logic has been fixed in v10 with the
concept of "important" WAL records.
--
Michael

Вложения

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

Предыдущее
От: Michael Paquier
Дата:
Сообщение: Re: [bug fix] pg_rewind creates corrupt WAL files, and the standbycannot catch up the primary
Следующее
От: Michael Paquier
Дата:
Сообщение: Re: Cast jsonb to numeric, int, float, bool