mirror of
https://git.postgresql.org/git/postgresql.git
synced 2024-10-04 08:16:58 +02:00
e3fb6170e5
WAL records may span multiple segments, but XLogWrite() does not wait for the entire record to be written out to disk before creating archive status files. Instead, as soon as the last WAL page of the segment is written, the archive status file is created, and the archiver may process it. If PostgreSQL crashes before it is able to write and flush the rest of the record (in the next WAL segment), the wrong version of the first segment file lingers in the archive, which causes operations such as point-in-time restores to fail. To fix this, keep track of records that span across segments and ensure that segments are only marked ready-for-archival once such records have been completely written to disk. This has always been wrong, so backpatch all the way back. Author: Nathan Bossart <bossartn@amazon.com> Reviewed-by: Kyotaro Horiguchi <horikyota.ntt@gmail.com> Reviewed-by: Ryo Matsumura <matsumura.ryo@fujitsu.com> Reviewed-by: Andrey Borodin <x4mmm@yandex-team.ru> Discussion: https://postgr.es/m/CBDDFA01-6E40-46BB-9F98-9340F4379505@amazon.com |
||
|---|---|---|
| .. | ||
| autovacuum.c | ||
| bgworker.c | ||
| bgwriter.c | ||
| checkpointer.c | ||
| fork_process.c | ||
| interrupt.c | ||
| Makefile | ||
| pgarch.c | ||
| pgstat.c | ||
| postmaster.c | ||
| startup.c | ||
| syslogger.c | ||
| walwriter.c | ||