RE: long-standing data loss bug in initial sync of logical replication - Mailing list pgsql-hackers

From Hayato Kuroda (Fujitsu)
Subject RE: long-standing data loss bug in initial sync of logical replication
Date
Msg-id OSCPR01MB149668597B9593D9EFCC5DE68F5DF2@OSCPR01MB14966.jpnprd01.prod.outlook.com
Whole thread Raw
In response to Re: long-standing data loss bug in initial sync of logical replication  (Amit Kapila <amit.kapila16@gmail.com>)
Responses Re: long-standing data loss bug in initial sync of logical replication
RE: long-standing data loss bug in initial sync of logical replication
List pgsql-hackers
Dear Amit,

> IIUC, workloads C and D will have regression in back branches, and
> HEAD will have regression only for workload D. We have avoided
> workload C regression in HEAD via commits 7c99dc587a and 3abe9dc188.

Right.

> We can backpatch those commits if required, but I think it is better
> not to do those as scenarios C and D won't be that common, and we
> should go ahead with the fix as it is. In the future, if we get any
> way to avoid regression due to scenario-D, then we can do that for the
> HEAD branch.

OK, let me share patched for back branches. Mostly the same fix patched as master
can be used for PG14-PG17, like attached. Regarding the PG13, it cannot be applied
as-is thus some adjustments are needed. I will share it in upcoming posts.

Best regards,
Hayato Kuroda
FUJITSU LIMITED


Attachment

pgsql-hackers by date:

Previous
From: Sungwoo Chang
Date:
Subject: Re: dsm_registry: Add detach and destroy features
Next
From: Steven Niu
Date:
Subject: Re: Not-terribly-safe checks for CRC intrinsic support