-## :fontawesome-solid-gears: Audit Log Filter plugin { .title }
+### :material-information-outline: Planning for MySQL 9.7 LTS? { .title }
+
+Plan your migration to Percona Server for MySQL 9.7 LTS from APT, DNF, or YUM packages.
+
+See the [MySQL 9.7 technical migration overview](whats-new-mysql-9.md) for breaking changes, compatibility, removed items, defaults, and tuning.
+
+
+
+## :fontawesome-solid-gears: Audit Log Filter component { .title }
-Learn about the Audit Log Filter plugin that allows you to monitor, log, and block a connection or query actively executed on the selected server.
+Learn about the Audit Log Filter component that allows you to monitor, log, and block a connection or query actively executed on the selected server.
[Audit Log Filter](audit-log-filter-overview.md){ .md-button}
diff --git a/docs/installation.md b/docs/installation.md
index ef82c2fd5ab..c4fb9517b2d 100644
--- a/docs/installation.md
+++ b/docs/installation.md
@@ -12,6 +12,10 @@ The following guides describe the installation process for using the official Pe
[Install Percona Server for MySQL on Debian and Ubuntu](apt-repo.md){.md-button} [Install Percona Server for MySQL on Red Hat Enterprise Linux](yum-repo.md){.md-button}
+Percona Server for MySQL 9.7 LTS supports installation through APT, DNF, and YUM packages.
+
+See the [MySQL 9.7 technical migration overview](whats-new-mysql-9.md) for breaking changes, compatibility, removed items, defaults, and tuning.
+
## Other installation methods
[Install Percona Server for MySQL from Binaries](binary-tarball-install.md){.md-button}
[Compile Percona Server for MySQL from Source](source-tarball.md){.md-button}
[Run Percona Server for MySQL in a Docker container](docker.md){.md-button}
diff --git a/docs/percona-sequence-table.md b/docs/percona-sequence-table.md
index 0c284c98451..b25eda7b239 100644
--- a/docs/percona-sequence-table.md
+++ b/docs/percona-sequence-table.md
@@ -13,9 +13,7 @@ Using the `PERCONA_SEQUENCE_TABLE()` function provides the following:
## Version update
-
-
-Percona Server for MySQL 8.4 deprecated [`SEQUENCE_TABLE()`](sequence-table.md), and Percona may remove this function in a future release. We recommend that you use `PERCONA_SEQUENCE_TABLE()` instead.
+Percona Server for MySQL 8.4 deprecated `SEQUENCE_TABLE()`. Percona Server for MySQL 9.7 removes `SEQUENCE_TABLE()` in favor of `PERCONA_SEQUENCE_TABLE()`. Use `PERCONA_SEQUENCE_TABLE()` in all new and existing code.
To maintain compatibility with existing third-party software, `SEQUENCE_TABLE` is no longer a reserved term and can be used as a regular identifier.
@@ -183,6 +181,4 @@ SELECT * FROM t1;
+-------+
```
-Sequences are helpful for various purposes, such as populating tables and generating test data.
-
-[SEQUENCE_TABLE()]: sequence-table.md
\ No newline at end of file
+Sequences are helpful for various purposes, such as populating tables and generating test data.
\ No newline at end of file
diff --git a/docs/sequence-table.md b/docs/sequence-table.md
deleted file mode 100644
index 0f00bd58e28..00000000000
--- a/docs/sequence-table.md
+++ /dev/null
@@ -1,193 +0,0 @@
-# SEQUENCE_TABLE(n) function
-
-Using `SEQUENCE_TABLE()` function provides the following:
-
-| Benefit | Description |
-|---------------------------|---------------------------------------------------------------------------------------------------|
-| Generates Sequences | Acts as an inline table-valued function that generates a sequence of numbers. |
-| Table-Valued Function | Unlike traditional scalar functions, `SEQUENCE_TABLE()` returns a virtual table with a single column named `value` containing the generated sequence. |
-| Simpler Syntax | Simplifies queries that need to generate predictable sequences of numbers. |
-| Flexibility | Allows dynamic definition of sequences within queries, offering more control compared to pre-defined tables for sequences. |
-| Predefined Sequence | Does not manage sequences like Oracle or PostgreSQL; instead, it allows definition and generation of sequences within a `SELECT` statement. |
-| Customization | Enables customization of starting value, increment/decrement amount, and number of values to generate. |
-
-## Version update
-
-Percona Server for MySQL 8.4 deprecated `SEQUENCE_TABLE()`, and this function can be removed in a future release. We recommend that you use [`PERCONA_SEQUENCE_TABLE()`](percona-sequence-table.md) instead.
-
-To maintain compatibility with existing third-party software, `SEQUENCE_TABLE` is no longer a reserved term and can be used as a regular identifier.
-
-## Table functions
-
-The function is an inline table-valued function. This function creates a temporary table with multiple rows. You can use this function within a single SELECT statement. Oracle MySQL Server only has the [`JSON_TABLE` :octicons-link-external-16:](https://dev.mysql.com/doc/refman/{{vers}}/en/json-table-functions.html) table function. The Percona Server for MySQL has the `JSON_TABLE` and `SEQUENCE_TABLE()` table functions. A single SELECT statement generates a multi-row result set. In contrast, a scalar function (like [EXP(x) :octicons-link-external-16:](https://dev.mysql.com/doc/refman/{{vers}}/en/mathematical-functions.html#function_exp) or [LOWER(str) :octicons-link-external-16:](https://dev.mysql.com/doc/refman/{{vers}}/en/string-functions.html#function_lower) always returns a single value of a specific data type.
-
-## Syntax
-
-As with any [derived tables :octicons-link-external-16:](https://dev.mysql.com/doc/refman/{{vers}}/en/derived-tables.html), a table function requires an [alias :octicons-link-external-16:](https://dev.mysql.com/doc/refman/{{vers}}/en/identifiers.html) in the `SELECT` statement.
-
-The result set is a single column with the predefined column name `value` of type `BIGINT UNSIGNED`. You can reference the `value` column in `SELECT` statements. The following statements are valid. Using `n` as the number of generated values, the following is the basic syntax:
-
-* SEQUENCE_TABLE(n) [AS] alias
-
-
-```text
-SELECT … FROM SEQUENCE_TABLE(n) [AS] alias
-
-SEQUENCE_TABLE(n) [AS] alias
-```
-
-```sql
-SELECT * FROM SEQUENCE_TABLE(n) AS tt;
-SELECT
FROM SEQUENCE_TABLE(n) AS tt;
-```
-
-The first number in the series, the initial term, is defined as `0`, and the series ends with a value less than `n`.
-
-## Example usage
-
-Using `SEQUENCE_TABLE()`:
-
-```sql
-SELECT * FROM SEQUENCE_TABLE(5)) AS sequence_data;
-```
-
-Using `PERCONA_SEQUENCE_TABLE()`:
-
-```sql
-SELECT * FROM PERCONA_SEQUENCE_TABLE(5)) AS sequence_data;
-```
-
-### Basic sequence generation
-
-In this example, the following statement generates a sequence:
-
-```sql
-SELECT * FROM SEQUENCE_TABLE(3) AS tt;
-```
-
-??? example "Expected output"
-
- ```{.text .no-copy}
- +-------+
- | value |
- +-------+
- | 0 |
- | 1 |
- | 2 |
- +-------+
- ```
-
-### Start with a specific value
-
-You can define the initial value using the `WHERE` clause. The following example starts the sequence with `4`.
-
-```sql
-SELECT value AS result FROM SEQUENCE_TABLE(8) AS tt WHERE value >= 4;
-```
-
-??? example "Expected output"
-
- ```{.text .no-copy}
- +--------+
- | result |
- +--------+
- | 4 |
- | 5 |
- | 6 |
- | 7 |
- +--------+
- ```
-
-### Filter even numbers
-
-Consecutive terms increase or decrease by a common difference. The default common difference value is `1`. However, it is possible to filter the results using the WHERE clause to simulate common differences greater than 1.
-
-The following example prints only even numbers from the 0..7 range:
-
-```sql
-SELECT value AS result FROM SEQUENCE_TABLE(8) AS tt WHERE value % 2 = 0;
-```
-
-??? example "Expected output"
-
- ```{.text .no-copy}
- +--------+
- | result |
- +--------+
- | 0 |
- | 2 |
- | 4 |
- | 6 |
- +--------+
- ```
-
-### Generate random numbers
-
-The following is an example of using the function to populate a table with a set of random numbers:
-
-```sql
-SELECT FLOOR(RAND() * 100) AS result FROM SEQUENCE_TABLE(4) AS tt;
-```
-
-The output could be the following:
-
-??? example "Expected output"
-
- ```{.text .no-copy}
- +--------+
- | result |
- +--------+
- | 24 |
- | 56 |
- | 70 |
- | 25 |
- +--------+
- ```
-
-### Generate random strings
-
-You can populate a table with a set of pseudo-random strings with the following statement:
-
-```sql
-SELECT MD5(value) AS result FROM SEQUENCE_TABLE(4) AS tt;
-```
-
-??? example "Expected output"
-
- ```{.text .no-copy}
- +----------------------------------+
- | result |
- +----------------------------------+
- | f17d9c990f40f8ac215f2ecdfd7d0451 |
- | 2e5751b7cfd7f053cd29e946fb2649a4 |
- | b026324c6904b2a9cb4b88d6d61c81d1 |
- | 26ab0db90d72e28ad0ba1e22ee510510 |
- +----------------------------------+
- ```
-
-### Add a sequence to a table
-
-You can add the sequence as a column to a new table or an existing table, as shown in this example:
-
-```sql
-CREATE TABLE t1 AS SELECT * FROM SEQUENCE_TABLE(4) AS tt;
-
-SELECT * FROM t1;
-```
-
-??? example "Expected output"
-
- ```{.text .no-copy}
- +-------+
- | value |
- +-------+
- | 0 |
- | 1 |
- | 2 |
- | 3 |
- +-------+
- ```
-
-Sequences are helpful for various purposes, such as populating tables and generating test data.
-
-[`PERCONA_SEQUENCE_TABLE()`]: percona-sequence-table.md
\ No newline at end of file
diff --git a/docs/upgrade.md b/docs/upgrade.md
index 910e679623a..5057019f795 100644
--- a/docs/upgrade.md
+++ b/docs/upgrade.md
@@ -51,6 +51,10 @@ Review these documents to understand breaking changes, removed features, and com
* [Percona Toolkit updates for {{vers}}](./percona-toolkit-8.4-updates.md) - Review toolkit changes if you use Percona Toolkit
+Plan a migration to Percona Server for MySQL 9.7 LTS.
+
+See the [MySQL 9.7 technical migration overview](./whats-new-mysql-9.md) for breaking changes, compatibility, removed items, defaults, and tuning.
+
### Step 2: Complete pre-upgrade preparation
Work through the pre-upgrade checks in the [upgrade checklist](./upgrade-checklist-8.4.md). This includes:
@@ -139,12 +143,10 @@ Review these upgrade-related documents:
* [Downgrade options](./downgrade.md)
* [Breaking and incompatible changes in {{vers}}](./8.4-breaking-changes.md)
-
* [Compatibility and removed items in {{vers}}](./8.4-compatibility-and-removed-items.md)
-
* [Defaults and tuning guidance for {{vers}}](./8.4-defaults-and-tuning.md)
-
* [Percona Toolkit updates for {{vers}}](./percona-toolkit-8.4-updates.md)
+* [MySQL 9.7 technical migration overview](./whats-new-mysql-9.md)
### Additional MySQL documentation
diff --git a/docs/whats-new-mysql-9.md b/docs/whats-new-mysql-9.md
new file mode 100644
index 00000000000..924d57c7684
--- /dev/null
+++ b/docs/whats-new-mysql-9.md
@@ -0,0 +1,520 @@
+# MySQL 9.7 technical migration overview
+
+MySQL 9 minor releases remove legacy plugins and change defaults for security and replication. Database administrators must align accounts, configuration files, and replication topology before they upgrade.
+
+Use this overview alongside the [upgrade overview](upgrade.md), [installation](installation.md) guide, and [upgrade procedures](upgrade-procedures.md).
+
+You move from MySQL 8.4 Long-Term Support (LTS) toward Percona Server for MySQL 9.7. Percona behavior can differ from Oracle MySQL Community Edition.
+
+Read the [release notes](release-notes/release-notes-index.md) for your build.
+
+The following sections cover incompatible changes by release, MySQL 9.7 Community Server behavior, defaults, and a pre-upgrade checklist.
+
+## Review breaking changes before upgrade
+
+Address the following items before you upgrade production servers.
+
+High-impact items:
+
+* `mysql_native_password` authentication plugin is removed.
+
+* Migrate all accounts to a supported plugin (for example, `caching_sha2_password`) before upgrade, or authentication fails.
+
+* `gtid_mode` and `enforce_gtid_consistency` default to `ON`.
+
+* You must set Global Transaction Identifier (GTID) options explicitly when replication still uses file names and positions only.
+
+* `keyring_file` plugin is removed.
+
+* Migrate to a supported keyring component before upgrade, or the server may fail to start.
+
+Each subsection states impact, replacement options, and required actions.
+
+## Migrate authentication and users (MySQL 9.0)
+
+MySQL 9.0 removes the `mysql_native_password` plugin and related server options.
+
+Impact:
+
+* Oracle removes `mysql_native_password` in MySQL 9.0.0 after deprecation across MySQL 8.0.
+
+* Accounts that still use `mysql_native_password` cannot authenticate against a MySQL 9.0 and later server.
+
+* Clients without `CLIENT_PLUGIN_AUTH` support receive rejection during handshake.
+
+* Server removes `--mysql-native-password`, `--mysql-native-password-proxy-users`, and `default_authentication_plugin`.
+
+* The removal affects only the MySQL 9.0 and later server process.
+
+* Client libraries can still use `mysql_native_password` against older MySQL 8.0 or 5.7 servers.
+
+Replacement:
+
+* Use `caching_sha2_password` or another supported authentication plugin.
+
+* The default plugin for accounts you create is `caching_sha2_password` in MySQL 8.4 and later.
+
+Action:
+
+* List accounts and applications that still reference `mysql_native_password`.
+
+* Migrate each account to a supported plugin before you upgrade the server.
+
+* Delete references to removed authentication options and variables from configuration files and scripts before upgrade.
+
+Example statement:
+
+```sql
+ALTER USER ''@''
+IDENTIFIED WITH caching_sha2_password BY '';
+```
+
+## Configure GTID and replication defaults (MySQL 9.0)
+
+Replication behavior depends on Global Transaction Identifier (GTID) variables. Incorrect defaults cause most upgrade failures in mixed topologies.
+
+Impact:
+
+* `gtid_mode` defaults to `ON` in MySQL 9.0.
+
+* `enforce_gtid_consistency` defaults to `ON`.
+
+* Non-GTID replication can fail to start unless you set variables explicitly.
+
+* `enforce_gtid_consistency=ON` blocks certain non-deterministic statements inside transactions.
+
+* Some packages apply `OFF_PERMISSIVE` transition states during upgrade.
+
+* Until GTID migration completes, set explicit `gtid_mode=OFF` and `enforce_gtid_consistency=OFF` when needed.
+
+Replacement:
+
+* Adopt GTID-based replication or set GTID variables off before you start the upgraded server.
+
+Action:
+
+* If you do not use GTID yet, add the following lines to configuration before upgrade:
+
+```text
+gtid_mode=OFF
+enforce_gtid_consistency=OFF
+```
+
+* Review application SQL and stored programs for `enforce_gtid_consistency=ON` violations.
+
+## Remove `--early-plugin-load` (MySQL 9.1)
+
+Oracle removes the `--early-plugin-load` server option in MySQL 9.1.
+
+Impact:
+
+* Configuration files that still contain `--early-plugin-load` can prevent startup.
+
+Replacement:
+
+* Load functionality through supported components and the component manifest (for example, `mysqld.my`).
+
+Action:
+
+* Search configuration paths for `--early-plugin-load` and delete those lines.
+
+* Move required behavior to components when the manual documents migration steps.
+
+## Adjust mysql client `\G` and `\C` usage (MySQL 9.1)
+
+The `mysql` client accepts `\G` (vertical output) and `\C` (clear) only at the end of a statement.
+
+Impact:
+
+* Scripts that place `\G` or `\C` in the middle of a statement can fail or print unexpected output.
+
+Replacement:
+
+* Place `\G` and `\C` only after a complete statement or split commands into separate invocations.
+
+Action:
+
+* Audit shell scripts, automation, and `mysql -e` batches.
+
+* Fix mid-statement tokens.
+
+## Recognize atomic DDL for databases (MySQL 9.1)
+
+`CREATE DATABASE` and `DROP DATABASE` run as atomic, crash-safe operations.
+
+Impact:
+
+* Correct usage does not change; behavior improves for crash recovery.
+
+Action:
+
+* No change required
+
+## Migrate from `keyring_file` to `component_keyring_file` (MySQL 9.2)
+
+Migration requires a component manifest. You cannot convert the plugin with a single `my.cnf` edit.
+
+Impact:
+
+* The MySQL 9.2 distribution omits the `keyring_file` plugin binary.
+
+* Startup fails when configuration still loads the plugin.
+
+Replacement:
+
+* Install `component_keyring_file` for file-based keyring storage.
+
+* Configure the component through a JSON manifest.
+
+* Use files such as `component_keyring_file.cnf` or the manifest registry.
+
+* Do not rely on legacy plugin variables in `my.cnf` alone.
+
+Action:
+
+* Create and initialize the component manifest before upgrade.
+
+* Move keyring data into the component layout that the manual specifies.
+
+* Remove `keyring_file` directives from `my.cnf` and other option files before upgrade.
+
+## Replace deprecated `FLUSH PRIVILEGES` usage (MySQL 9.2)
+
+Oracle deprecates `FLUSH PRIVILEGES` and related administration paths in MySQL 9.2.
+
+Impact:
+
+* `FLUSH PRIVILEGES` emits warnings.
+
+* `FLUSH_PRIVILEGES` privilege, `mysqladmin flush-privileges`, and `mysqladmin reload` are deprecated.
+
+Replacement:
+
+* Follow privilege-load behavior in the MySQL Reference Manual for the target version.
+
+Action:
+
+* Update scripts, automation, and runbooks that still call deprecated flush commands.
+
+## Remove Version Tokens usage (MySQL 9.3)
+
+Oracle deprecates Version Tokens in MySQL 9.2 and removes the plugin in MySQL 9.3.
+
+Impact:
+
+* MySQL 9.3 removes functions, privileges, and variables associated with Version Tokens.
+
+Replacement:
+
+* Oracle provides no direct substitute inside the server.
+
+Action:
+
+* Delete Version Tokens references from configuration and application code before upgrade.
+
+## Migrate Connection Control to the component (MySQL 9.2)
+
+Oracle deprecates the Connection Control plugins and schedules removal after MySQL 9.2.
+
+Impact:
+
+* Oracle removes both Connection Control plugins from the distribution after MySQL 9.2.
+
+Replacement:
+
+* Install `component_connection_control` through `INSTALL COMPONENT` syntax.
+
+Action:
+
+* Replace the plugins with the component.
+
+* Update monitoring queries that read deprecated Information Schema tables.
+
+## Set `replica_parallel_workers` minimum (MySQL 9.3)
+
+Oracle disallows `replica_parallel_workers=0` starting in MySQL 9.3.
+
+Impact:
+
+* Minimum value is `1`.
+
+* Default became `4` in MySQL 8.0.30 and later.
+
+* Setups that use `replica_parallel_workers=0` for single-threaded apply must change before upgrade.
+
+Replacement:
+
+* Use `replica_parallel_workers=1` for single-threaded apply or omit the variable to keep the default.
+
+Action:
+
+* Before upgrade, change `replica_parallel_workers=0` to `1` or delete the line to restore the default.
+
+## Remove deprecated InnoDB variables (MySQL 9.3)
+
+Oracle removes legacy InnoDB sizing variables in MySQL 9.3. Redo and undo sizing follow variables documented for MySQL 9.7.
+
+Impact:
+
+The following variables are removed:
+
+* `innodb_log_file_size`
+
+* `innodb_log_files_in_group`
+
+* `innodb_undo_tablespaces`
+
+Replacement:
+
+| Removed variable | MySQL 9.7 approach |
+| ------------------------- | --------------------------- |
+| `innodb_log_file_size` | `innodb_redo_log_capacity` |
+| `innodb_log_files_in_group` | Automatic management |
+| `innodb_undo_tablespaces` | Automatic undo management |
+
+Action:
+
+* Delete removed variables from option files.
+
+* Read redo and undo chapters in the MySQL Reference Manual for the target version.
+
+## Fix `IGNORE` with scalar subqueries (MySQL 9.0)
+
+`IGNORE` no longer hides `ER_SUBQUERY_NO_1_ROW` when a scalar subquery returns more than one row.
+
+Impact:
+
+* `INSERT IGNORE`, `UPDATE IGNORE`, and `DELETE IGNORE` can fail where they succeeded before.
+
+Replacement:
+
+* Restrict scalar subqueries to zero or one row.
+
+Action:
+
+* Audit application SQL and stored routines.
+
+* Correct the logic or remove unsafe `IGNORE` usage.
+
+## Enforce inline foreign keys (MySQL 9.0)
+
+Oracle enforces inline foreign key syntax that older releases parsed but ignored.
+
+Impact:
+
+* MySQL 9.0 rejects invalid inline foreign keys as errors.
+
+Action:
+
+* Compare schemas and generated Data Definition Language (DDL) against intended constraints.
+
+## Plan migration from `MD5()` and `SHA1()` in SQL (MySQL 9.4)
+
+Oracle deprecates the `MD5()` and `SHA1()` SQL functions in MySQL 9.4. Legacy applications that compute hashes in SQL face the highest risk of breakage.
+
+Impact:
+
+* Deprecation applies to the SQL functions `MD5()` and `SHA1()`.
+
+* Functions still execute, but Oracle may remove them in a later release.
+
+* PHP and Java stacks that call these functions in SQL need review.
+
+Replacement:
+
+* Call `SHA2()` in SQL or compute hashes in the application.
+
+Action:
+
+* Audit procedures, triggers, and application SQL.
+
+* Replace `MD5()` and `SHA1()` calls when compliance allows.
+
+## Replace removed Group Replication and semisync variables (MySQL 9.5)
+
+Oracle removes several replication variables in MySQL 9.5. Semisynchronous replication moves from plugins to components.
+
+Impact:
+
+* `group_replication_allow_local_lower_version_join` is removed.
+
+* `replica_parallel_type` and `slave_parallel_type` are removed.
+
+* MySQL 9.5 removes the legacy semisynchronous plugins `semisync_master.so` and `semisync_slave.so`.
+
+* `rpl_semi_sync_*` variables are removed.
+
+* Semisynchronous replication remains available through replacement components.
+
+Replacement:
+
+* Use the Semisynchronous Replication Source and Replica components for semisync behavior.
+
+Action:
+
+* Delete removed variables from configuration and monitoring.
+
+* Install and configure semisync components as documented in the MySQL Reference Manual.
+
+## What changed in MySQL 9.7 Community Server
+
+The following statements describe Oracle MySQL Community Server 9.7 only.
+
+Percona Server for MySQL can differ. Read the Percona release notes for your build.
+
+### Cross-reference MySQL 9.7 removal lists
+
+Section 1.5 of the MySQL 9.7 Reference Manual lists no options or variables removed only in MySQL 9.7. Compare [What Is New in MySQL 9.7](https://dev.mysql.com/doc/refman/9.7/en/mysql-nutshell.html) with Section 1.5. Nutshell removal lists can repeat changes first documented in earlier MySQL 9 minor releases.
+
+Reference: [Server options and variables added, deprecated, or removed in MySQL 9.7](https://dev.mysql.com/doc/refman/9.7/en/added-deprecated-removed.html).
+
+### Configure replication across versions
+
+Community Server 9.7 exposes the following replication-related settings:
+
+* `replica_allow_higher_version_source` controls replication from a higher-version source to a lower replica. Use this variable during staged upgrades.
+
+* `object_policy_flush_interval_seconds` refreshes the object policy cache on secondaries and replicas.
+
+References:
+
+* [Replication options (replica)](https://dev.mysql.com/doc/refman/9.7/en/replication-options-replica.html)
+
+* [MySQL 9.7.0 release notes](https://dev.mysql.com/doc/relnotes/mysql/9.7/en/news-9-7-0.html)
+
+* Section 1.5 in the MySQL 9.7 Reference Manual
+
+### Configure caching SHA-2 storage format
+
+The following variables control caching SHA-2 password storage format options:
+
+* `caching_sha2_password_storage_format` and `caching_sha2_password_enforce_storage_format` support PBKDF2 storage with `caching_sha2_password`.
+
+See [Caching SHA-2 pluggable authentication](https://dev.mysql.com/doc/refman/9.7/en/caching-sha2-pluggable-authentication.html).
+
+### Review foreign key cascade handling
+
+The variable `enable_cascade_triggers` controls the foreign key cascade execution path in MySQL 9.7. Oracle deprecated the variable in the same release.
+
+Follow the MySQL 9.7 manual for supported behavior after upgrade.
+
+### Install components that Community Edition includes
+
+Community Server 9.7 includes components that once required MySQL Enterprise Edition only.
+
+The following list orders components alphabetically by name:
+
+* Group Replication Flow Control Statistics component
+
+* Group Replication Primary Election component
+
+* Group Replication Resource Manager component
+
+* Replication Applier Metrics component
+
+* Telemetry component
+
+See [MySQL 9.7.0 release notes, Component notes](https://dev.mysql.com/doc/relnotes/mysql/9.7/en/news-9-7-0.html).
+
+### Run Data Manipulation Language (DML) on JSON duality views
+
+Community Server 9.7 supports `INSERT`, `UPDATE`, and `DELETE` on JSON duality views.
+
+See [DML operations on JSON duality views](https://dev.mysql.com/doc/refman/9.7/en/json-duality-views-updatable.html).
+
+### Toggle the hypergraph optimizer
+
+Community Server 9.7 exposes the hypergraph optimizer through `optimizer_switch`. Scope includes session, global, persisted, and statement hints.
+
+See [MySQL 9.7.0 release notes, Optimizer](https://dev.mysql.com/doc/relnotes/mysql/9.7/en/news-9-7-0.html).
+
+### Use Clone across consecutive LTS releases
+
+Clone supports donor and recipient pairs on consecutive LTS releases later than 9.7.0.
+
+Read [Clone plugin limitations](https://dev.mysql.com/doc/refman/9.7/en/clone-plugin-limitations.html). Read [Remote cloning prerequisites](https://dev.mysql.com/doc/refman/9.7/en/clone-plugin-remote.html) before you rely on Clone for upgrades.
+
+### Packaging and resource limits
+
+Review package builds and runtime resource behavior from the following notes:
+
+* Builds that bundle OpenSSL link a refreshed library. See packaging notes in [MySQL 9.7.0 release notes](https://dev.mysql.com/doc/relnotes/mysql/9.7/en/news-9-7-0.html).
+
+* InnoDB reads logical CPU counts from `cpuset` cgroup limits when those limits exist. See InnoDB notes in the [MySQL 9.7.0 release notes](https://dev.mysql.com/doc/relnotes/mysql/9.7/en/news-9-7-0.html).
+
+### External manuals for MySQL 9.7
+
+Oracle publishes the following manuals for MySQL 9.7 Community Server, listed alphabetically by title:
+
+* [MySQL 9.7 Reference Manual](https://dev.mysql.com/doc/refman/9.7/en/)
+
+* [MySQL 9.7 release notes index](https://dev.mysql.com/doc/relnotes/mysql/9.7/en/)
+
+* [Server and status variables in MySQL 9.7](https://dev.mysql.com/doc/refman/9.7/en/added-deprecated-removed.html)
+
+* [What Is New in MySQL 9.7](https://dev.mysql.com/doc/refman/9.7/en/mysql-nutshell.html)
+
+## What changed in Percona Server for MySQL 9.7
+
+The following changes apply to Percona Server for MySQL 9.7 only. Oracle MySQL Community Server does not include these items.
+
+### Removed `SEQUENCE_TABLE()` in favor of `PERCONA_SEQUENCE_TABLE()`
+
+Percona Server for MySQL 8.4 deprecated `SEQUENCE_TABLE()`. Percona Server for MySQL 9.7 removes the function.
+
+Impact:
+
+* Queries that call `SEQUENCE_TABLE(n)` fail on 9.7 servers.
+
+* Stored routines, views, and applications that reference `SEQUENCE_TABLE()` break after upgrade.
+
+Replacement:
+
+* Use `PERCONA_SEQUENCE_TABLE(n)`. The replacement returns the same single-column virtual table.
+
+Action:
+
+* Search application code, stored routines, and scripts for `SEQUENCE_TABLE(` occurrences.
+
+* Replace each call with `PERCONA_SEQUENCE_TABLE(` before you upgrade.
+
+See [`PERCONA_SEQUENCE_TABLE(n)` function](percona-sequence-table.md) for syntax and examples.
+
+## Defaults and tuning guidance
+
+Global Transaction Identifier (GTID) defaults changed in MySQL 9.0.
+
+| Variable | Default in MySQL 9.0 and later | Default before 9.0 |
+| -------------------------- | ------------------------------ | ------------------ |
+| `gtid_mode` | `ON` | `OFF` |
+| `enforce_gtid_consistency` | `ON` | `OFF` |
+
+## InnoDB redo writers and binary log history (MySQL 9.5 and later)
+
+Default behavior depends on `innodb_log_writer_threads`:
+
+* When binary logging is off, the default follows logical CPU count.
+
+* When binary logging is on, defaults match MySQL 9.4 rules for large CPU counts.
+
+The `binlog_transaction_dependency_history_size` default is 1,000,000 in MySQL 9.5.0 and later. The maximum is 10,000,000.
+
+Existing explicit values stay unchanged.
+
+## Pre-upgrade checklist
+
+Run the following checks in a non-production environment first:
+
+* Delete deprecated variables, options, and plugins from configuration.
+
+* Confirm authentication plugins and migrate accounts off `mysql_native_password`.
+
+* Document replication topology and Global Transaction Identifier (GTID) strategy.
+
+* Validate InnoDB redo and undo settings against the target manual.
+
+* Replace `SEQUENCE_TABLE()` calls with `PERCONA_SEQUENCE_TABLE()` in application code, stored routines, and scripts.
+
+* Execute test upgrades, replication failover, and backup restore drills before production cutover.
+
+For upgrade sequencing, return to the [upgrade overview](upgrade.md) and [upgrade strategies](upgrade-strategies.md).
diff --git a/generate_index_keywords.py b/generate_index_keywords.py
deleted file mode 100644
index 7c98eb5c6f4..00000000000
--- a/generate_index_keywords.py
+++ /dev/null
@@ -1,304 +0,0 @@
-"""
-Generate an A–Z documentation index that lists:
- * Markdown files (by title) grouped under their starting letter.
- * Keywords/phrases (from db_terms.txt) grouped under their starting letter,
- each linking to all docs in which the term appears.
-
-What's new in this version
-==========================
-• **Multi‑word terms supported**: Lines in `db_terms.txt` may contain spaces (e.g., "tech preview", "storage engine").
-• **Original capitalization preserved**: How you write the term in `db_terms.txt` is how it appears in the generated index.
-• **Case‑insensitive matching**: Terms match regardless of capitalization in Markdown content.
-• **Whitespace‑flexible phrase matching**: Internal whitespace in a term (spaces/tabs/newlines) is matched with `\s+` so a term can wrap lines in Markdown and still match.
-• **Code blocks ignored**: Fenced code (``` ... ```) and inline code (`...`) are stripped before matching so code examples do not create false positives.
-• **Backward compatible single‑word behavior**: Single tokens in `db_terms.txt` work exactly as before.
-
-Usage
------
-1. Put your canonical keyword/phrase list (one per line) in `db_terms.txt`.
-2. Run this script from the project root (the directory that contains `docs/`).
-3. The script writes `docs/index-keywords.md`.
-
-Notes / Recommendations
------------------------
-* Blank lines and lines that start with `#` (comment) in `db_terms.txt` are ignored.
-* Duplicate terms (case-insensitive) keep the first casing encountered.
-* If you have overlapping terms (e.g., "engine" and "storage engine"), **both** can be listed; each is matched independently.
-* Very common short words (e.g., "the") will match widely—avoid including those.
-
-"""
-
-import os
-import re
-from collections import defaultdict
-from typing import Dict, List, Tuple, Pattern
-
-DEBUG = False
-DB_TERMS_FILE = "db_terms.txt"
-
-# ---------------------------------------------------------------------------
-# Loading & preparing DB terms
-# ---------------------------------------------------------------------------
-
-def load_db_terms() -> Dict[str, str]:
- """Load terms from DB_TERMS_FILE.
-
- Returns a dict mapping lowercase term -> *original* term string (trimmed),
- preserving the first capitalization seen.
-
- Lines that are blank or start with '#' are skipped.
- """
- if not os.path.exists(DB_TERMS_FILE):
- print(f"'{DB_TERMS_FILE}' not found. Creating an empty file.")
- open(DB_TERMS_FILE, 'w', encoding='utf-8').close()
- return {}
-
- terms: Dict[str, str] = {}
- with open(DB_TERMS_FILE, 'r', encoding='utf-8') as f:
- for raw in f:
- line = raw.strip()
- if not line:
- continue
- if line.startswith('#'):
- continue
- key = line.lower()
- # keep the *first* capitalization encountered for a given lowercase key
- terms.setdefault(key, line)
- return terms
-
-
-# ---------------------------------------------------------------------------
-# Content preprocessing (strip code blocks / inline code)
-# ---------------------------------------------------------------------------
-
-def strip_code(content: str) -> str:
- """Remove fenced and inline code segments from Markdown content.
-
- This reduces false positives when scanning for terms.
- """
- # Remove fenced code blocks ```...``` (greedy across newlines)
- content = re.sub(r"```[\s\S]*?```", " ", content)
- # Remove inline code `...`
- content = re.sub(r"`[^`]+`", " ", content)
- return content
-
-
-# ---------------------------------------------------------------------------
-# Build regex patterns for each term
-# ---------------------------------------------------------------------------
-
-def _term_to_regex(term: str) -> str:
- """Convert a term (possibly multi-word) to a regex string.
-
- Rules:
- * Match case-insensitively (applied when compiled).
- * Enforce word boundaries at start & end (\b) for alnum/underscore tokens.
- * Internal whitespace in the term becomes "\s+" in regex.
- * Other punctuation characters in the term are escaped literally.
-
- Examples:
- 'MySQL' -> r'\bMySQL\b'
- 'tech preview' -> r'\btech\s+preview\b'
- 'xtrabackup-plugin' -> r'\bxtrabackup\-plugin\b'
-
- NOTE: If you *intentionally* want to match inside words, include a '*' at
- the start/end yourself and call this function differently. For now we keep
- it simple & safe.
- """
- # Split on whitespace to decide where to allow flexible spacing
- parts = re.split(r"\s+", term.strip())
- escaped_parts = [re.escape(p) for p in parts if p]
- if not escaped_parts:
- return "" # shouldn't happen; caller guards
-
- body = r"\s+".join(escaped_parts) if len(escaped_parts) > 1 else escaped_parts[0]
-
- # Wrap with word boundaries. We deliberately use \b; this behaves well for
- # alnum/_ boundaries. If your term starts/ends with punctuation, \b may not
- # behave exactly as expected, but it's still usually fine. We could enhance
- # with lookarounds if needed later.
- return rf"\b{body}\b"
-
-
-def build_term_patterns(db_terms: Dict[str, str]) -> Dict[str, Pattern[str]]:
- """Compile regex patterns (IGNORECASE) for each term.
-
- Returns dict mapping lowercase-term -> compiled Pattern.
- """
- patterns: Dict[str, Pattern[str]] = {}
- for lterm, orig in db_terms.items():
- regex_str = _term_to_regex(orig)
- if not regex_str:
- continue
- patterns[lterm] = re.compile(regex_str, re.IGNORECASE)
- return patterns
-
-
-# ---------------------------------------------------------------------------
-# Extract title from Markdown
-# ---------------------------------------------------------------------------
-
-def extract_title(content: str, filename: str) -> str:
- """Extract the first Markdown H1 (#) heading; fallback to filename."""
- match = re.search(r'^#\s+(.*)', content, re.MULTILINE)
- return match.group(1).strip() if match else filename
-
-
-# ---------------------------------------------------------------------------
-# Keyword/phrase detection in content
-# ---------------------------------------------------------------------------
-
-def extract_keywords(content: str, db_terms: Dict[str, str], patterns: Dict[str, Pattern[str]]) -> List[str]:
- """Return a list of *original-case* db terms found in content.
-
- Matching is case-insensitive; internal whitespace in the term is flexible.
- Code blocks and inline code are ignored.
- """
- text = strip_code(content)
- found: List[str] = []
- for lterm, pat in patterns.items():
- if pat.search(text):
- found.append(db_terms[lterm]) # original capitalization
- # Deduplicate while preserving original order
- seen = set()
- unique = []
- for t in found:
- if t.lower() in seen:
- continue
- seen.add(t.lower())
- unique.append(t)
- return sorted(unique, key=str.lower)
-
-
-# ---------------------------------------------------------------------------
-# Scan docs tree
-# ---------------------------------------------------------------------------
-
-def scan_markdown_files(
- docs_dir: str,
- db_terms: Dict[str, str],
- patterns: Dict[str, Pattern[str]],
-) -> Tuple[List[Tuple[str, str]], Dict[str, List[str]], Dict[str, str]]:
- """Scan Markdown files and map found keywords to files.
-
- Returns:
- file_data : list of (title, rel_path)
- keyword_map : term -> [rel_paths...]
- title_map : rel_path -> title
- """
- file_data: List[Tuple[str, str]] = []
- keyword_map: Dict[str, List[str]] = defaultdict(list)
- title_map: Dict[str, str] = {}
-
- for root, _, files in os.walk(docs_dir):
- for filename in files:
- if not filename.endswith('.md'):
- continue
- if filename == 'index-keywords.md':
- continue
-
- rel_path = os.path.relpath(os.path.join(root, filename), docs_dir)
-
- # Skip release notes subtree
- if rel_path.startswith("release-notes" + os.sep):
- continue
-
- full_path = os.path.join(root, filename)
- with open(full_path, 'r', encoding='utf-8') as f:
- content = f.read()
-
- title = extract_title(content, filename)
- kws = extract_keywords(content, db_terms, patterns)
-
- file_data.append((title, rel_path))
- title_map[rel_path] = title
-
- if DEBUG and kws:
- print(f"[DEBUG] {rel_path}: {kws}")
-
- for kw in kws:
- keyword_map[kw].append(rel_path)
-
- # Deduplicate and sort rel_paths per keyword
- for kw in keyword_map:
- keyword_map[kw] = sorted(set(keyword_map[kw]))
-
- return file_data, keyword_map, title_map
-
-
-# ---------------------------------------------------------------------------
-# Index generation
-# ---------------------------------------------------------------------------
-
-def generate_alphabetical_index(
- file_data: List[Tuple[str, str]],
- keyword_map: Dict[str, List[str]],
- title_map: Dict[str, str],
-) -> str:
- """Generate the Markdown index grouped by initial letter."""
- index_content = "# Documentation Index by Alphabet\n\n"
-
- # Group files by first letter of title
- files_by_letter: Dict[str, List[Tuple[str, str]]] = defaultdict(list)
- for title, path in file_data:
- letter = title[0].upper() if title else '#'
- files_by_letter[letter].append((title, path))
-
- # Group keywords by first letter (use display case; safe to index 0)
- kws_by_letter: Dict[str, List[str]] = defaultdict(list)
- for kw in keyword_map.keys():
- letter = kw[0].upper() if kw else '#'
- kws_by_letter[letter].append(kw)
-
- for letter in (chr(c) for c in range(ord('A'), ord('Z') + 1)):
- files = files_by_letter.get(letter, [])
- kws = kws_by_letter.get(letter, [])
- if not files and not kws:
- continue
-
- index_content += f"## {letter}\n\n"
-
- if files:
- index_content += "**Files:**\n\n"
- for title, path in sorted(files, key=lambda x: x[0].lower()):
- index_content += f"* [{title}]({path})\n"
- index_content += "\n"
-
- if kws:
- index_content += "**Keywords:**\n\n"
- for kw in sorted(kws, key=str.lower):
- linked_titles = ", ".join(
- f"[{title_map[p]}]({p})" for p in keyword_map[kw]
- )
- index_content += f"* **{kw}** — {linked_titles}\n"
- index_content += "\n"
-
- return index_content
-
-
-# ---------------------------------------------------------------------------
-# Main
-# ---------------------------------------------------------------------------
-
-def main():
- docs_dir = 'docs'
-
- if not os.path.exists(docs_dir):
- print(f"Error: '{docs_dir}' not found.")
- return
-
- db_terms = load_db_terms() # lower -> original
- patterns = build_term_patterns(db_terms)
-
- file_data, keyword_map, title_map = scan_markdown_files(docs_dir, db_terms, patterns)
- index_content = generate_alphabetical_index(file_data, keyword_map, title_map)
-
- index_path = os.path.join(docs_dir, 'index-keywords.md')
- with open(index_path, 'w', encoding='utf-8') as f:
- f.write(index_content)
-
- print(f"A–Z index with titles and keyword links generated: {index_path}")
-
-
-if __name__ == "__main__":
- main()
diff --git a/mkdocs-base.yml b/mkdocs-base.yml
index c7d4f6dc5e7..5131082f737 100644
--- a/mkdocs-base.yml
+++ b/mkdocs-base.yml
@@ -215,7 +215,6 @@ nav:
- percona-sequence-table.md
- procfs-plugin.md
- proxy-protocol-support.md
- - sequence-table.md
- slowlog-rotation.md
- threadpool.md
- trigger-updates.md
@@ -262,6 +261,8 @@ nav:
- upgrade.md
- Understand what's changing:
- percona-toolkit-9.7-updates.md
+ - MySQL 9.x series:
+ - whats-new-mysql-9.md
- upgrade-checklist-9.7.md
- upgrade-strategies.md
- mysql-upgrade-paths.md
@@ -423,5 +424,5 @@ nav:
- copyright-and-licensing-information.md
- glossary.md
- ai-docs.md
- - Topic Index: index-keywords.md
+ - Topic Index: index-contents.md
# - Version Selector: "../"
diff --git a/sync-docs-index.ps1 b/sync-docs-index.ps1
new file mode 100644
index 00000000000..f99046ae02b
--- /dev/null
+++ b/sync-docs-index.ps1
@@ -0,0 +1,103 @@
+# -----------------------------
+# CONFIG
+# -----------------------------
+$docsPath = Join-Path $PSScriptRoot "docs"
+$outputFile = Join-Path $docsPath "index-contents.md"
+
+# -----------------------------
+# HELPERS
+# -----------------------------
+function Get-Heading {
+ param ([string]$filePath)
+
+ foreach ($line in Get-Content $filePath) {
+ if ($line -match '^\s*#\s+(.+)') {
+ return $matches[1].Trim()
+ }
+ }
+
+ return [System.IO.Path]::GetFileNameWithoutExtension($filePath)
+}
+
+function Should-Ignore {
+ param ([string]$path)
+
+ return $path -match "[\\/](release-notes)[\\/]"
+}
+
+function Normalize-RelativePath {
+ param ([string]$fullPath)
+
+ $relative = $fullPath.Substring($docsPath.Length)
+
+ return ($relative -replace '\\','/').TrimStart('/')
+}
+
+# -----------------------------
+# COLLECT FILES
+# -----------------------------
+$files = Get-ChildItem $docsPath -Recurse -File -Filter "*.md" |
+ Where-Object {
+ $_.Name -ne "index-contents.md" -and
+ -not (Should-Ignore $_.FullName)
+ }
+
+# -----------------------------
+# BUILD TOPICS + VALIDATION
+# -----------------------------
+$topics = @()
+$brokenLinks = @()
+
+foreach ($file in $files) {
+
+ $title = Get-Heading $file.FullName
+ $relative = Normalize-RelativePath $file.FullName
+ $link = "docs/$relative"
+
+ # VALIDATION: ensure file still exists
+ if (-not (Test-Path $file.FullName)) {
+ $brokenLinks += $link
+ continue
+ }
+
+ $topics += [PSCustomObject]@{
+ Title = $title
+ Path = "./$relative"
+ }
+}
+
+# -----------------------------
+# SORT (GLOBAL ALPHABETICAL)
+# -----------------------------
+$topics = $topics | Sort-Object Title
+
+# -----------------------------
+# RENDER INDEX
+# -----------------------------
+$output = @()
+$output += "# Documentation Index"
+$output += ""
+$output += "## Topics"
+$output += ""
+
+foreach ($t in $topics) {
+ $output += "- [$($t.Title)]($($t.Path))"
+}
+
+# -----------------------------
+# WRITE INDEX
+# -----------------------------
+$output | Set-Content -Path $outputFile -Encoding UTF8
+
+# -----------------------------
+# REPORT BROKEN LINKS
+# -----------------------------
+if ($brokenLinks.Count -gt 0) {
+ Write-Warning "Broken links detected:"
+ $brokenLinks | ForEach-Object { Write-Warning " - $_" }
+}
+else {
+ Write-Host "All links validated successfully."
+}
+
+Write-Host "Index generated at: $outputFile"
\ No newline at end of file