| From: | Alyona Vinter <dlaaren8(at)gmail(dot)com> |
|---|---|
| To: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Timeline switching with partial WAL records can break replica recovery |
| Date: | 2025-09-03 05:37:18 |
| Message-ID: | CAGWv16L-ofAYPQvzCo6PG-faNqU54FmmP=SJEFxM1gAQn+Dh7w@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi hackers,
I've found an error in my previous patch and have attached a fixed version.
I'd also like to clarify the timeline switching bug scenario that this
patch fixes:
The issue occurs in this cluster configuration:
[ master ] → [ cascade replica ] → [ replica ]
When the master is lost and the cascade replica is promoted (as described
above), the downstream replica may enter an infinite loop during recovery
instead of properly following the new timeline.
--
Regards,
Alyona Vinter
>
| Attachment | Content-Type | Size |
|---|---|---|
| v2-0002-FIX-Removed-assertion-in-walsummarizer.patch | text/x-patch | 1.2 KB |
| v2-0001-FIX-Handle-WAL-timeline-switches-with-incomplete-records.patch | text/x-patch | 10.1 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alyona Vinter | 2025-09-03 05:39:43 | Re: Timeline switching with partial WAL records can break replica recovery |
| Previous Message | shveta malik | 2025-09-03 04:19:21 | Re: Conflict detection for update_deleted in logical replication |