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: | |
| Category: | MySQL Server: Replication | Severity: | S3 (Non-critical) |
| Version: | 8.0.35 | OS: | Any |
| Assigned to: | Assigned Account | CPU Architecture: | Any |
[6 Nov 2023 22:10]
Charles Thompson
[6 Nov 2023 22:26]
Charles Thompson
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
[7 Nov 2023 13:34]
MySQL Verification Team
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
[7 Nov 2023 17:04]
Charles Thompson
Can Bug#109199 be made public? I can't access it.
Portions of this website are copyright © 2001, 2002 The PHP Group
Page generated in 0.056 sec. using MySQL 8.4.7-u6-cloud
Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the
respective copyright holders.
It is not reviewed in advance
by Oracle and does not necessarily represent the opinion of
Oracle or any other party.