MySQL Bugs: #112979: binlog_transaction_compression_level

Bug #112979	binlog_transaction_compression_level_zstd bug not fixed in 8.0.35
Submitted:	6 Nov 2023 22:10	Modified:	7 Nov 2023 17:04
Reporter:	Charles Thompson	Email Updates:
Status:	Duplicate	Impact on me:	None
Category:	MySQL Server: Replication	Severity:	S3 (Non-critical)
Version:	8.0.35	OS:	Any
Assigned to:	MySQL Verification Team	CPU Architecture:	Any

Description:
Hello,

In the 8.2 release notes, I read:

> Replication: The server did not honor the setting for the binlog_transaction_compression_level_zstd server system variable. (Bug #34833913)

I did not find a reference to this bug in 8.0.35 patch notes.

Is this intended to not go downstream or was it forgotten? I was hoping to use this variable and currently can't due to this bug. 

Thanks,

Charles

How to repeat:
None

Adding "How to repeat" for clarity:
Query:
SELECT
   compression_percentage
FROM
   performance_schema.binary_log_transaction_compression_stats
WHERE
   log_type = 'BINARY'

1. Run a workload
2. Run query above to see what the compression percentage is
3. Change binlog_transaction_compression_level_zstd from 3 (default) to maximum (22) - SET GLOBAL binlog_transaction_compression_level_zstd = 22;
4. Run a workload
5. Run query above to see what the compression percentage is

The percentages between the two values changed should be the same or very similiar

Duplicate of Bug#109199

I do not believe we will be adding this change to 8.0 but you can add your concern on the original Bug#109199

Thanks

Can Bug#109199 be made public? I can't access it.