Use XLogRecPtrIsValid() consistently for WAL position checks
Fujii Masao <fujii@postgresql.org>
Use XLogRecPtrIsValid() consistently for WAL position checks Commit a2b02293bc6 switched various checks to use XLogRecPtrIsValid(), but later changes reintroduced XLogRecPtrIsInvalid() and direct comparisons with InvalidXLogRecPtr. This commit replaces those uses with XLogRecPtrIsValid() for better readability and consistency. Author: Vignesh C <vignesh21@gmail.com> Reviewed-by: Xiaopeng Wang <wxp_728@163.com> Reviewed-by: Amul Sul <sulamul@gmail.com> Reviewed-by: Fujii Masao <masao.fujii@gmail.com> Discussion: https://postgr.es/m/CALDaNm16knMFtcqyAG3XYSkyagmVXfhaR0T=hau8UTAU0+eLQQ@mail.gmail.com
Files
| Path | Change | +/− |
|---|---|---|
| src/backend/commands/repack_worker.c | modified | +1 −1 |
| src/backend/replication/walreceiver.c | modified | +2 −2 |
| src/bin/pg_waldump/archive_waldump.c | modified | +2 −2 |
Discussion
- Use XLogRecPtrIsValid() instead of negated XLogRecPtrIsInvalid 9 messages · 2026-04-10 → 2026-04-16