| From: | Kirill Reshke <reshkekirill(at)gmail(dot)com> |
|---|---|
| To: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Do not fail WAL buffers read after on-disk xlog removal |
| Date: | 2026-10-24 17:30:19 |
| Message-ID: | CALdSSPg=o=RYYhA+vpd2QbwePwcqS=aTkumy1JV=nPXttGV+og@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sat, 24 Oct 2026 at 22:19, Kirill Reshke <reshkekirill(at)gmail(dot)com> wrote:
>
> Hi,
>
> XLogSendPhysical checks for on-disk xlog removal even when the entire requested
> range was copied from WAL buffers. So this rejects data already available in the
> output buffer and terminates streaming unnecessarily.
>
> Attached checks for xlog files presence only in WAL buffers read failed.
>
> --
> Best regards,
> Kirill Reshke
Also PFA TAP test demonstrating an issue. Not intended to commit
thought. Just show-caseing a bug
--
Best regards,
Kirill Reshke
| Attachment | Content-Type | Size |
|---|---|---|
| 0002-Test-WAL-buffer-reads-after-segment-recycling.patch | application/octet-stream | 6.7 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kirill Reshke | 2026-10-24 17:45:03 | Re: Let physical WAL senders restore missing segments from the archive |
| Previous Message | Kirill Reshke | 2026-10-24 17:19:42 | Do not fail WAL buffers read after on-disk xlog removal |