[MDEV-32589] FULL_NODUP mode for binlog_row_image Created: 2023-10-26  Updated: 2024-01-18  Resolved: 2024-01-18

Status: Closed
Project: MariaDB Server
Component/s: Replication
Fix Version/s: 11.4.1

Type: New Feature Priority: Critical
Reporter: Andrew Hutchings Assignee: Andrew Hutchings
Resolution: Done Votes: 0
Labels: Preview_11.4

Issue Links:
PartOf
Problem/Incident
causes MDEV-33049 Assertion `marked_for_write_or_comput... Closed
Relates
relates to MDEV-32894 mysqlbinlog flashback support binlog_... Closed

 Description   

With FULL_DIFFERENT mode, all columns are included in before image, but only updated columns are included in after image for UPDATE. While all columns are included in the after image for INSERT.

FULL_DIFFERENT is for replacing FULL mode. It includes all data of the before and after image as FULL mode, but it uses less storage, especially in the case that only a few columns are updated.

This Jira is to track the contribution by Alibaba (https://github.com/MariaDB/server/pull/2803)



 Comments   
Comment by Andrew Hutchings [ 2023-10-26 ]

I've given this a first pass, assigned to Andrei to give a second pass.

Comment by Andrei Elkin [ 2023-11-21 ]

The patch was reviewed on GH to approve.

Comment by Andrew Hutchings [ 2023-11-23 ]

Note that with the final version this mode was called FULL_NODUP.

Comment by Andrew Hutchings [ 2023-11-23 ]

Assigned to Elena for testing, please let me know if this is incorrect.

Comment by Roel Van de Paar [ 2023-12-20 ]

ramesh is testing this one in combination with MDEV-32894

Comment by Ramesh Sivaraman [ 2024-01-16 ]

ok to push

Generated at Thu Feb 08 10:32:30 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.