| From: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
|---|---|
| To: | kehan5800(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #19774: Incremental backup loses re-extended blocks when WAL summaries are merged out of LSN order |
| Date: | 2026-10-21 08:17:30 |
| Message-ID: | CAHGQGwHkXH7-O9x8TY0Bp-MGhg5qwFnbF0grPi85_09Do-6xGQ@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Tue, Oct 20, 2026 at 8:56 PM PG Bug reporting form
<noreply(at)postgresql(dot)org> wrote:
> Sorting
> the list before the merge fixes this.
Thanks for the report and patch!
Attached is an updated patch that retains your fix, makes minor naming and
comment changes, and adds a TAP test. The test truncates a table before
promoting a standby, re-extends it afterward, and verifies the restored data.
Using different timelines makes the test independent of directory
enumeration order.
Seems this should be backpatched to v17.
Regards,
--
Fujii Masao
| Attachment | Content-Type | Size |
|---|---|---|
| v1-0001-Fix-incremental-backup-data-loss-due-to-WAL-summa.patch | application/octet-stream | 7.0 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nitin Motiani | 2026-10-21 08:34:57 | Re: BUG #19770: CREATE TABLE (LIKE ...) PARTITION BY copies a NO INHERIT not-null constraint; NULLs then go into par |
| Previous Message | Michael Paquier | 2026-10-21 07:12:42 | Re: BUG #19760: CLUSTER loses a row the transaction inserted and then updated in a rolled-back subtransaction |