Release notes for 5.7.23-23 (57) #2523
Conversation
| @@ -0,0 +1,75 @@ | |||
| .. rn:: 5.7.22-22 | |||
|
|
|||
| :variable:`binlog_space_limit` is consistent with the variable | ||
| :variable:`relay-log-space-limit` used for relay logs and having the same | ||
| semantics. | ||
| * In the InnoDB system tablespace all data are encrypted including the parallel |
There was a problem hiding this comment.
It is not clear whether system tablespace encryption is an existing feature we changed somehow or a new feature (it's the latter)
The parallel doublewrite buffer is not a part of the system tablespace. The legacy doublewrite buffer is.
| parallel double write buffer file is controlled by the variable | ||
| :variable:`innodb_parallel_dblwr_encrypt`. Both variables are ``OFF`` by | ||
| default. | ||
| * Changing ``rocksdb_update_cf_options`` shows warnings and errors in the |
There was a problem hiding this comment.
What was the previous behavior? (cc @georgelorchpercona)
Add JIRA ref
| New Features | ||
| ============ | ||
|
|
||
| * The :variable:`max_binlog_files` variable is deprecated and replaced |
| :variable:`binlog_space_limit` is consistent with the variable | ||
| :variable:`relay-log-space-limit` used for relay logs and having the same | ||
| semantics. | ||
| * In the InnoDB system tablespace all data are encrypted including the parallel |
| * The statement ``SELECT...ORDER BY`` produced inconsistent results with the | ||
| ``euckr`` charset or ``euckr_bin`` collation. Bug fixed :psbug:`4513` | ||
| (upstream :mysqlbug:`91091`). | ||
| * InnoDB statistics could incorrectly report zeros in the slow query log. Bug |
There was a problem hiding this comment.
InnoDB extensions for the slow query log, consider linking to the feature doc page
| * :psbug:`3988` "Unclear message in the LOG for fast CRC32" | ||
| * :psbug:`4533` "audit_log MTR tests should refer to include files without parent directories" | ||
| * :psbug:`4546` "Can\'t run mysql on Ubuntu systems with long recovery time" | ||
| * :psbug:`3702` "ALTER TABLE is slow in 5.7 when the number of dirty pages is high" |
There was a problem hiding this comment.
To main bugs fixed
| * :psbug:`3851` "Percona Ver 5.6.39-83.1 Failing assertion: sym_node->table != NULL" | ||
| * :psbug:`3988` "Unclear message in the LOG for fast CRC32" | ||
| * :psbug:`4533` "audit_log MTR tests should refer to include files without parent directories" | ||
| * :psbug:`4546` "Can\'t run mysql on Ubuntu systems with long recovery time" |
There was a problem hiding this comment.
To main bugs fixed
| * :psbug:`3796` "Cannot configure flush_caches on PS 5.7 using systemd" | ||
| * :psbug:`4046` "Ship assert failure: \'res == 0\' (bulk loader)" | ||
| * :psbug:`3851` "Percona Ver 5.6.39-83.1 Failing assertion: sym_node->table != NULL" | ||
| * :psbug:`3988` "Unclear message in the LOG for fast CRC32" |
There was a problem hiding this comment.
To main bugs fixed
|
|
||
| * :psbug:`4620` "Enable encryption of temporary tablespace from foreground thread" | ||
| * :psbug:`4727` "intrinsic temp table behaviour shouldn't depend on innodb_encrypt_tables" | ||
| * :psbug:`3796` "Cannot configure flush_caches on PS 5.7 using systemd" |
There was a problem hiding this comment.
To main bugs fixed ?
| :variable:`innodb_sys_tablespace_encrypt` is introduced to encrypt the system | ||
| tablespace. The encryption of the parallel double write buffer file is | ||
| controlled by the variable :variable:`innodb_parallel_dblwr_encrypt`. Both | ||
| variables are ``OFF`` by default. For more information, see :psbug:`3822`. |
There was a problem hiding this comment.
This should be added to https://www.percona.com/doc/percona-server/5.7/management/data_at_rest_encryption.html where rest of the feature is described. This is also missing BETA/GA information.
There was a problem hiding this comment.
This still doesn't mention the feature Beta/GA status
There was a problem hiding this comment.
Is my understanding correct that informing that the feature is in beta would conflict with the proposed (and implemented) solution for https://jira.percona.com/browse/PS-4752?
There was a problem hiding this comment.
No, please check https://jira.percona.com/browse/PS-4754
| with with the :variable:`binlog_space_limit` variable. The behavior of | ||
| :variable:`binlog_space_limit` is consistent with the variable | ||
| :variable:`relay-log-space-limit` used for relay logs and having the same | ||
| semantics. For more information, see :psbug:`275`. |
There was a problem hiding this comment.
this info should be in the feature documentation as well, for users that get redirected to max_binlog_files
| * With the FIPS mode enabled and performance_schema=off, the instance crashed | ||
| when running the ``CREATE VIEW`` command. Bug fixed :psbug:`3840`. | ||
| * The soft limit of the core file size was set incorrectly starting with PS | ||
| 5.7.21-20. Bug fixed :psbug:`4479`. |
There was a problem hiding this comment.
s/5.7.21-20/:rn:5.7.21-20 this will create the link to that PS version release notes.
There was a problem hiding this comment.
In addition to @hrvojem comments.
Upstream bug list needs updating too.
| controlled by the variable :variable:`innodb_parallel_dblwr_encrypt`. Both | ||
| variables are ``OFF`` by default. For more information, see :psbug:`3822`. | ||
| * Changing ``rocksdb_update_cf_options`` shows warnings and errors in the | ||
| client. For more information, see :psbug:`4258`. |
There was a problem hiding this comment.
returns any warnings and errors to the client instead of printing them to the server error log
|
Any update? |
| * The option ``innodb-optimize-keys`` could fail when a dumped table has two | ||
| columns such that the name of one of them contains the other as as a prefix and | ||
| is defined with the AUTO_INCREMENT attribute. Bug fixed :psbug:`4524`. | ||
| * When ``innodb_temp_tablespace_encrypt`` was set to ``ON`` the ``CREATE TABLE`` |
There was a problem hiding this comment.
use :variable:innodb_temp_tablespace_encrypt so it's automatically linked to variable description.
doc/source/ext/psdom.py
Outdated
| @@ -362,7 +362,7 @@ def resolve_xref(self, env, fromdocname, builder, | |||
| contnode, target) | |||
|
|
|||
| def get_objects(self): | |||
| for refname, (docname, type) in self.data['objects'].iteritems(): | |||
| for refname, (docname, type) in self.data['objects'].items(): | |||
| Other Bugs Fixed | ||
| ================ | ||
|
|
||
| * :psbug:`4451` "Implement better compression algo testing" | ||
| * :psbug:`4451` \"Implement better compression algo testing\" |
There was a problem hiding this comment.
Why escape the quotes? What's the difference in the output?
| :variable:`binlog_space_limit` is consistent with the variable | ||
| :variable:`relay-log-space-limit` used for relay logs; both variables have the | ||
| same semantics. For more information, see :psbug:`275`. | ||
| * Starting with |release|, all data are encrypted in the InnoDB system |
There was a problem hiding this comment.
maybe "it is possible to encrypt all data in..." as this an optional feature
reverted upon request as build nodes don’t have python3 installed yet
No description provided.