stack/wendelin: add some configurations to make binlog size smaller.
After erp5@567a8364, binlog size is bigger because READ COMMITTED causes statements to be replicated in row-mode.
To make binlog size smaller, here we add some configurations, proposed by @vpelletier.
- binlog_annotate_row_events = OFF
- binlog_row_image= MINIMAL
- log_bin_compress= ON
We can verify the effect of these parameters by checking binlog file like bin/mariadb-binlog --base64-output=DECODE-ROWS -v srv/backup/mariadb-incremental/binlog.xxx
By default, where binlog_annotate_row_events=ON and binlog_row_image=FULL, mariadb-binlog output (with options above) is like
#Q> UPDATE message SET processing_node=1 WHERE uid IN (2987760775610849703)
#260930 14:30:06 server id 3378668469 end_log_pos 0 CRC32 0x8b288462 Table_map: `erp5`.`message` mapped to number 199
# at 4257
#260930 14:30:06 server id 3378668469 end_log_pos 0 CRC32 0x2f935159 Update_compressed_rows: table id 199 flags: STMT_END_F
### UPDATE `erp5`.`message`
### WHERE
### @1=2987760775610849703 /* LONGINT meta=0 nullable=0 is_null=0 */
### @2='2026-09-30 12:30:05.104002' /* DATETIME(6) meta=6 nullable=0 is_null=0 */
...
### @13='(long binary)
### SET
### @1=2987760775610849703 /* LONGINT meta=0 nullable=0 is_null=0 */
### @2='2026-09-30 12:30:05.104002' /* DATETIME(6) meta=6 nullable=0 is_null=0 */
...
### @13='(long binary)
i.e. all columns including unchanged ones are recorded in binlog.
With binlog_annotate_row_events=OFF, we will not have #Q> lines thus we cannot know the exact query issued, but still we can guess the original query by the following lines.
With binlog_row_image=MINIMAL, unchanged columns are not recorded in binlog and its output is like
### UPDATE `erp5_test_0`.`message_queue`
### WHERE
### @1=2161290526103520279
### SET
### @6=0
### UPDATE `erp5_test_0`.`message_queue`
### WHERE
### @1=2161290526103520280
### SET
### @6=0
The difference can be huge especially for activity tables where we may have big blob in message column.
In case of DELETE query, it's similar as UPDATE query case above, but without lines after SET.
With log_bin_compress=ON, zlib compression algorithm is used and I believe it's lightweight enough.