Fix infinite wait when reading a partially written WAL record If a crash occurs while writing a WAL record that spans multiple pages, the recovery process marks the page with the XLP_FIRST_IS_OVERWRITE_CONTRECORD flag. However, logical decoding currently attempts to read the full WAL record based on its expected size before checking this flag, which can lead to an infinite wait if the remaining data is never written (e.g., no activity after crash).
This patch updates the logic first to read the page header and check for the XLP_FIRST_IS_OVERWRITE_CONTRECORD flag before attempting to reconstruct the full WAL record. If the flag is set, decoding correctly identifies the record as incomplete and avoids waiting for WAL data that will never arrive. Discussion: https://postgr.es/m/CAAKRu_ZCOzQpEumLFgG_%2Biw3FTa%2BhJ4SRpxzaQBYxxM_ZAzWcA%40mail.gmail.com Discussion: https://postgr.es/m/CALDaNm34m36PDHzsU_GdcNXU0gLTfFY5rzh9GSQv%3Dw6B%2BQVNRQ%40mail.gmail.com Author: Vignesh C <vignes...@gmail.com> Reviewed-by: Hayato Kuroda <kuroda.hay...@fujitsu.com> Reviewed-by: Dilip Kumar <dilipbal...@gmail.com> Reviewed-by: Michael Paquier <mich...@paquier.xyz> Reviewed-by: Alexander Korotkov <aekorot...@gmail.com> Backpatch-through: 13 Branch ------ master Details ------- https://git.postgresql.org/pg/commitdiff/d3917d8f13e725a3ae3be8a1c051e677ac6e3334 Modified Files -------------- src/backend/access/transam/xlogreader.c | 20 +++++++++++++++----- 1 file changed, 15 insertions(+), 5 deletions(-)
