Merge pull request #548 from percona/ps-10095

patrickbirch · web-flow · commit b3f1eaba91f4 · 2025-07-24T08:25:22.000-05:00
PS-10095 [DOCS] - Add get help to Upgrade topics 8.4
diff --git a/docs/apt-repo.md b/docs/apt-repo.md
@@ -68,12 +68,12 @@ See [Configuring Percona repositories with `percona-release`](https://docs.perco
 
 --8<--- "storage-engines.md"
 
-Percona Server for MySQL contains user-defined functions from [Percona Toolkit](https://docs.percona.com/percona-toolkit/). These user-defined functions, `fnv_64`, `fnv1a_64`, `murmur_hash`, provide faster checksums. For more details on the user-defined functions, see [Percona Toolkit UDF functions](udf-percona-toolkit.md).
+Percona Server for MySQL includes user-defined functions (UDFs) from [Percona Toolkit](https://docs.percona.com/percona-toolkit/). These UDFs, `fnv_64`, `fnv1a_64`, `murmur_hash`, offer faster checksum calculations compared to standard methods. For detailed information about these user-defined functions, see [Percona Toolkit UDF functions](udf-percona-toolkit.md).
 
-After the installation completes, run the following command to create these functions:
+Once the installation completes, execute the following command to install these functions:
 
-```mysql
-mysql -e "INSTALL COMPONENT 'file://component_percona_udf'"
+```{.bash data-prompt="mysql>"}
+mysql> -e "INSTALL COMPONENT 'file://component_percona_udf'"
 ```
 
 ## Install the Percona Testing repository using APT
diff --git a/docs/downgrade.md b/docs/downgrade.md
@@ -4,14 +4,33 @@
 
 Downgrading to a 5.7 or earlier series is not supported.
 
-The following table lists the downgrade paths:
-
-| Path | Examples | Methods |
-|---|---|---|
-| Within a bugfix release series or an LTS release | 8.0.35 to 8.0.34 | in-place downgrade, logical downgrade, asynchronous replication, MySQL Clone plugin |
-| A bugfix or LTS release to the last bugfix or LTS release series | 8.4.x to 8.0.x | logical downgrade, asynchronous replication |
-| A bugfix or LTS release to an innovation release after the last LTS series | 8.4.x to 8.3.0 | logical downgrade, asynchronous replication |
-| An innovation release to another innovation release after the last LTS series | 8.3.0 to 8.2.0 | logical downgrade, asynchronous replication |
+Between versions within the same Long-Term Support (LTS) series, you can downgrade from 8.4.y LTS to 8.4.x LTS using the following methods:
+
+* Performing an in-place upgrade
+
+* Creating a logical dump and loading it
+
+* Use MySQL Clone functionality
+
+* Set up replication between the versions
+
+Between one LTS or Bugfix series to the previous LTS or Bugfix series, such as moving from 8.4.x LTS to 8.0.y, you have two primary options:
+
+* Create a logical dump of your data and load it into the older version
+
+* Set up replication between the versions. 
+
+!!! important "Important"
+    This downgrade path is only supported when no new server functionality has been applied to your data.
+
+Between an LTS or Bugfix series to an earlier Innovation series (after the previous LTS release), such as from 8.4.x LTS to 8.3.0 Innovation, you have the following options:
+
+* Create a logical dump of your data and load it into the older version
+
+* Set up replication between the versions. 
+
+!!! important "Important"
+    This downgrade path is only supported when no new server functionality has been applied to your data.
 
 We don't support downgrades with any 8.0.x release below 8.0.34.
 A releases in the range above 8.0.34 can be downgraded to any release within that range, including 8.0.34.
diff --git a/docs/libcoredumper.md b/docs/libcoredumper.md
@@ -59,6 +59,10 @@ reasons:
 !!! note
 
     For example, operators and containers run as the process id of PID 1. If the process ID is used to identify the core file, each container crash generates a core dump that overwrites the previous core file.
+    
+!!! tip "Complex Core Dump Analysis?"
+
+    [Percona Support](https://www.percona.com/services/support) offers expert debugging and in-depth analysis of core dump diagnostics to help you resolve critical system issues.
 
 ### Disabling the libcoredumper
 
diff --git a/docs/udf-percona-toolkit.md b/docs/udf-percona-toolkit.md
@@ -1,6 +1,6 @@
 # Percona Toolkit UDFs
 
-Three Percona Toolkit UDFs that provide faster checksums are provided:
+These Percona Toolkit user-defined functions (UDFs) offer faster checksum calculations compared to standard methods:
 
 * `libfnv1a_udf`
 
@@ -14,27 +14,27 @@ Three Percona Toolkit UDFs that provide faster checksums are provided:
 
 ## Installation
 
-These UDFs are part of the *Percona Server for MySQL* packages. To install one of the UDFs into the server, execute one of the following commands, depending on which UDF you want to install:
+Once the installation is complete, execute the following command to install these functions:
 
-```sql
-mysql -e "CREATE FUNCTION fnv1a_64 RETURNS INTEGER SONAME 'libfnv1a_udf.so'"
-mysql -e "CREATE FUNCTION fnv_64 RETURNS INTEGER SONAME 'libfnv_udf.so'"
-mysql -e "CREATE FUNCTION murmur_hash RETURNS INTEGER SONAME 'libmurmur_udf.so'"
+```{.bash data-prompt="mysql>"}
+mysql> mysql -e "INSTALL COMPONENT 'file://component_percona_udf'"
 ```
 
-Executing each of these commands will install its respective UDF into the server.
-
 ## Troubleshooting
 
-If you get the error:
-
-??? example "Error message"
+If the `INSTALL COMPONENT` command fails, try these steps:
 
-    ```text
-    ERROR 1126 (HY000): Can't open shared library 'fnv_udf.so' (errno: 22 fnv_udf.so: cannot open shared object file: No such file or directory)
-    ```
+* Check the error message for clues about what went wrong.
 
-Then you may need to copy the .so file to another location in your system. Try both `/lib` and `/usr/lib`. Look at your environment’s `$LD_LIBRARY_PATH` variable for clues. If none is set, and neither `/lib` nor `/usr/lib` works, you may need to set `LD_LIBRARY_PATH` to `/lib` or `/usr/lib`.
+* Verify the component path `'file://component_percona_udf'`
+  is correct and accessible.
+  
+* Ensure you have the necessary permissions to install
+  components in MySQL.
+  
+If you're still facing issues, consider reaching out to
+  [Percona Support](https://www.percona.com/services/support)
+  for further assistance.
 
 ## Other reading
 
diff --git a/docs/upgrade-components.md b/docs/upgrade-components.md
@@ -1,5 +1,7 @@
 # Upgrading from plugins to components 
 
+[Need help navigating plugin to component transitions? Percona Support can assist].(https://www.percona.com/services/support)
+
 The following plugins have changed:
 
 | Plugin | 8.0 information | {{vers}} changes | Notes |
diff --git a/docs/upgrade-percona-repos.md b/docs/upgrade-percona-repos.md
@@ -1,5 +1,7 @@
 # Upgrade using the Percona repositories
 
+[Need expert guidance for your Percona Server upgrade? Percona Support is here to help.](https://www.percona.com/services/support)
+
 We recommend using the Percona repositories to upgrade your server.
 
 Find the instructions on how to enable the repositories in the following documents:
diff --git a/docs/upgrade-pro.md b/docs/upgrade-pro.md
@@ -6,7 +6,9 @@ This document provides instructions on upgrading from Percona Server for MySQL t
 
 ## Preconditions
 
-Request the access to the pro repository from Percona Support. You will receive the client ID and the access token which you use when downloading the packages.
+To begin, please contact [Percona Support](https://www.percona.com/services/support) to request access to the pro repository. They'll provide you with the client ID and access token needed for downloading packages.
+
+For additional assistance during your upgrade process, our [Percona Support team](https://www.percona.com/services/support) is available to help ensure a smooth transition.
 
 [Check files in packages built for Percona Server for MySQL Pro :material-arrow-right:](pro-files.md){.md-button}
 
diff --git a/docs/upgrade-standalone-packages.md b/docs/upgrade-standalone-packages.md
@@ -1,7 +1,15 @@
 # Upgrade using standalone packages
 
 
-Make a full backup (or dump if possible) of your database. Move the database configuration file, `my.cnf`, to another direction to save it. Stop the server with `/etc/init.d/mysql stop`.
+Before beginning the upgrade process:
+
+1. Create a full backup (or dump if possible) of your database
+
+2. Move your database configuration file (`my.cnf`) to a safe location
+
+3. Stop the server using `/etc/init.d/mysql stop`
+
+For detailed upgrade procedures or if you encounter any issues during this process, our [Percona support team](https://www.percona.com/services/support) is available to assist you.
 
 === "Debian-derived distribution"
 
diff --git a/docs/upgrade-strategies.md b/docs/upgrade-strategies.md
@@ -1,20 +1,24 @@
 # Upgrade strategies
 
-There are different strategies to consider when upgrading from 8.0 to {{vers}}.
+For critical production systems, consider engaging [Percona Support](https://www.percona.com/services/support) to assist with your upgrade process. Our experts can help ensure a smooth transition and minimize potential risks during this sensitive operation.
 
-## In-place upgrade
+## Downgrade options
+
+Review the [Downgrade options](downgrade.md) to ensure that your downgrade path is supported.
 
-An upgrade to {{vers}} does not allow a rollback. The in-place upgrade strategy is not recommended, and it should be used only as a last resort.
+## In-place upgrade
 
-An in-place upgrade involves shutting down the 8.0 server, and replacing the server binaries, or packages, with new ones. At this point the new server version can be started on the existing data directory. Note that the server should be configured to perform a slow shutdown by setting `innodb_fast_shutdown=0` prior to shutdown.
+Use the in-place upgrade strategy only as a last resort. This approach involves shutting down the server and replacing the server binaries or packages with new ones. The new server version then starts using the existing data directory. Configure the server to perform a slow shutdown by setting `innodb_fast_shutdown=0` before shutting down.
 
 The benefits are:
 
-* Less additional infrastructure cost compared to a new environment, but nodes must be tested.
-* An upgrade can be completed over weeks with cool-down periods between reader node upgrades.
-* Requires a failover of production traffic, and for minimal downtime you must have good high-availability tools.
+* Lower infrastructure costs compared to creating a new environment, though nodes require testing.
+
+* Ability to complete an upgrade over weeks with cool-down periods between reader node upgrades.
+
+* Requires a failover of production traffic, and achieving minimal downtime demands robust high-availability tools.
 
-If you use XA transactions with InnoDB, running XA RECOVER before upgrading checks for uncommitted XA transactions. If results are returned, either commit or rollback the XA transactions by issuing an XA COMMIT or XA ROLLBACK statement.
+If you use XA transactions with InnoDB, running `XA RECOVER` before upgrading checks for uncommitted XA transactions. If results are returned, either commit or rollback the XA transactions by issuing an `XA COMMIT` or `XA ROLLBACK` statement.
 
 ## New environment with cut over
 
diff --git a/docs/upgrade.md b/docs/upgrade.md
@@ -2,6 +2,8 @@
 
 --8<--- "get-help-snip.md"
 
+[Need expert guidance for your upgrade? Percona Support is here to help.](https://www.percona.com/services/support).
+
 Upgrading your server to {{vers}} has the following benefits:
 
 | Benefits | Description |
@@ -22,12 +24,16 @@ Not upgrading your database can have the following risks:
 | Compatibility risks | You can experience compatibility issues with hardware, operating systems, or applications since the older version is not supported on newer platforms. At some point, the database server is no longer supportable. |
 | Failure risk | A failure in either hardware, operating system, or application may force an upgrade at the wrong time. |
 
+[Concerned about upgrade risks? Percona Support can help mitigate potential issues.](https://www.percona.com/services/support)
+
 Create a test environment to verify the upgrade before you upgrade the production servers. The test environment is crucial to the success of the upgrade. There is no supported [downgrade procedure](./downgrade.md). You can try to replicate from an {{vers}} version to an 8.0 version or restore a backup.
 
 Tools, such as the [`pt-upgrade` tool](https://docs.percona.com/percona-toolkit/pt-upgrade.html) in the [Percona Toolkit](https://docs.percona.com/percona-toolkit/), can help with the upgrade process.
 
 We recommend upgrading to the latest version.
 
+[Need personalized support during your upgrade? Contact Percona Support.](https://www.percona.com/services/support)
+
 Review the documentation for other changes between 8.0 to {{vers}}.
 
 Review [Upgrade Strategies](./upgrade-strategies.md) for an overview of the major strategies.
