Re: prevent immature WAL streaming
От | Andres Freund |
---|---|
Тема | Re: prevent immature WAL streaming |
Дата | |
Msg-id | 20210901170052.4iz3iilihqkad4ui@alap3.anarazel.de обсуждение исходный текст |
Ответ на | Re: prevent immature WAL streaming (Fujii Masao <masao.fujii@oss.nttdata.com>) |
Ответы |
Re: prevent immature WAL streaming
|
Список | pgsql-hackers |
Hi, On 2021-09-01 15:01:43 +0900, Fujii Masao wrote: > Thanks for clarifying that! Unless I misunderstand that, when recovery ends > at a partially-flushed segment-spanning record, it sets > XLP_FIRST_IS_ABORTED_PARTIAL in the next segment before starting writing > new WAL data there. Therefore XLP_FIRST_IS_CONTRECORD or > XLP_FIRST_IS_ABORTED_PARTIAL must be set in the next segment following > a partially-flushed segment-spanning record. If none of them is set, > the validation code in recovery should report an error. Right. With the small addition that I think we shouldn't just do this for segment spanning records, but for all records spanning pages. Greetings, Andres Freund
В списке pgsql-hackers по дате отправления: