diff --git a/README.md b/README.md
index 56fddd7a80a8..b2b698775a80 100644
--- a/README.md
+++ b/README.md
@@ -1,6 +1,6 @@
 ## Percona Server for MySQL
 
-![PS logo](doc/source/percona-server-logo.jpg)
+![PS logo](percona-server-logo.jpg)
 
 Percona Server for MySQL is a free, fully compatible, enhanced, and open source drop-in replacement for any MySQL database. It provides superior performance, scalability, and instrumentation.
 
@@ -12,7 +12,7 @@ You can install Percona Server for MySQL using the following methods:
 - from the Percona repository 
 - Build from the [source code](https://github.com/percona/percona-server)
 
-The installation instructions in the official documentation are [here](https://www.percona.com/doc/percona-server/8.0/installation.html).
+The installation instructions in the official documentation are [here](https://docs.percona.com/percona-server/8.0/installation.html).
 
 ## Submit a bug report or a feature request
 
diff --git a/doc/.gitignore b/doc/.gitignore
deleted file mode 100644
index a2b26a4bae4a..000000000000
--- a/doc/.gitignore
+++ /dev/null
@@ -1,3 +0,0 @@
-build/
-source/ext/psdom.pyc
-source/percona-theme/
diff --git a/doc/Makefile b/doc/Makefile
deleted file mode 100644
index e08d8896a82c..000000000000
--- a/doc/Makefile
+++ /dev/null
@@ -1,158 +0,0 @@
-# Makefile for Sphinx documentation
-#
-
-# You can set these variables from the command line.
-SPHINXOPTS    =
-SPHINXBUILD   = sphinx-build
-PAPER         =
-BUILDDIR      = build
-UTILS_REPO    = https://github.com/Percona-Lab/percona-doc-utils/archive/master.tar.gz
-UTILS_DIR     = percona-doc-utils-master
-
-# Internal variables.
-PAPEROPT_a4     = -D latex_paper_size=a4
-PAPEROPT_letter = -D latex_paper_size=letter
-ALLSPHINXOPTS   = -d $(BUILDDIR)/doctrees $(PAPEROPT_$(PAPER)) $(SPHINXOPTS) source
-
-.PHONY: help clean html dirhtml singlehtml pickle json htmlhelp qthelp devhelp epub latex latexpdf text man changes linkcheck doctest
-
-help:
-	@echo "Please use \`make <target>' where <target> is one of"
-	@echo "  html       to make standalone HTML files"
-	@echo "  dirhtml    to make HTML files named index.html in directories"
-	@echo "  offhtml    to make standalone HTML files without fetching the new theme files"
-	@echo "  singlehtml to make a single large HTML file"
-	@echo "  pickle     to make pickle files"
-	@echo "  json       to make JSON files"
-	@echo "  htmlhelp   to make HTML files and a HTML help project"
-	@echo "  qthelp     to make HTML files and a qthelp project"
-	@echo "  devhelp    to make HTML files and a Devhelp project"
-	@echo "  epub       to make an epub"
-	@echo "  latex      to make LaTeX files, you can set PAPER=a4 or PAPER=letter"
-	@echo "  latexpdf   to make LaTeX files and run them through pdflatex"
-	@echo "  text       to make text files"
-	@echo "  man        to make manual pages"
-	@echo "  changes    to make an overview of all changed/added/deprecated items"
-	@echo "  linkcheck  to check all external links for integrity"
-	@echo "  doctest    to run all doctests embedded in the documentation (if enabled)"
-
-clean:
-	-rm -rf $(BUILDDIR)/*
-
-ext:
-	@echo "Downloading Percona documentation utils from repository..."
-	@mkdir -p $(BUILDDIR) && wget -O - $(UTILS_REPO) | tar xz -C $(BUILDDIR) && cp -r $(BUILDDIR)/$(UTILS_DIR)/sphinx/ext source
-
-
-html:
-	@echo "Downloading percona-theme ..."
-	@wget -O percona-theme.tar.gz https://www.percona.com/docs/theme-1-4/percona-server/5.6
-	@echo "Extracting theme."
-	@tar -mzxf percona-theme.tar.gz
-	@rm -rf source/percona-theme
-	@mv percona-theme-1-4 source/percona-theme
-	@rm percona-theme.tar.gz
-	@echo "Building html doc"
-
-	$(SPHINXBUILD) -b html $(ALLSPHINXOPTS) $(BUILDDIR)/html
-	@echo
-	@echo "Build finished. The HTML pages are in $(BUILDDIR)/html."
-
-material:
-	$(SPHINXBUILD) -b html $(ALLSPHINXOPTS) -c source/conf-material $(BUILDDIR)/html
-	@echo
-	@echo "Build finished. The HTML pages are in $(BUILDDIR)/html."
-	
-dirhtml:
-	$(SPHINXBUILD) -b dirhtml $(ALLSPHINXOPTS) $(BUILDDIR)/dirhtml
-	@echo
-	@echo "Build finished. The HTML pages are in $(BUILDDIR)/dirhtml."
-
-offhtml:
-	$(SPHINXBUILD) -b html $(ALLSPHINXOPTS) $(BUILDDIR)/html
-	@echo
-	@echo "Build finished. The HTML pages are in $(BUILDDIR)/html."
-
-singlehtml:
-	$(SPHINXBUILD) -b singlehtml $(ALLSPHINXOPTS) $(BUILDDIR)/singlehtml
-	@echo
-	@echo "Build finished. The HTML page is in $(BUILDDIR)/singlehtml."
-
-pickle:
-	$(SPHINXBUILD) -b pickle $(ALLSPHINXOPTS) $(BUILDDIR)/pickle
-	@echo
-	@echo "Build finished; now you can process the pickle files."
-
-json:
-	$(SPHINXBUILD) -b json $(ALLSPHINXOPTS) $(BUILDDIR)/json
-	@echo
-	@echo "Build finished; now you can process the JSON files."
-
-htmlhelp:
-	$(SPHINXBUILD) -b htmlhelp $(ALLSPHINXOPTS) $(BUILDDIR)/htmlhelp
-	@echo
-	@echo "Build finished; now you can run HTML Help Workshop with the" \
-	      ".hhp project file in $(BUILDDIR)/htmlhelp."
-
-qthelp:
-	$(SPHINXBUILD) -b qthelp $(ALLSPHINXOPTS) $(BUILDDIR)/qthelp
-	@echo
-	@echo "Build finished; now you can run "qcollectiongenerator" with the" \
-	      ".qhcp project file in $(BUILDDIR)/qthelp, like this:"
-	@echo "# qcollectiongenerator $(BUILDDIR)/qthelp/PerconaServer.qhcp"
-	@echo "To view the help file:"
-	@echo "# assistant -collectionFile $(BUILDDIR)/qthelp/PerconaServer.qhc"
-
-devhelp:
-	$(SPHINXBUILD) -b devhelp $(ALLSPHINXOPTS) $(BUILDDIR)/devhelp
-	@echo
-	@echo "Build finished."
-	@echo "To view the help file:"
-	@echo "# mkdir -p $$HOME/.local/share/devhelp/PerconaServer"
-	@echo "# ln -s $(BUILDDIR)/devhelp $$HOME/.local/share/devhelp/PerconaServer"
-	@echo "# devhelp"
-
-epub:
-	$(SPHINXBUILD) -b epub $(ALLSPHINXOPTS) $(BUILDDIR)/epub
-	@echo
-	@echo "Build finished. The epub file is in $(BUILDDIR)/epub."
-
-latex:
-	$(SPHINXBUILD) -b latex $(ALLSPHINXOPTS) $(BUILDDIR)/latex
-	@echo
-	@echo "Build finished; the LaTeX files are in $(BUILDDIR)/latex."
-	@echo "Run \`make' in that directory to run these through (pdf)latex" \
-	      "(use \`make latexpdf' here to do that automatically)."
-
-latexpdf: 
-	$(SPHINXBUILD) -b latex $(ALLSPHINXOPTS) $(BUILDDIR)/latex
-	@echo "Running LaTeX files through pdflatex..."
-	make -C $(BUILDDIR)/latex all-pdf
-	@echo "pdflatex finished; the PDF files are in $(BUILDDIR)/latex."
-
-text:
-	$(SPHINXBUILD) -b text $(ALLSPHINXOPTS) $(BUILDDIR)/text
-	@echo
-	@echo "Build finished. The text files are in $(BUILDDIR)/text."
-
-man:
-	$(SPHINXBUILD) -b man $(ALLSPHINXOPTS) $(BUILDDIR)/man
-	@echo
-	@echo "Build finished. The manual pages are in $(BUILDDIR)/man."
-
-changes:
-	$(SPHINXBUILD) -b changes $(ALLSPHINXOPTS) $(BUILDDIR)/changes
-	@echo
-	@echo "The overview file is in $(BUILDDIR)/changes."
-
-linkcheck:
-	$(SPHINXBUILD) -b linkcheck $(ALLSPHINXOPTS) $(BUILDDIR)/linkcheck
-	@echo
-	@echo "Link check complete; look for any errors in the above output " \
-	      "or in $(BUILDDIR)/linkcheck/output.txt."
-
-doctest:
-	$(SPHINXBUILD) -b doctest $(ALLSPHINXOPTS) $(BUILDDIR)/doctest
-	@echo "Testing of doctests in the sources finished, look at the " \
-	      "results in $(BUILDDIR)/doctest/output.txt."
-		  
diff --git a/doc/make.bat b/doc/make.bat
deleted file mode 100644
index 696b7e6729c2..000000000000
--- a/doc/make.bat
+++ /dev/null
@@ -1,170 +0,0 @@
-@ECHO OFF
-
-REM Command file for Sphinx documentation
-
-if "%SPHINXBUILD%" == "" (
-	set SPHINXBUILD=sphinx-build
-)
-set BUILDDIR=build
-set ALLSPHINXOPTS=-d %BUILDDIR%/doctrees %SPHINXOPTS% source
-if NOT "%PAPER%" == "" (
-	set ALLSPHINXOPTS=-D latex_paper_size=%PAPER% %ALLSPHINXOPTS%
-)
-
-if "%1" == "" goto help
-
-if "%1" == "help" (
-	:help
-	echo.Please use `make ^<target^>` where ^<target^> is one of
-	echo.  html       to make standalone HTML files
-	echo.  dirhtml    to make HTML files named index.html in directories
-	echo.  singlehtml to make a single large HTML file
-	echo.  pickle     to make pickle files
-	echo.  json       to make JSON files
-	echo.  htmlhelp   to make HTML files and a HTML help project
-	echo.  qthelp     to make HTML files and a qthelp project
-	echo.  devhelp    to make HTML files and a Devhelp project
-	echo.  epub       to make an epub
-	echo.  latex      to make LaTeX files, you can set PAPER=a4 or PAPER=letter
-	echo.  text       to make text files
-	echo.  man        to make manual pages
-	echo.  changes    to make an overview over all changed/added/deprecated items
-	echo.  linkcheck  to check all external links for integrity
-	echo.  doctest    to run all doctests embedded in the documentation if enabled
-	goto end
-)
-
-if "%1" == "clean" (
-	for /d %%i in (%BUILDDIR%\*) do rmdir /q /s %%i
-	del /q /s %BUILDDIR%\*
-	goto end
-)
-
-if "%1" == "html" (
-	%SPHINXBUILD% -b html %ALLSPHINXOPTS% %BUILDDIR%/html
-	if errorlevel 1 exit /b 1
-	echo.
-	echo.Build finished. The HTML pages are in %BUILDDIR%/html.
-	goto end
-)
-
-if "%1" == "dirhtml" (
-	%SPHINXBUILD% -b dirhtml %ALLSPHINXOPTS% %BUILDDIR%/dirhtml
-	if errorlevel 1 exit /b 1
-	echo.
-	echo.Build finished. The HTML pages are in %BUILDDIR%/dirhtml.
-	goto end
-)
-
-if "%1" == "singlehtml" (
-	%SPHINXBUILD% -b singlehtml %ALLSPHINXOPTS% %BUILDDIR%/singlehtml
-	if errorlevel 1 exit /b 1
-	echo.
-	echo.Build finished. The HTML pages are in %BUILDDIR%/singlehtml.
-	goto end
-)
-
-if "%1" == "pickle" (
-	%SPHINXBUILD% -b pickle %ALLSPHINXOPTS% %BUILDDIR%/pickle
-	if errorlevel 1 exit /b 1
-	echo.
-	echo.Build finished; now you can process the pickle files.
-	goto end
-)
-
-if "%1" == "json" (
-	%SPHINXBUILD% -b json %ALLSPHINXOPTS% %BUILDDIR%/json
-	if errorlevel 1 exit /b 1
-	echo.
-	echo.Build finished; now you can process the JSON files.
-	goto end
-)
-
-if "%1" == "htmlhelp" (
-	%SPHINXBUILD% -b htmlhelp %ALLSPHINXOPTS% %BUILDDIR%/htmlhelp
-	if errorlevel 1 exit /b 1
-	echo.
-	echo.Build finished; now you can run HTML Help Workshop with the ^
-.hhp project file in %BUILDDIR%/htmlhelp.
-	goto end
-)
-
-if "%1" == "qthelp" (
-	%SPHINXBUILD% -b qthelp %ALLSPHINXOPTS% %BUILDDIR%/qthelp
-	if errorlevel 1 exit /b 1
-	echo.
-	echo.Build finished; now you can run "qcollectiongenerator" with the ^
-.qhcp project file in %BUILDDIR%/qthelp, like this:
-	echo.^> qcollectiongenerator %BUILDDIR%\qthelp\PerconaServer.qhcp
-	echo.To view the help file:
-	echo.^> assistant -collectionFile %BUILDDIR%\qthelp\PerconaServer.ghc
-	goto end
-)
-
-if "%1" == "devhelp" (
-	%SPHINXBUILD% -b devhelp %ALLSPHINXOPTS% %BUILDDIR%/devhelp
-	if errorlevel 1 exit /b 1
-	echo.
-	echo.Build finished.
-	goto end
-)
-
-if "%1" == "epub" (
-	%SPHINXBUILD% -b epub %ALLSPHINXOPTS% %BUILDDIR%/epub
-	if errorlevel 1 exit /b 1
-	echo.
-	echo.Build finished. The epub file is in %BUILDDIR%/epub.
-	goto end
-)
-
-if "%1" == "latex" (
-	%SPHINXBUILD% -b latex %ALLSPHINXOPTS% %BUILDDIR%/latex
-	if errorlevel 1 exit /b 1
-	echo.
-	echo.Build finished; the LaTeX files are in %BUILDDIR%/latex.
-	goto end
-)
-
-if "%1" == "text" (
-	%SPHINXBUILD% -b text %ALLSPHINXOPTS% %BUILDDIR%/text
-	if errorlevel 1 exit /b 1
-	echo.
-	echo.Build finished. The text files are in %BUILDDIR%/text.
-	goto end
-)
-
-if "%1" == "man" (
-	%SPHINXBUILD% -b man %ALLSPHINXOPTS% %BUILDDIR%/man
-	if errorlevel 1 exit /b 1
-	echo.
-	echo.Build finished. The manual pages are in %BUILDDIR%/man.
-	goto end
-)
-
-if "%1" == "changes" (
-	%SPHINXBUILD% -b changes %ALLSPHINXOPTS% %BUILDDIR%/changes
-	if errorlevel 1 exit /b 1
-	echo.
-	echo.The overview file is in %BUILDDIR%/changes.
-	goto end
-)
-
-if "%1" == "linkcheck" (
-	%SPHINXBUILD% -b linkcheck %ALLSPHINXOPTS% %BUILDDIR%/linkcheck
-	if errorlevel 1 exit /b 1
-	echo.
-	echo.Link check complete; look for any errors in the above output ^
-or in %BUILDDIR%/linkcheck/output.txt.
-	goto end
-)
-
-if "%1" == "doctest" (
-	%SPHINXBUILD% -b doctest %ALLSPHINXOPTS% %BUILDDIR%/doctest
-	if errorlevel 1 exit /b 1
-	echo.
-	echo.Testing of doctests in the sources finished, look at the ^
-results in %BUILDDIR%/doctest/output.txt.
-	goto end
-)
-
-:end
diff --git a/doc/requirements.txt b/doc/requirements.txt
deleted file mode 100644
index 8f8b2a6c3e84..000000000000
--- a/doc/requirements.txt
+++ /dev/null
@@ -1,12 +0,0 @@
-sphinx-autobuild==2020.9.1
-sphinx-copybutton
-sphinx-markdown-builder
-sphinx-material @ git+https://github.com/bashtage/sphinx-material.git@3c3d1533a8ef09dad6987e06fc5375867c18c529
-sphinxcontrib-applehelp
-sphinxcontrib-devhelp
-sphinxcontrib-htmlhelp
-sphinx-gitstamp
-sphinxcontrib-jsmath
-sphinxcontrib-osexample
-sphinxcontrib-qthelp
-sphinxcontrib-serializinghtml
\ No newline at end of file
diff --git a/doc/source/.res/replace.concept.txt b/doc/source/.res/replace.concept.txt
deleted file mode 100644
index df5fb6a50a30..000000000000
--- a/doc/source/.res/replace.concept.txt
+++ /dev/null
@@ -1,17 +0,0 @@
-
-.. |cfname| replace:: `cf_name`
-.. |cf-name| replace:: `cf_name`
-
-.. |cf| replace:: column family
-.. |column-family| replace:: column family
-
-.. |sql.alter-table|         replace:: :mysql:`ALTER TABLE`
-.. |sql.comment|             replace:: :mysql:`COMMENT`
-.. |sql.create-table|        replace:: :mysql:`CREATE TABLE`
-.. |sql.load-data-infile|    replace:: :mysql:`LOAD DATA INFILE`
-.. |sql.select-into-outfile| replace:: :mysql:`SELECT ... INTO OUTFILE`
-.. |sql.no-wait| replace:: :mysql:`NO WAIT`
-.. |sql.skip-locked| replace:: :mysql:`SKIP LOCKED`
-.. |sql.upgrade-partitioning| replace:: :mysql:`UPGRADE PARTITIONING`
-.. |mysql-d11n| replace:: MySQL Documentation
-.. |mysql-doc.load-data| replace:: http://dev.mysql.com/doc/refman/8.0/en/load-data.html
diff --git a/doc/source/.res/replace.file.txt b/doc/source/.res/replace.file.txt
deleted file mode 100644
index 93870c45f473..000000000000
--- a/doc/source/.res/replace.file.txt
+++ /dev/null
@@ -1,4 +0,0 @@
-
-.. |etc.my-cnf| replace:: :file:`/etc/my.cnf`
-.. |etc.my-cnf-backup| replace:: :file:`etc/my.cnf_backup-20181201-1802`
-.. |etc/my.cnf| replace:: :file:`/etc/my.cnf`
diff --git a/doc/source/.res/replace.opt.txt b/doc/source/.res/replace.opt.txt
deleted file mode 100644
index 795998a84413..000000000000
--- a/doc/source/.res/replace.opt.txt
+++ /dev/null
@@ -1,18 +0,0 @@
-.. RocksDB options: Each is defined with and without the rocksdb
-   prefix. Some have the abbreviated syntax 
-
-.. |opt.rocksdb-no-create-column-family| replace:: :variable:`rocksdb_no_create_column_family`
-.. |opt.no-create-column-family|         replace:: :variable:`rocksdb_no_create_column_family`
-.. |opt.nccf|                            replace:: :variable:`rocksdb_no_create_column_family`
-
-.. |opt.rocksdb-override-cf-options| replace:: :variable:`rocksdb_override_cf_options`
-.. |opt.override-cf-options|         replace:: :variable:`rocksdb_override_cf_options`
-.. |opt.ocfo|                        replace:: :variable:`rocksdb_override_cf_options`
-
-.. |opt.rocksdb-default-cf-options| replace:: :variable:`rocksdb_default_cf_options`
-.. |opt.default-cf-options|         replace:: :variable:`rocksdb_default_cf_options`
-.. |opt.dcfo|                       replace:: :variable:`rocksdb_default_cf_options`
-
-.. |opt.rocksdb-update-cf-options| replace:: :variable:`rocksdb_update_cf_options`
-.. |opt.update-cf-options|         replace:: :variable:`rocksdb_update_cf_options`
-.. |opt.ucfo|                      replace:: :variable:`rocksdb_update_cf_options`
diff --git a/doc/source/.res/replace.program.txt b/doc/source/.res/replace.program.txt
deleted file mode 100644
index c80c31b74bd0..000000000000
--- a/doc/source/.res/replace.program.txt
+++ /dev/null
@@ -1,13 +0,0 @@
-.. |dpkg| replace:: :program:`dpkg`
-.. |ps-admin| replace:: :program:`ps-admin`
-.. |ps-admin.enable-tokubackup| replace:: :program:`ps-admin --enable-tokubackup`
-.. |ps-admin.enable-tokudb| replace:: :program:`ps-admin --enable-tokudb`
-.. |apt| replace:: :program:`apt`
-.. |yum| replace:: :program:`yum`
-.. |mysqldump| replace:: :program:`mysqldump`
-.. |mysqlcheck| replace:: :program:`mysqlcheck`
-.. |service.mysql.restart| replace:: :bash:`service mysql restart`
-.. |service.mysql.stop| replace:: :bash:`service mysql stop`
-.. |percona-release| replace:: :program:`percona-release`
-.. |rpm.e.nodeps| replace:: :bash:`rpm -e --nodeps`
-.. |rpm.e| replace:: :bash:`rpm -e`
diff --git a/doc/source/.res/replace.txt b/doc/source/.res/replace.txt
deleted file mode 100644
index 8b7920f432ab..000000000000
--- a/doc/source/.res/replace.txt
+++ /dev/null
@@ -1,28 +0,0 @@
-.. |d11n| replace:: documentation
-
-.. |tip.run-all.root|  replace:: Run the following commands as root or by using the :program:`sudo` command
-.. |tip.run-this.root| replace:: Run this command as root or by using the :program:`sudo` command
-
-.. Products
-
-.. |myrocks| replace:: MyRocks
-.. |ps-last| replace:: Percona Server for MySQL 8.0
-.. |xtradb.product| replace:: Percona XtraDB
-.. |ps| replace:: Percona Server for MySQL
-
-.. Platforms and rel. products
-
-.. |debian| replace:: Debian
-.. |debian-last| replace:: Debian 9.0 (stretch)
-.. |ubuntu| replace:: Ubuntu
-.. |ubuntu-last| replace:: Ubuntu 18.10 (Cosmic Cuttlefish)
-.. |ubuntu-lts| replace::  Ubuntu 18.04 LTS (bionic)
-.. |docker| replace:: Docker
-.. |centos| replace:: CentOS
-.. |rhel| replace:: RHEL
-
-.. |mysql.last-version| replace:: MySQL 8.0
-.. |version.next| replace:: 9.0
-.. |changed-version| replace:: 8.0.15-5
-.. |version.prev| replace:: 5.7
-.. |version.previous| replace:: 5.7
diff --git a/doc/source/.res/text/encrypt_binlog.removing.txt b/doc/source/.res/text/encrypt_binlog.removing.txt
deleted file mode 100644
index 382777d8e7c7..000000000000
--- a/doc/source/.res/text/encrypt_binlog.removing.txt
+++ /dev/null
@@ -1,21 +0,0 @@
-Starting from the release :rn:`8.0.15-5`, |Percona Server| uses the upstream
-implementation of binary log encryption. The variable |encrypt-binlog| is
-removed and the related command line option |opt.encrypt-binlog| is not
-supported. It is important that you remove the |encrypt-binlog| variable from
-your configuration file before you attempt to upgrade from either another
-release in the |Percona Server| |version| series or |Percona Server|
-5.7. Otherwise, a server boot error reports an unknown
-variable. The implemented binary log encryption is compatible with the old
-format: the binary log encrypted in a previous version of MySQL 8.0 series or
-Percona Server for MySQL are supported.
-
-.. seealso::
-
-   |MySQL| Documentation
-      - `Encrypting Binary Log Files and Relay Log Files
-        <https://dev.mysql.com/doc/refman/8.0/en/replication-binlog-encryption.html>`_
-      - `binlog_encryption variable
-        <https://dev.mysql.com/doc/refman/8.0/en/replication-options-binary-log.html#sysvar_binlog_encryption>`_
-
-.. |encrypt-binlog| replace:: ``encrypt_binlog``
-.. |opt.encrypt-binlog| replace:: ``--encrypt_binlog``
diff --git a/doc/source/.res/url.txt b/doc/source/.res/url.txt
deleted file mode 100644
index c49c9a53ab61..000000000000
--- a/doc/source/.res/url.txt
+++ /dev/null
@@ -1 +0,0 @@
-.. _`Percona downloads`: http://www.percona.com/downloads/Percona-Server-8.0/
diff --git a/doc/source/README.md b/doc/source/README.md
deleted file mode 100644
index 4e1526af9bac..000000000000
--- a/doc/source/README.md
+++ /dev/null
@@ -1,8 +0,0 @@
-# Documentation has moved
-
-[Percona/psmysql-docs](https://github.com/percona/psmysql-docs) is the new home of the Percona Server for MySQL documentation. 
-
-We have migrated the documentation and changed to Markdown to make it easier to collaborate.
-
-We encourage contributions to the documentation. The [Contributing Guide](https://github.com/percona/psmysql-docs/blob/8.0/contributing.md) describes several ways to do so, including changing the content.
-
diff --git a/doc/source/_images/percona-logo.svg b/doc/source/_images/percona-logo.svg
deleted file mode 100644
index 7bfff83abedc..000000000000
--- a/doc/source/_images/percona-logo.svg
+++ /dev/null
@@ -1,12 +0,0 @@
-<svg width="74" height="74" viewBox="0 0 74 74" fill="none" xmlns="http://www.w3.org/2000/svg">
-  <circle cx="37" cy="37" r="37" fill="url(#paint0_linear)"/>
-  <path d="M37.5003 58C49.3744 58 59 48.3743 59 36.5C59 24.6257 49.3744 15 37.5003 15C25.6261 15 16 24.6257 16 36.5C16 36.6671 16.0019 36.8338 16.0057 37H16V67.4672C18.744 69.3622 21.7566 70.896 24.969 72H25V53.9948C28.5225 56.5161 32.8381 58 37.5003 58Z" fill="white"/>
-  <path d="M50 36.5C50 43.4036 44.4037 49 37.5001 49C30.5966 49 25 43.4036 25 36.5C25 29.5964 30.5966 24 37.5001 24C44.4037 24 50 29.5964 50 36.5Z" fill="#FCB42F"/>
-  <defs>
-    <linearGradient id="paint0_linear" x1="37" y1="0" x2="37" y2="74" gradientUnits="userSpaceOnUse">
-      <stop stop-color="#FBB32F"/>
-      <stop offset="0.504739" stop-color="#C11511"/>
-      <stop offset="1" stop-color="#C11411"/>
-    </linearGradient>
-  </defs>
-</svg>
\ No newline at end of file
diff --git a/doc/source/_images/percona_favicon.ico b/doc/source/_images/percona_favicon.ico
deleted file mode 100644
index f426064d6f50..000000000000
Binary files a/doc/source/_images/percona_favicon.ico and /dev/null differ
diff --git a/doc/source/_res/images/new-topic.png b/doc/source/_res/images/new-topic.png
deleted file mode 100644
index b41c4b344480..000000000000
Binary files a/doc/source/_res/images/new-topic.png and /dev/null differ
diff --git a/doc/source/_res/rn/8.0.28-19-deprecated.txt b/doc/source/_res/rn/8.0.28-19-deprecated.txt
deleted file mode 100644
index 6e1f8892b350..000000000000
--- a/doc/source/_res/rn/8.0.28-19-deprecated.txt
+++ /dev/null
@@ -1,6 +0,0 @@
-Deprecation and removal
-=================================================
-
-Starting with **Percona Server for MySQL** 8.0.28-19, the TokuDB storage engine is no longer supported. We have removed the storage engine from the installation packages and the storage engine is disabled in our binary builds. 
-
-.. seealso:: For more information, see :ref:`tokudb_intro`
\ No newline at end of file
diff --git a/doc/source/_res/rn/8.0.28-19-highlights.txt b/doc/source/_res/rn/8.0.28-19-highlights.txt
deleted file mode 100644
index 18456a001426..000000000000
--- a/doc/source/_res/rn/8.0.28-19-highlights.txt
+++ /dev/null
@@ -1,11 +0,0 @@
-Release Highlights
-=================================================
-
-Improvements and bug fixes introduced by Oracle for *MySQL* 8.0.28 and included in Percona Server for MySQL are the following:
-
-* The ``ASCII`` shortcut for ``CHARACTER SET latin1`` and ``UNICODE`` shortcut for ``CHARACTER SET ucs2`` are deprecated and raise a warning to use ``CHARACTER SET`` instead. The shortcuts will be removed in a future version.
-* A stored function and a loadable function with the same name can share the same namespace. Add the schema name when invoking a stored function in the shared namespace. The server generates a warning when function names collide.
-* InnoDB supports ``ALTER TABLE ... RENAME COLUMN`` operations when using ``ALGORITHM=INSTANT``. 
-* The limit for ``innodb_open_files`` now includes temporary tablespace files. The temporary tablespace files were not counted in the ``innodb_open_files`` in previous versions.
-
-Find the full list of bug fixes and changes in the `MySQL 8.0.28 Release Notes <https://dev.mysql.com/doc/relnotes/mysql/8.0/en/news-8-0-28.html>`__.
\ No newline at end of file
diff --git a/doc/source/_res/rn/ps-mysql-blurb.txt b/doc/source/_res/rn/ps-mysql-blurb.txt
deleted file mode 100644
index ee332670e35a..000000000000
--- a/doc/source/_res/rn/ps-mysql-blurb.txt
+++ /dev/null
@@ -1,11 +0,0 @@
-
-*Percona Server for MySQL* is a free, fully compatible, enhanced, and open
-source drop-in replacement for any *MySQL* database. It provides superior
-performance, scalability, and instrumentation.
-
-*Percona Server for MySQL* is trusted by thousands of enterprises to provide
-better performance and concurrency for their most demanding workloads. It
-delivers more value to *MySQL* server users with optimized performance,
-greater performance scalability and availability, enhanced backups, and
-increased visibility. `Commercial support contracts are available
-<https://www.percona.com/services/support/mysql-support>`__.
diff --git a/doc/source/_res/rn/useful-links.txt b/doc/source/_res/rn/useful-links.txt
deleted file mode 100644
index 74052ea60d2e..000000000000
--- a/doc/source/_res/rn/useful-links.txt
+++ /dev/null
@@ -1,10 +0,0 @@
-Useful links
-========================
-
-- The `Percona Server for MySQL installation instructions <https://www.percona.com/doc/percona-server/LATEST/installation.html>`__
-
-- `Download Percona Server for MySQL 8.0 <https://www.percona.com/downloads/Percona-Server-LATEST/>`__
-
-- The `Percona Server for MySQL GitHub location <https://github.com/percona/percona-server>`__ 
-
-- To contribute to the documentation, review the `Documentation Contribution Guide <https://github.com/percona/percona-server/blob/8.0/doc/source/contributing.md>`__
diff --git a/doc/source/_templates/theme/header.html b/doc/source/_templates/theme/header.html
deleted file mode 100644
index 1718edaff0a7..000000000000
--- a/doc/source/_templates/theme/header.html
+++ /dev/null
@@ -1,40 +0,0 @@
-<header class="md-header" data-md-component="header">
-  <nav class="md-header-nav md-grid">
-    <div class="md-flex navheader">
-      <div class="md-flex__cell md-flex__cell--shrink">
-        <a href="https://www.percona.com/software/documentation" title="{{ docstitle|e }}"
-           class="md-header-nav__button md-logo">
-          {% if theme_logo_icon|e %}
-            <i class="md-icon">{{ theme_logo_icon }}</i>
-          {% elif logo %}
-              <img src="{{ pathto('_static/' ~ logo, 1) }}" height="26"
-                   alt="{{ shorttitle|striptags|e }} logo">
-          {% else %}
-            &nbsp;
-          {% endif %}
-        </a>
-      </div>
-      <div class="md-flex__cell md-flex__cell--shrink">
-        <label class="md-icon md-icon--menu md-header-nav__button" for="__drawer"></label>
-      </div>
-      <div class="md-flex__cell md-flex__cell--stretch">
-        <div class="md-flex__ellipsis md-header-nav__title" data-md-component="title">
-          <span class="md-header-nav__topic"> <a href="https://www.percona.com/software/documentation">Percona Product Documentation</a></span>
-          <span class="md-header-nav__topic"> {{ title|striptags|e }} </span>
-        </div>
-      </div>
-      <div class="md-flex__cell md-flex__cell--shrink">
-        <label class="md-icon md-icon--search md-header-nav__button" for="__search"></label>
-        {% include "searchbox.html" %}
-      </div>
-      {% if theme_repo_url %}
-        <div class="md-flex__cell md-flex__cell--shrink">
-          <div class="md-header-nav__source">
-            {% include "repo.html" %}
-          </div>
-        </div>
-      {% endif %}
-      {% include "version_dropdown.html" %}
-    </div>
-  </nav>
-</header>
diff --git a/doc/source/_templates/theme/layout.html b/doc/source/_templates/theme/layout.html
deleted file mode 100644
index a464b2552111..000000000000
--- a/doc/source/_templates/theme/layout.html
+++ /dev/null
@@ -1,19 +0,0 @@
-{# Import the theme's layout. #}
-{% extends "!layout.html" %}
-
-{# Adds Google Analytics events on button click. #}
-{%- block extrahead %}
-<script>
-var _gaq = _gaq || [];
-_gaq.push(['_setAccount', 'UA-343802-3']);
-_gaq.push(['_trackPageview']);
-</script>
-{{ super() }}
-{%- endblock %}
-
-
-{%- block relbar2 %}
-{% include "relbar2.html" %}
-{%- endblock %}
-
-
diff --git a/doc/source/_templates/theme/localtoc.html b/doc/source/_templates/theme/localtoc.html
deleted file mode 100644
index d6361d4dc520..000000000000
--- a/doc/source/_templates/theme/localtoc.html
+++ /dev/null
@@ -1,26 +0,0 @@
-{% set toc_nodes = derender_toc(toc, True, pagename) if display_toc else [] %}
-<nav class="md-nav md-nav--secondary">
-  {%- if display_toc and toc_nodes and sidebars and 'localtoc.html' in sidebars %}
-    <label class="md-nav__title" for="__toc">Contents</label>
-  {%- endif %}
-  <ul class="md-nav__list" data-md-scrollfix="">
-    {%- if display_toc and sidebars and 'localtoc.html' in sidebars %}
-      {%- for item in toc_nodes recursive %}
-        <li class="md-nav__item"><a href="{{ item.href|e }}" class="md-nav__link">{{ item.contents }}</a>
-          {%- if item.children -%}
-            <nav class="md-nav">
-              <ul class="md-nav__list">{{ loop(item.children) }}</ul>
-            </nav>
-          {%- endif %}
-        </li>
-      {%- endfor %}
-    {%- endif %}
-    {%- if show_source %}
-    {% include "sourcelink.html" %}
-    {%- endif %}
-    {% if theme_repo_url|e %}
-    <li class="md-nav__item"><a class="md-nav__extra_link" href="{{ theme_repo_url }}/{{ edit_uri }}/{{ pagename }}.rst" target="_blank">
-    <i class="fa fa-github"></i>    Edit this page</a> </li>
-   {% endif %}
-  </ul>
-</nav>
diff --git a/doc/source/_templates/theme/relbar2.html b/doc/source/_templates/theme/relbar2.html
deleted file mode 100644
index f2d8a4cba6e3..000000000000
--- a/doc/source/_templates/theme/relbar2.html
+++ /dev/null
@@ -1,14 +0,0 @@
-<div class="md-relbar2__inner md-grid">
-<div class="md-content">
-  <article class="md-content__inner md-typeset" role="main">    
-    <h4>Contact Us </h4>
-       <p>For free technical help, visit the Percona <a class="reference external" href="https://forums.percona.com/c/mysql-mariadb/percona-server-for-mysql-8-0/20">Community Forum</a>.<br>
-        <p>To report bugs or submit feature requests, open a <a class="reference external" href="https://jira.percona.com/projects/PS/issues" target="_blank">JIRA</a> ticket.<br>
-         <p>For paid <a class="reference external" href="https://www.percona.com/services/support"> support </a> and <a class="reference external" href="https://www.percona.com/services/managed-services"> managed </a> or <a class="reference external" href="https://www.percona.com/services/consulting">consulting services </a>, contact <a class="reference external" href="https://www.percona.com/about-percona/contact" target="_blank">Percona Sales</a>.</p>
-         <hr>
-         {# Add the last updated timestamp from git commits using gitstamp extension #}
-         {%- if gitstamp %} <small> Last update: {{gitstamp}} </small> 
-         {%- endif %}
- </article>
-</div>
-</div>
\ No newline at end of file
diff --git a/doc/source/_templates/theme/sidebar.html b/doc/source/_templates/theme/sidebar.html
deleted file mode 100644
index 2c67800850aa..000000000000
--- a/doc/source/_templates/theme/sidebar.html
+++ /dev/null
@@ -1,22 +0,0 @@
-<nav class="md-nav md-nav--primary" data-md-level="0">
-  <label class="md-nav__title md-nav__title--site" for="__drawer">
-    <a href="{{ pathto(master_doc)|e }}" title="{{ docstitle|striptags|e }}" class="md-nav__button md-logo">
-      {% if theme_logo_icon %}
-        <i class="md-icon">{{ theme_logo_icon }}</i>
-      {% else %}
-        <img src="{{ pathto('_static/' ~ logo, 1) }}" alt="{{ html_title }} logo" width="48" height="48">
-      {% endif %}
-    </a>
-    <a href="{{ pathto(master_doc)|e }}"
-       title="{{ docstitle|striptags|e }}">{{ theme_nav_title or shorttitle }}</a>
-  </label>
-  {%- if theme_repo_url %}
-    <div class="md-nav__source">
-      {% include "repo.html" %}
-    </div>
-  {% endif %}
-  {% include "globaltoc.html" %}
-  <label class="md-nav__title md-nav__title--site" for="__drawer">
-<a title="Download PDF Manual" onclick="_gaq.push(['b._trackEvent', 'Percona Server', 'Download', 'Download Manual Percona Server']);" href="https://learn.percona.com/download-percona-server-8-0-manual" class="md-nav__link">Download PDF Manual <span class="glyphicon glyphicon-chevron-down"></span></a>
-  </label>
-</nav>
diff --git a/doc/source/changed_in_version.rst b/doc/source/changed_in_version.rst
deleted file mode 100644
index cd17ffc75dea..000000000000
--- a/doc/source/changed_in_version.rst
+++ /dev/null
@@ -1,159 +0,0 @@
-.. _changed_in_version:
-
-================================================================================
-Changed in Percona Server |version|
-================================================================================
-
-|Percona Server| |version| is based on |MySQL| |version| and incorporates many of the
-improvements found in |Percona Server| 5.7.
-
-------------------------------------------------------------------------
-Features Ported to |Percona Server| |version| from |Percona Server| 5.7
-------------------------------------------------------------------------
-
-The features are listed within the following sections:
-
-SHOW ENGINE INNODB STATUS Extensions
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-
-- The Redo Log state
-- Specifying the InnoDB buffer pool sizes in bytes
-- ``innodb_print_lock_wait_timeout_info`` system variable
-
-Performance
-^^^^^^^^^^^
-
-- :ref:`prefix_index_queries_optimization`
-- :ref:`aio_page_requests`
-- :ref:`threadpool`
-- :ref:`ps.buffer-pool.free-list.priority-refill`
-- :ref:`lru_manager_threads`
-
-
-Flexibility
-^^^^^^^^^^^
-
-- :ref:`innodb_fts_improvements`
-- :ref:`improved_memory_engine`
-- :ref:`extended_mysqldump`
-- :ref:`extended_select_into_outfile`
-- :ref:`proxy_protocol_support`
-- :ref:`compressed_columns`
-
-Management
-^^^^^^^^^^
-
-- :ref:`udf_percona_toolkit`
-- :ref:`kill_idle_trx`
-- :ref:`changed_page_tracking`
-- :ref:`pam_plugin`
-- :ref:`expanded_innodb_fast_index_creation`
-- :ref:`backup_locks`
-- :ref:`audit_log_plugin`
-- :ref:`start_transaction_with_consistent_snapshot`
-- :ref:`extended_show_grants`
-- :ref:`data_at_rest_encryption`
-
-Reliability
-^^^^^^^^^^^
-
-- :ref:`innodb_corrupt_table_action_page`
-- :ref:`log_connection_error`
-
-Diagnostics
-^^^^^^^^^^^
-
-- :ref:`user_stats`
-- :ref:`slow_extended`
-- :ref:`show_engines`
-- :ref:`process_list`
-- :ref:`INFORMATION_SCHEMA.[GLOBAL_]TEMP_TABLES <temp_tables>`
-- :ref:`thread_based_profiling`
-- :ref:`innodb_fragmentation_count`
-
-Features Removed from |Percona Server| |version|
-================================================
-
-Some features, that were present in |Percona Server| 5.7, are removed from
-|Percona Server| |version|:
-
-Removed Features
---------------------------------------------------------------------------------
-
-- `Slow Query Log Rotation and Expiration
-  <https://www.percona.com/doc/percona-server/5.7/flexibility/slowlog_rotation.html>`_
-- `CSV engine mode for standard-compliant quote and comma parsing <https://www.percona.com/doc/percona-server/5.7/flexibility/csv_engine_mode.html>`_
-- `Expanded program option modifiers <https://www.percona.com/doc/percona-server/5.7/management/expanded_program_option_modifiers.html>`_
-- `The ALL_O_DIRECT InnoDB flush method: it is not compatible with the new
-  redo logging implementation <https://www.percona.com/doc/percona-server/5.7/scalability/innodb_io.html>`_
-- `XTRADB_RSEG table from INFORMATION_SCHEMA <https://www.percona.com/doc/percona-server/5.7/diagnostics/misc_info_schema_tables.html>`_
-- `InnoDB memory size information from SHOW ENGINE INNODB STATUS; the same
-  information is available from Performance Schema memory summary tables <https://www.percona.com/doc/percona-server/5.7/diagnostics/innodb_show_status.html>`_
-- `Query cache enhancements
-  <https://www.percona.com/doc/percona-server/5.7/performance/query_cache_enhance.html#query-cache-enhancements>`_
-
-
-.. seealso::
-
-   |MySQL| Documentation: Performance Schema Table Description
-      https://dev.mysql.com/doc/refman/8.0/en/performance-schema-table-descriptions.html
-
-.. _changed_in_version.removed_syntax:
-
-Removed Syntax
---------------------------------------------------------------------------------
-
-- The ``SET STATEMENT ... FOR ...`` statement that enabled setting a
-  variable for a single query. For more information see
-  :ref:`Replacing SET STATEMENT FOR with the Upstream Equivalent
-  <set-statement-for.upstream.replacing>`.
-- The ``LOCK BINLOG FOR BACKUP`` statement due to the introduction of the
-  ``log_status`` table in Performance Schema of |MySQL| |version|.
-
-
-Removed Plugins
---------------------------------------------------------------------------------
-
-- ``SCALABILITY_METRICS``
-- ``QUERY_RESPONSE_TIME`` plugins
-
-The ``QUERY_RESPONSE_TIME`` plugins have been removed from |Percona
-Server| |version| as the Performance Schema of |MySQL| |version|
-provides histogram data for statement execution time.
-
-.. seealso::
-
-   |MySQL| Documentation: Statement Histogram Summary Tables
-      https://dev.mysql.com/doc/refman/8.0/en/statement-histogram-summary-tables.html
-
-Removed System variables
---------------------------------------------------------------------------------
-
-- The `innodb_use_global_flush_log_at_trx_commit
-  <https://www.percona.com/doc/percona-server/5.7/scalability/innodb_io.html#innodb_use_global_flush_log_at_trx_commit>`_
-  system variable which enabled setting the global |MySQL| variable
-  `innodb_flush_log_at_trx_commit
-  <https://dev.mysql.com/doc/refman/8.0/en/innodb-parameters.html#sysvar_innodb_flush_log_at_trx_commit>`_
-- `pseudo_server_id
-  <https://www.percona.com/doc/percona-server/5.7/flexibility/per_session_server-id.html#pseudo_server_id>`_
-- `max_slowlog_files
-  <https://www.percona.com/doc/percona-server/5.7/flexibility/slowlog_rotation.html#max_slowlog_files>`_
-- `max_slowlog_size <https://www.percona.com/doc/percona-server/5.7/flexibility/slowlog_rotation.html#max_slowlog_size>`_
-- `innodb_show_verbose_locks
-  <https://www.percona.com/doc/percona-server/5.7/diagnostics/innodb_show_status.html#innodb_show_verbose_locks>`_:
-  showed the records locked in ``SHOW ENGINE INNODB STATUS``
-- `NUMA support in mysqld_safe
-  <https://www.percona.com/doc/percona-server/5.7/performance/innodb_numa_support.html#improved-numa-support>`_
-- `innodb_kill_idle_trx
-  <https://www.percona.com/doc/percona-server/LATEST/management/innodb_kill_idle_trx.html>`_
-  which was an alias to the ``kill_idle_trx`` system variable
-- The `max_binlog_files <https://www.percona.com/doc/percona-server/5.7/flexibility/max_binlog_files.html#max_binlog_files>`_ system variable
-
-Deprecated Storage engine
------------------------------------------------------
-
--  The TokuDB Storage Engine was `declared as deprecated <https://www.percona.com/doc/percona-server/8.0/release-notes/Percona-Server-8.0.13-3.html>`__ in Percona Server for MySQL 8.0 and will be disabled in upcoming 8.0 versions. 
-    
-    We recommend migrating to the MyRocks Storage Engine. 
-
-    For more information, see the Percona blog post: `Heads-Up: TokuDB Support Changes and Future Removal from Percona Server for MySQL 8.0 <https://www.percona.com/blog/2021/05/21/tokudb-support-changes-and-future-removal-from-percona-server-for-mysql-8-0/>`__.
\ No newline at end of file
diff --git a/doc/source/conf-material/conf.py b/doc/source/conf-material/conf.py
deleted file mode 100644
index 573b1c3cf429..000000000000
--- a/doc/source/conf-material/conf.py
+++ /dev/null
@@ -1,35 +0,0 @@
-#!/usr/bin/env python3
-# -*- coding: utf-8 -*-
-import sys
-import os
-sys.path.append(os.path.abspath("../"))
-from conf import *
-extensions.append('sphinx_gitstamp')
-extensions.append('sphinx_copybutton')
-html_sidebars['**']=['globaltoc.html', 'searchbox.html', 'localtoc.html', 'logo-text.html']
-html_theme = 'sphinx_material'
-html_theme_options = {
-    'base_url': 'http://bashtage.github.io/sphinx-material/',
-    'repo_url': 'https://github.com/percona/percona-server',
-    'repo_name': 'percona/percona-server',
-    'color_accent': 'grey',
-    'color_primary': 'orange',
-    'globaltoc_collapse': True,
-    'version_dropdown': True,
-    'version_dropdown_text': 'Versions',
-    'version_info': {
-        "5.7": "https://docs.percona.com/percona-server/5.7/",
-        "8.0": "https://docs.percona.com/percona-server/8.0/",
-        "Latest": "https://docs.percona.com/percona-server/latest/"
-    },
-}
-html_logo = '../_images/percona-logo.svg'
-html_favicon = '../_images/percona_favicon.ico'
-pygments_style = 'emacs'
-gitstamp_fmt = "%b %d, %Y"
-# Specify the text pattern that won't be copied with the code block contents
-copybutton_prompt_text = '$'
-# Add any paths that contain templates here, relative to this directory.
-templates_path = ['../_templates/theme']
-#html_last_updated_fmt = ''
-
diff --git a/doc/source/conf.py b/doc/source/conf.py
deleted file mode 100644
index 3fd133895900..000000000000
--- a/doc/source/conf.py
+++ /dev/null
@@ -1,335 +0,0 @@
-# -*- coding: utf-8 -*-
-#
-# Percona Server documentation build configuration file, created by
-# sphinx-quickstart on Mon Aug  8 01:24:46 2011.
-#
-# This file is execfile()d with the current directory set to its containing dir.
-#
-# Note that not all possible configuration values are present in this
-# autogenerated file.
-#
-# All configuration values have a default; values that are commented out
-# serve to show the default.
-
-import sys, os
-
-# If extensions (or modules to document with autodoc) are in another directory,
-# add these directories to sys.path here. If the directory is relative to the
-# documentation root, use os.path.abspath to make it absolute, like shown here.
-#sys.path.insert(0, os.path.abspath('.'))
-
-sys.path.append(os.path.abspath('ext'))
-
-# -- General configuration -----------------------------------------------------
-
-# If your documentation needs a minimal Sphinx version, state it here.
-#needs_sphinx = '1.0'
-
-# Add any Sphinx extension module names here, as strings. They can be extensions
-# coming with Sphinx (named 'sphinx.ext.*') or your custom ones.
-extensions = ['sphinx.ext.intersphinx', 'sphinx.ext.todo',
-              'sphinx.ext.coverage', 'sphinx.ext.ifconfig',
-              'sphinx.ext.extlinks']
-
-# Add any paths that contain templates here, relative to this directory.
-templates_path = ['_templates']
-
-# The suffix of source filenames.
-source_suffix = '.rst'
-
-# The encoding of source files.
-#source_encoding = 'utf-8-sig'
-
-# The master toctree document.
-master_doc = 'index'
-
-# General information about the project.
-project = u'Percona Server'
-copyright = u'Percona LLC and/or its affiliates 2009-2022'
-
-# The version info for the project you're documenting, acts as replacement for
-# |version| and |release|, also used in various other places throughout the
-# built documents.
-#
-# The short X.Y version.
-version = '8.0'
-# The full version, including alpha/beta/rc tags.
-release = ".".join([version, '29-21'])
-# The language for content autogenerated by Sphinx. Refer to documentation
-# for a list of supported languages.
-#language = None
-
-# There are two options for replacing |today|: either, you set today to some
-# non-false value, then it is used:
-#today = ''
-# Else, today_fmt is used as the format for a strftime call.
-#today_fmt = '%B %d, %Y'
-
-# List of patterns, relative to source directory, that match files and
-# directories to ignore when looking for source files.
-exclude_patterns = []
-
-# If true, '()' will be appended to :func: etc. cross-reference text.
-#add_function_parentheses = True
-
-# If true, the current module name will be prepended to all description
-# unit titles (such as .. function::).
-#add_module_names = True
-
-# If true, sectionauthor and moduleauthor directives will be shown in the
-# output. They are ignored by default.
-#show_authors = False
-
-# The name of the Pygments (syntax highlighting) style to use.
-pygments_style = 'sphinx'
-
-rst_prolog = '''
-
-.. role:: mysql(code)
-   :language: mysql
-
-.. role:: dir(file)
-
-.. role:: bash(code)
-   :language: bash
-
-.. |check|  replace:: ``|[[---CHECK---]]|``
-
-.. |xtrabackup|  replace:: :program:`xtrabackup`
-
-.. |innobackupex|  replace:: :program:`innobackupex`
-
-.. |XtraDB|  replace:: *XtraDB*
-
-.. |Jenkins|  replace:: :term:`Jenkins`
-
-.. |InnoDB|  replace:: *InnoDB*
-
-.. |MyISAM|  replace:: *MyISAM*
-
-.. |LSN|  replace:: *LSN*
-
-.. |XtraBackup|  replace:: *XtraBackup*
-
-.. |Percona XtraBackup|  replace:: *Percona XtraBackup*
-
-.. |Percona TokuBackup|  replace:: *Percona TokuBackup*
-
-.. |TokuBackup|  replace:: *TokuBackup*
-
-.. |Percona Toolkit|  replace:: *Percona Toolkit*
-
-.. |Percona Server|  replace:: *Percona Server for MySQL*
-
-.. |Percona|  replace:: *Percona*
-
-.. |TokuDB|  replace:: *TokuDB*
-
-.. |Percona FT|  replace:: *Percona FT*
-
-.. |MySQL|  replace:: *MySQL*
-
-.. |MariaDB|  replace:: *MariaDB*
-
-.. |tar4ibd|  replace:: :program:`tar4ibd`
-
-.. |tar|  replace:: :program:`tar`
-
-.. |MyRocks| replace:: *MyRocks*
-
-'''
-
-# A list of ignored prefixes for module index sorting.
-#modindex_common_prefix = []
-
-extlinks = {'bug': ('https://bugs.launchpad.net/percona-server/+bug/%s', '#'),
-            'mysqlbug': ('http://bugs.mysql.com/bug.php?id=%s', '#'),
-            'ftbug': ('https://tokutek.atlassian.net/browse/FT-%s', '#'),
-            'tokubug': ('https://tokutek.atlassian.net/browse/DB-%s', '#'),
-            'backupbug': ('https://tokutek.atlassian.net/browse/BACKUP-%s', '#'),
-            'tdbbug': ('https://jira.percona.com/browse/TDB-%s', '#'),
-            'psbug': ('https://jira.percona.com/browse/PS-%s', '#'),
-            'jirabug': ('https://jira.percona.com/browse/%s', '')
-}
-
-
-# -- Options for HTML output ---------------------------------------------------
-
-# The theme to use for HTML and HTML Help pages.  See the documentation for
-# a list of builtin themes.
-html_theme = 'percona-theme'
-
-# Theme options are theme-specific and customize the look and feel of a theme
-# further.  For a list of options available for each theme, see the
-# documentation.
-#html_theme_options = {}
-
-# Add any paths that contain custom themes here, relative to this directory.
-html_theme_path = ['.', './percona-theme']
-
-# Redirect info for Edit on Github link
-html_context = {
-    'repo_name': '/percona/percona-server',
-    'repo_url': 'https://github.com/percona/percona-server',
-    'edit_uri': 'blob/8.0/doc/source/'
-}
-
-# The name for this set of Sphinx documents.  If None, it defaults to
-# "<project> v<release> documentation".
-html_title = ' '.join([project, version, 'Documentation'])
-
-# A shorter title for the navigation bar.  Default is the same as html_title.
-html_short_title = ' '.join([project, version])
-
-# The name of an image file (relative to this directory) to place at the top
-# of the sidebar.
-html_logo = 'percona-server-logo.jpg'
-
-# The name of an image file (within the static path) to use as favicon of the
-# docs.  This file should be a Windows icon file (.ico) being 16x16 or 32x32
-# pixels large.
-#html_favicon = None
-
-# Add any paths that contain custom static files (such as style sheets) here,
-# relative to this directory. They are copied after the builtin static files,
-# so a file named "default.css" will overwrite the builtin "default.css".
-html_static_path = ['_static']
-
-# If not '', a 'Last updated on:' timestamp is inserted at every page bottom,
-# using the given strftime format.
-#html_last_updated_fmt = '%b %d, %Y'
-
-# If true, SmartyPants will be used to convert quotes and dashes to
-# typographically correct entities.
-#html_use_smartypants = True
-
-# Custom sidebar templates, maps document names to template names.
-html_sidebars = {
-        '**': ['localtoc.html', 'relations.html', 'sourcelink.html'],
-        'using/windows': ['windowssidebar.html'],
-}
-
-# Additional templates that should be rendered to pages, maps page names to
-# template names.
-#html_additional_pages = {}
-
-# If false, no module index is generated.
-#html_domain_indices = True
-
-# If false, no index is generated.
-#html_use_index = True
-
-# If true, the index is split into individual pages for each letter.
-#html_split_index = False
-
-# If true, links to the reST sources are added to the pages.
-#html_show_sourcelink = True
-
-# If true, "Created using Sphinx" is shown in the HTML footer. Default is True.
-#html_show_sphinx = True
-
-# If true, "(C) Copyright ..." is shown in the HTML footer. Default is True.
-#html_show_copyright = True
-
-# If true, an OpenSearch description file will be output, and all pages will
-# contain a <link> tag referring to it.  The value of this option must be the
-# base URL from which the finished HTML is served.
-#html_use_opensearch = ''
-
-# This is the file name suffix for HTML files (e.g. ".xhtml").
-#html_file_suffix = None
-
-# Output file base name for HTML help builder.
-# Base name: project without whitespace;
-#            version without the dot;
-#            doc
-# Base name example: PerconaServer57doc
-
-# Tip: To see the value assigned to the following variable, copy the
-# expression to be assigned and evaluate it in Python3 schell.
-
-htmlhelp_basename = ''.join([''.join(project.split()),
-                             ''.join(version.split('.')),
-                             'doc'])
-
-# -- Options for LaTeX output --------------------------------------------------
-
-# The paper size ('letter' or 'a4').
-#latex_paper_size = 'letter'
-
-# The font size ('10pt', '11pt' or '12pt').
-#latex_font_size = '10pt'
-
-# Grouping the document tree into LaTeX files. List of tuples
-# (source start file, target name (example: 'PerconaServer-5.7.tex'),
-# title, author, documentclass [howto/manual]).
-
-# Tip: To see the value assigned to the following variable, copy the
-# expression to be assigned and evaluate it in Python3 schell.
-
-latex_documents = [
-  ('index', # source start file
-   #target name, such as PerconaServer-5.7.tex
-   '.'.join(['-'.join([''.join(project.split()), version]), 'tex']),
-   ' '.join([project, 'Documentation']), # title, such as Percona Server Documentation
-   copyright,
-   'manual' # document class [howto/manual]
-  ),
-]
-
-# The name of an image file (relative to this directory) to place at the top of
-# the title page.
-latex_logo = 'percona-logo-color.png'
-
-# For "manual" documents, if this is true, then toplevel headings are parts,
-# not chapters.
-latex_toplevel_sectioning = 'part'
-
-latex_elements = {
-  'classoptions': ',oneside',
-  'babel': '\\usepackage[english]{babel}'
-}
-
-# If true, show page references after internal links.
-#latex_show_pagerefs = False
-
-# If true, show URL addresses after external links.
-#latex_show_urls = False
-
-# Additional stuff for the LaTeX preamble.
-#latex_preamble = ''
-
-# Documents to append as an appendix to all manuals.
-#latex_appendices = []
-
-# If false, no module index is generated.
-#latex_domain_indices = True
-
-
-# -- Options for manual page output --------------------------------------------
-
-# One entry per manual page. List of tuples
-# (source start file, name, description, authors, manual section).
-
-# Tip: To see the value assigned to the following variable, copy the
-# expression to be assigned and evaluate it in Python3 schell.
-
-man_pages = [('index', # source start file
-              ''.join([''.join(project.lower().split()),
-                       ''.join(version.split('.'))]), # name, such as perconaserver57
-              ' '.join([project, version, u'Documentation']), # description, such as Percona Server 5.7 Documentation
-              [u'Percona LLC and/or its affiliates 2009-2022'], # authors
-              1 # manual section
-)]
-
-
-# Example configuration for intersphinx: refer to the Python standard library.
-intersphinx_mapping = {
-    'ps51' : ('https://www.percona.com/doc/percona-server/5.1/', None),
-    'ps55' : ('https://www.percona.com/doc/percona-server/5.5/', None),
-    'ps56' : ('https://www.percona.com/doc/percona-server/5.6/', None),
-    'ps57' : ('https://www.percona.com/doc/percona-server/5.7/', None),
-    'ps80' : ('https://www.percona.com/doc/percona-server/8.0/', None),
-    'xb21' : ('https://www.percona.com/doc/percona-xtrabackup/2.1/', None),
-    'ptoolkit' : ('https://www.percona.com/doc/percona-toolkit/2.2/', None)
- }
diff --git a/doc/source/copyright.rst b/doc/source/copyright.rst
deleted file mode 100644
index db1bed655626..000000000000
--- a/doc/source/copyright.rst
+++ /dev/null
@@ -1,23 +0,0 @@
-===================================
-Copyright and Licensing Information
-===================================
-
-Documentation Licensing
-=======================
-
-This software documentation is (C)2009-2018 Percona LLC and/or its affiliates
-and is distributed under the `Creative Commons Attribution-ShareAlike 2.0
-Generic <http://creativecommons.org/licenses/by-sa/2.0/>`_ license.
-
-Software License
-================
-
-|Percona Server| is built upon MySQL from Oracle. Along with making our own
-modifications, we merge in changes from other sources such as community
-contributions and changes from MariaDB.
-
-The original SHOW USER/TABLE/INDEX statistics code came from Google.
-
-Percona does not require copyright assignment.
-
-See the COPYING files accompanying the software distribution.
diff --git a/doc/source/development.rst b/doc/source/development.rst
deleted file mode 100644
index 9ed6e58621e0..000000000000
--- a/doc/source/development.rst
+++ /dev/null
@@ -1,66 +0,0 @@
-.. _development:
-
-================================================================================
-Development of |Percona Server|
-================================================================================
-
-|Percona Server| is an open source project to produce a distribution
-of the |MySQL| Server with improved performance, scalability and
-diagnostics.
-
-Submitting Changes
-================================================================================
-
-We keep trunk in a constant state of stability to allow for a release at
-any time and to minimize wasted time by developers due to broken code.
-
-Overview
---------------------------------------------------------------------------------
-
-At Percona we use `Git <https://git-scm.com>`_ for source control, `GitHub
-<https://github.com/percona>`_ for code hosting, and `Jira
-<https://jira.percona.com>`_ for release management.
-
-We change our software to implement new features and/or to fix bugs. Refactoring
-could be classed either as a new feature or a bug depending on the scope of
-work.
-
-New features and bugs are targeted to specific releases. A
-release is part of a series. For example, 2.4 is a series in Percona
-XtraBackup and 2.4.15, 2.4.16 and 2.4.17 are releases in this series.
-
-Code is proposed for merging in the form of pull requests on GitHub.
-
-For |Percona Server|, we have several Git branches on which development occurs:
-5.5, 5.6, 5.7, and 8.0. As |Percona Server| is not a traditional project, instead
-of being a set of patches against an existing product, these branches are not
-related. In other words, we do not merge from one release branch to another. To
-have your changes in several branches, you must propose branches to each release
-branch.
-
-Making a Change to a Project
---------------------------------------------------------------------------------
-
-In this case, we are going to use ``percona-xtrabackup`` as an example. The
-workflow is similar for |Percona Server|, but the patch will need to be modified
-in all release branches of |Percona Server|.
-
-* ``git branch https://github.com/percona/percona-xtrabackup/featureX`` (where 'featureX' is a
-  sensible name for the task at hand)
-* (developer makes changes in featureX, testing locally)
-* The Developer pushes to ``https://github.com/percona/username/percona-xtrabackup/featureX``
-* The developer can submit a pull request to https://github.com/percona/percona-xtrabackup,
-* Code undergoes a review
-* Once code is accepted, it can be merged
-
-If the change also applies to a stable release (e.g. 2.4) then changes should be
-made on a branch of 2.4 and merged to a branch of trunk. In this case there
-should be two branches run through the param build and two merge proposals (one
-for the stable release and one with the changes merged to trunk). This prevents
-somebody else having to guess how to merge your changes.
-
-|Percona Server|
---------------------------------------------------------------------------------
-
-The same process for |Percona Server|, but we have several different branches
-(and merge requests).
diff --git a/doc/source/diagnostics/innodb_fragmentation_count.rst b/doc/source/diagnostics/innodb_fragmentation_count.rst
deleted file mode 100644
index 737ef8580afb..000000000000
--- a/doc/source/diagnostics/innodb_fragmentation_count.rst
+++ /dev/null
@@ -1,120 +0,0 @@
-.. _innodb_fragmentation_count:
-
-====================================
-InnoDB Page Fragmentation Counters
-====================================
-
-*InnoDB* page fragmentation is caused by random insertion or deletion from a
-secondary index. This means that the physical ordering of the index pages on
-the disk is not same as the index ordering of the records on the pages. As a
-consequence this means that some pages take a lot more space and that queries
-which require a full table scan can take a long time to finish.
-
-To provide more information about the *InnoDB* page fragmentation *Percona Server for MySQL* now provides the following counters as status variables: 
-:ref:`Innodb_scan_pages_contiguous`,
-:ref:`Innodb_scan_pages_disjointed`, :ref:`Innodb_scan_data_size`,
-:ref:`Innodb_scan_deleted_recs_size`, and
-:ref:`Innodb_scan_pages_total_seek_distance`.
-
-
-Version Specific Information
-============================
-
-* :ref:`8.0.12-1`: The feature was ported from *Percona Server for MySQL* 5.7
-
-Status Variables
-================
-
-.. _Innodb_scan_pages_contiguous:
-
-.. rubric:: ``Innodb_scan_pages_contiguous``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Scope
-     - Session
-   * - Data type
-     - Numeric
-
-This variable shows the number of contiguous page reads inside a query.
-
-.. _Innodb_scan_pages_disjointed:
-
-.. rubric:: ``Innodb_scan_pages_disjointed``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Scope
-     - Session
-   * - Data type
-     - Numeric
-
-This variable shows the number of disjointed page reads inside a query.
-
-.. _Innodb_scan_data_size:
-
-.. rubric:: ``Innodb_scan_data_size``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Scope
-     - Session
-   * - Data type
-     - Numeric
-
-This variable shows the size of data in all *InnoDB* pages read inside a
-query (in bytes) - calculated as the sum of ``page_get_data_size(page)`` for
-every page scanned.
-
-.. _Innodb_scan_deleted_recs_size:
-
-.. rubric:: ``Innodb_scan_deleted_recs_size``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Scope
-     - Session
-   * - Data type
-     - Numeric
-
-This variable shows the size of deleted records (marked as ``deleted`` in
-``page_delete_rec_list_end()``) in all *InnoDB* pages read inside a query
-(in bytes) - calculated as the sum of ``page_header_get_field(page,
-PAGE_GARBAGE)`` for every page scanned.
-
-.. _Innodb_scan_pages_total_seek_distance:
-
-.. rubric:: ``Innodb_scan_pages_total_seek_distance``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Scope
-     - Session
-   * - Data type
-     - Numeric
-
-This variable shows the total seek distance when moving between pages.
-
-Related Reading
-===============
-
-  * `InnoDB: look after fragmentation
-    <https://www.percona.com/blog/2009/11/05/innodb-look-after-fragmentation/>`_
- 
-  * `Defragmenting a Table
-    <https://dev.mysql.com/doc/refman/8.0/en/innodb-file-defragmenting.html>`_
diff --git a/doc/source/diagnostics/innodb_show_status.rst b/doc/source/diagnostics/innodb_show_status.rst
deleted file mode 100644
index 4a0841f3c521..000000000000
--- a/doc/source/diagnostics/innodb_show_status.rst
+++ /dev/null
@@ -1,653 +0,0 @@
-.. _innodb_show_status:
-
-====================================
-Extended Show Engine InnoDB Status
-====================================
-
-This feature reorganizes the output of ``SHOW ENGINE INNODB STATUS``
-to improve readability and to provide additional information. The
-variable :ref:`innodb_show_locks_held` controls the umber of
-locks held to print for each *InnoDB* transaction.
-
-This feature modified the ``SHOW ENGINE INNODB STATUS`` command as follows:
-
-* Added extended information about *InnoDB* internal hash table sizes
-  (in bytes) in the ``BUFFER POOL AND MEMORY`` section; also added
-  buffer pool size in bytes.
-* Added additional LOG section information.
-
-Other Information
-=================
-
-  * Author / Origin:
-    Baron Schwartz, http://lists.mysql.com/internals/35174
-
-System Variables
-================
-
-.. _innodb_show_locks_held:
-
-.. rubric:: ``innodb_show_locks_held``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - Yes
-   * - Config file
-     - Yes
-   * - Scope
-     - Global
-   * - Dynamic
-     - Yes
-   * - Data type
-     - ULONG
-   * - Default
-     - 10
-   * - Range
-     - 0 - 1000
-
-Specifies the number of locks held to print for each *InnoDB* transaction in
-``SHOW ENGINE INNODB STATUS``.
-
-.. _innodb_print_lock_wait_timeout_info:
-
-.. rubric:: ``innodb_print_lock_wait_timeout_info``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - Yes
-   * - Config file
-     - Yes
-   * - Scope
-     - Global
-   * - Dynamic
-     - Yes
-   * - Data type
-     - Boolean
-   * - Default
-     - ``OFF``
-
-Makes *InnoDB* to write information about all lock wait timeout errors 
-into the log file. 
-
-This allows to find out details about the failed transaction, and, most 
-importantly, the blocking transaction. Query string can be obtained from `EVENTS_STATEMENTS_CURRENT` table, based on the 
-``PROCESSLIST_ID`` field, which corresponds to ``thread_id`` from the log
-output.
-
-Taking into account that blocking transaction is often a multiple statement 
-one, folowing query can be used to obtain blocking thread statements history:
-
-.. code-block:: mysql
-
-   SELECT s.SQL_TEXT FROM performance_schema.events_statements_history s
-   INNER JOIN performance_schema.threads t ON t.THREAD_ID = s.THREAD_ID
-   WHERE t.PROCESSLIST_ID = %d
-   UNION
-   SELECT s.SQL_TEXT FROM performance_schema.events_statements_current s
-   INNER JOIN performance_schema.threads t ON t.THREAD_ID = s.THREAD_ID
-   WHERE t.PROCESSLIST_ID = %d;
-
-(PROCESSLIST_ID in this example is exactly the thread id from error log
-output).
-
-
-Status Variables
-================
-
-The status variables here contain information available in the output of ``SHOW
-ENGINE INNODB STATUS``, organized by the sections ``SHOW ENGINE INNODB STATUS``
-displays. If you are familiar with the output of ``SHOW ENGINE INNODB STATUS``,
-you will probably already recognize the information these variables contain.
-
-
-BACKGROUND THREAD
------------------
-
-The following variables contain information in the ``BACKGROUND THREAD``
-section of the output from ``SHOW ENGINE INNODB STATUS``. An example of that
-output is: ::
-
-  -----------------
-  BACKGROUND THREAD
-  -----------------
-  srv_master_thread loops: 1 srv_active, 0 srv_shutdown, 11844 srv_idle
-  srv_master_thread log flush and writes: 11844
-
-*InnoDB* has a source thread which performs background tasks depending on the
-server state, once per second. If the server is under workload, the source
-thread runs the following: performs background table drops; performs change
-buffer merge, adaptively; flushes the redo log to disk; evicts tables from the
-dictionary cache if needed to satisfy its size limit; makes a checkpoint. If
-the server is idle: performs background table drops, flushes and/or checkpoints
-the redo log if needed due to the checkpoint age; performs change buffer merge
-at full I/O capacity; evicts tables from the dictionary cache if
-needed; and makes a checkpoint.
-
-.. _Innodb_master_thread_active_loops:
-
-.. rubric:: ``Innodb_master_thread_active_loops``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Scope
-     - Global
-   * - Data type
-     - Numeric
-
-This variable shows the number of times the above one-second loop was executed
-for active server states.
-
-.. _Innodb_master_thread_idle_loops:
-
-.. rubric:: ``Innodb_master_thread_idle_loops``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Scope
-     - Global
-   * - Data type
-     - Numeric
-
-This variable shows the number of times the above one-second loop was executed
-for idle server states.
-
-.. _Innodb_background_log_sync:
-
-.. rubric:: ``Innodb_background_log_sync``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Scope
-     - Global
-   * - Data type
-     - Numeric
-
-This variable shows the number of times the *InnoDB* source thread has written
-and flushed the redo log.
-
-SEMAPHORES
-----------
-
-The following variables contain information in the ``SEMAPHORES`` section of
-the output from ``SHOW ENGINE INNODB STATUS``. An example of that output is: ::
-
-  ----------
-  SEMAPHORES
-  ----------
-  OS WAIT ARRAY INFO: reservation count 9664, signal count 11182
-  Mutex spin waits 20599, rounds 223821, OS waits 4479
-  RW-shared spins 5155, OS waits 1678; RW-excl spins 5632, OS waits 2592
-  Spin rounds per wait: 10.87 mutex, 15.01 RW-shared, 27.19 RW-excl
-
-INSERT BUFFER AND ADAPTIVE HASH INDEX
--------------------------------------
-
-The following variables contain information in the ``INSERT BUFFER AND ADAPTIVE
-HASH INDEX`` section of the output from ``SHOW ENGINE INNODB STATUS``. An
-example of that output is: ::
-
-  -------------------------------------
-  INSERT BUFFER AND ADAPTIVE HASH INDEX
-  -------------------------------------
-  Ibuf: size 1, free list len 6089, seg size 6091,
-  44497 inserts, 44497 merged recs, 8734 merges
-  0.00 hash searches/s, 0.00 non-hash searches/s
-
-.. _Innodb_ibuf_free_list:
-
-.. rubric:: ``Innodb_ibuf_free_list``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Scope
-     - Global
-   * - Data type
-     - Numeric
-
-.. _Innodb_ibuf_segment_size:
-
-.. rubric:: ``Innodb_ibuf_segment_size``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Scope
-     - Global
-   * - Data type
-     - Numeric
-
-LOG
----
-
-The following variables contain information in the ``LOG`` section of the
-output from ``SHOW ENGINE INNODB STATUS``. An example of that output is: ::
-
-  LOG
-  ---
-  Log sequence number 10145937666
-  Log flushed up to   10145937666
-  Pages flushed up to 10145937666
-  Last checkpoint at  10145937666
-  Max checkpoint age    80826164
-  Checkpoint age target 78300347
-  Modified age          0
-  Checkpoint age        0
-  0 pending log writes, 0 pending chkp writes
-  9 log i/o's done, 0.00 log i/o's/second
-  Log tracking enabled
-  Log tracked up to   10145937666
-  Max tracked LSN age 80826164
-
-.. _Innodb_lsn_current:
-
-.. rubric:: ``Innodb_lsn_current``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Scope
-     - Global
-   * - Data type
-     - Numeric
-
-This variable shows the current log sequence number.
-
-.. _Innodb_lsn_flushed:
-
-.. rubric:: ``Innodb_lsn_flushed``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Scope
-     - Global
-   * - Data type
-     - Numeric
-
-This variable shows the current maximum LSN that has been written and flushed
-to disk.
-
-.. _Innodb_lsn_last_checkpoint:
-
-.. rubric:: ``Innodb_lsn_last_checkpoint``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Scope
-     - Global
-   * - Data type
-     - Numeric
-
-This variable shows the LSN of the latest completed checkpoint.
-
-.. _Innodb_checkpoint_age:
-
-.. rubric:: ``Innodb_checkpoint_age``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Scope
-     - Global
-   * - Data type
-     - Numeric
-
-This variable shows the current |InnoDB| checkpoint age, i.e., the difference
-between the current LSN and the LSN of the last completed checkpoint.
-
-.. _Innodb_checkpoint_max_age:
-
-.. rubric:: ``Innodb_checkpoint_max_age``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Scope
-     - Global
-   * - Data type
-     - Numeric
-
-This variable shows the maximum allowed checkpoint age above which the redo
-log is close to full and a checkpoint must happen before any further redo log
-writes.
-
-.. note:: 
-
-        This variable was removed in *Percona Server for MySQL* 8.0.13-4 due to a change
-        in MySQL. The variable is identical to log capacity.
-
-BUFFER POOL AND MEMORY
-----------------------
-
-The following variables contain information in the ``BUFFER POOL AND MEMORY``
-section of the output from ``SHOW ENGINE INNODB STATUS``. An example of that
-output is: ::
-
-  ----------------------
-  BUFFER POOL AND MEMORY
-  ----------------------
-  Total memory allocated 137363456; in additional pool allocated 0
-  Total memory allocated by read views 88
-  Internal hash tables (constant factor + variable factor)
-      Adaptive hash index 2266736         (2213368 + 53368)
-      Page hash           139112 (buffer pool 0 only)
-      Dictionary cache    729463  (554768 + 174695)
-      File system         824800  (812272 + 12528)
-      Lock system         333248  (332872 + 376)
-      Recovery system     0       (0 + 0)
-  Dictionary memory allocated 174695
-  Buffer pool size        8191
-  Buffer pool size, bytes 134201344
-  Free buffers            7481
-  Database pages          707
-  Old database pages      280
-  Modified db pages       0
-  Pending reads 0
-  Pending writes: LRU 0, flush list 0 single page 0
-  Pages made young 0, not young 0
-  0.00 youngs/s, 0.00 non-youngs/s
-  Pages read 707, created 0, written 1
-  0.00 reads/s, 0.00 creates/s, 0.00 writes/s
-  No buffer pool page gets since the last printout
-  Pages read ahead 0.00/s, evicted without access 0.00/s, Random read ahead 0.00/s
-  LRU len: 707, unzip_LRU len: 0
-
-.. _Innodb_mem_adaptive_hash:
-
-.. rubric:: ``Innodb_mem_adaptive_hash``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Scope
-     - Global
-   * - Data type
-     - Numeric
-
-This variable shows the current size, in bytes, of the adaptive hash index.
-
-.. _Innodb_mem_dictionary:
-
-.. rubric:: ``Innodb_mem_dictionary``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Scope
-     - Global
-   * - Data type
-     - Numeric
-
-This variable shows the current size, in bytes, of the *InnoDB* in-memory data
-dictionary info.
-
-.. _Innodb_mem_total:
-
-.. rubric:: ``Innodb_mem_total``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Scope
-     - Global
-   * - Data type
-     - Numeric
-
-This variable shows the total amount of memory, in bytes, *InnoDB* has
-allocated in the process heap memory.
-
-.. _Innodb_buffer_pool_pages_LRU_flushed:
-
-.. rubric:: ``Innodb_buffer_pool_pages_LRU_flushed``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Scope
-     - Global
-   * - Data type
-     - Numeric
-
-This variable shows the total number of buffer pool pages which have been
-flushed from the LRU list, i.e., too old pages which had to be flushed in
-order to make buffer pool room to read in new data pages.
-
-.. _Innodb_buffer_pool_pages_made_not_young:
-
-.. rubric:: ``Innodb_buffer_pool_pages_made_not_young``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Scope
-     - Global
-   * - Data type
-     - Numeric
-
-This variable shows the number of times a buffer pool page was not marked as
-accessed recently in the LRU list because of `innodb_old_blocks_time`
-variable setting.
-
-.. _Innodb_buffer_pool_pages_made_young:
-
-.. rubric:: ``Innodb_buffer_pool_pages_made_young``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Scope
-     - Global
-   * - Data type
-     - Numeric
-
-This variable shows the number of times a buffer pool page was moved to the
-young end of the LRU list due to its access, to prevent its eviction from the
-buffer pool.
-
-.. _Innodb_buffer_pool_pages_old:
-
-.. rubric:: ``Innodb_buffer_pool_pages_old``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Scope
-     - Global
-   * - Data type
-     - Numeric
-
-This variable shows the total number of buffer pool pages which are considered
-to be old according to the `Making the Buffer Pool Scan Resistant manual page
-<https://dev.mysql.com/doc/refman/8.0/en/innodb-performance-midpoint_insertion.html>`_.
-
-
-TRANSACTIONS
-------------
-
-The following variables contain information in the ``TRANSACTIONS`` section of
-the output from ``SHOW INNODB STATUS``. An example of that output is: ::
-
-  ------------
-  TRANSACTIONS
-  ------------
-  Trx id counter F561FD
-  Purge done for trx's n:o < F561EB undo n:o < 0
-  History list length 19
-  LIST OF TRANSACTIONS FOR EACH SESSION:
-  ---TRANSACTION 0, not started, process no 993, OS thread id 140213152634640
-  mysql thread id 15933, query id 32109 localhost root
-  show innodb status
-  ---TRANSACTION F561FC, ACTIVE 29 sec, process no 993, OS thread id 140213152769808 updating or deleting
-  mysql tables in use 1, locked 1
-
-.. _Innodb_max_trx_id:
-
-.. rubric:: ``Innodb_max_trx_id``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Scope
-     - Global
-   * - Data type
-     - Numeric
-
-This variable shows the next free transaction id number.
-
-.. _Innodb_oldest_view_low_limit_trx_id:
-
-.. rubric:: ``Innodb_oldest_view_low_limit_trx_id``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Scope
-     - Global
-   * - Data type
-     - Numeric
-
-This variable shows the highest transaction id, above which the current oldest
-open read view does not see any transaction changes. Zero if there is no open
-view.
-
-.. _Innodb_purge_trx_id:
-
-.. rubric:: ``Innodb_purge_trx_id``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Scope
-     - Global
-   * - Data type
-     - Numeric
-
-This variable shows the oldest transaction id whose records have not been
-purged yet.
-
-.. _Innodb_purge_undo_no:
-
-.. rubric:: ``Innodb_purge_undo_no``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Scope
-     - Global
-   * - Data type
-     - Numeric
-
-INFORMATION_SCHEMA Tables
-=========================
-
-The following table contains information about the oldest active transaction in
-the system.
-
-.. _XTRADB_READ_VIEW:
-
-.. rubric:: ``INFORMATION_SCHEMA.XTRADB_READ_VIEW``
-
-.. list-table::
-      :header-rows: 1
-
-      * - Column Name
-        - Description
-      * - 'READ_VIEW_LOW_LIMIT_TRX_NUMBER'
-        - 'This is the highest transactions number at the time the view was created.'
-      * - 'READ_VIEW_UPPER_LIMIT_TRX_ID'
-        - 'This is the highest transactions ID at the time the view was created. This means that it should not see newer transactions with IDs bigger than or equal to that value.'
-      * - 'READ_VIEW_LOW_LIMIT_TRX_ID'
-        - 'This is the latest committed transaction ID at the time the oldest view was created. This means that it should see all transactions with IDs smaller than or equal to that value.'
-
-.. note::
-
-    Starting with *Percona Server for MySQL* 8.0.20-11, in ``INFORMATION_SCHEMA.XTRADB_READ_VIEW``, the data type for the following columns is changed from ``VARCHAR(18)`` to ``BIGINT UNSIGNED``:
-
-    * ``READ_VIEW_LOW_LIMIT_TRX_NUMBER`` 
-    * ``READ_VIEW_UPPER_LIMIT_TRX_ID`` 
-    * ``READ_VIWE_LOW_LIMIT_TRX_ID`` 
-    
-The columns contain 64-bit integers, which is too large for ``VARCHAR(18)``.
-
-The following table contains information about the memory usage for
-InnoDB/XtraDB hash tables.
-
-.. _XTRADB_READ_VIEW:
-
-.. rubric:: ``INFORMATION_SCHEMA.XTRADB_INTERNAL_HASH_TABLES``
-
-.. list-table::
-      :header-rows: 1
-
-      * - Column Name
-        - Description
-      * - 'INTERNAL_HASH_TABLE_NAME'
-        - 'Hash table name'
-      * - 'TOTAL_MEMORY'
-        - 'Total amount of memory'
-      * - 'CONSTANT_MEMORY'
-        - 'Constant memory'
-      * - 'VARIABLE_MEMORY'
-        - 'Variable memory'
-
-Other reading
-=============
-
-  * `SHOW INNODB STATUS walk through <http://www.mysqlperformanceblog.com/2006/07/17/show-innodb-status-walk-through/>`_
-
-  * `Table locks in SHOW INNODB STATUS <http://www.mysqlperformanceblog.com/2010/06/08/table-locks-in-show-innodb-status/>`_
diff --git a/doc/source/diagnostics/libcoredumper.rst b/doc/source/diagnostics/libcoredumper.rst
deleted file mode 100644
index af009b96f738..000000000000
--- a/doc/source/diagnostics/libcoredumper.rst
+++ /dev/null
@@ -1,89 +0,0 @@
-.. libcoredumper:
-
-==================================
-Using libcoredumper
-==================================
-
-:Availability: This tool is in tech preview.
-
-This feature was implemented in *Percona Server for MySQL* 8.0.21-12 and has been tested
-against the version's supported platforms. The tool may not be supported on future platforms. You should test before putting this tool into production.
-
-A core dump file is the documented moment of a computer when either the computer or an application exits. Developers examine the dump as one of the tasks when searching for the cause of a failure.
-
-The ``libcoredumper`` is a free and Open Source fork of ``google-coredumper``,
-enhanced to work on newer Linux versions, and GCC and CLANG.
-
-.. rubric:: Enabling the ``libcoredumper``
-
-Enable core dumps for troubleshooting purposes. 
-
-To enable the ``libcoredumper``, add the ``coredumper`` variable to the
-``mysqld`` section of ``my.cnf``. This variable is independent of the
-older ``core-file`` variable.
-
-The variable can have the following possible values: 
-
-.. tabularcolumns:: |p{5cm}|p{11cm}|
-
-.. list-table::
-   :header-rows: 1
-
-   * - Value 
-     - Description
-   * - Blank
-     - The core dump is saved under MySQL datadir and named ``core``.
-   * - A path ending with /
-     - The core dump is saved under the specified directory and named ``core``.
-   * - Full path with a filename
-     - The core dump is saved under the specified directory and filename
-
-Restart the server.
-
-.. rubric:: Verifying the ``libcoredumper`` is Active
-
-MySQL writes to the log when generating a core file and delegates the core
-dump operation to the Linux kernel. An example of the log message is the
-following:
-
-.. code-block:: text
-
-    Writing a core file
-
-MySQL using the ``libcoredumper`` to generate the file creates the following
-message in the log:
-
-.. code-block:: text
-
-    Writing a core file using lib coredumper
-
-Every core file adds a crash timestamp instead of a PID for the following
-reasons:
-
-* Correlates the core file with the crash. MySQL prints a UTC timestamp
-  on the crash log.
-
-    .. code-block:: bash
-
-        10:02:09 UTC - mysqld got signal 11;
-
-* Stores multiple core files.
-
-.. 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.
-
-.. rubric:: Disabling the libcoredumper
-
-You can disable the libcoredumper. A core file may contain sensitive data and
-takes disk space. 
-
-To disable the ``libcoredumper`` you must do the following:
-
-1. In the ``mysqld`` section of my.cnf, remove the ``libcoredumper`` variable.
-
-2. Restart the server.
-
-
diff --git a/doc/source/diagnostics/misc_info_schema_tables.rst b/doc/source/diagnostics/misc_info_schema_tables.rst
deleted file mode 100644
index 7fa6c9a5781d..000000000000
--- a/doc/source/diagnostics/misc_info_schema_tables.rst
+++ /dev/null
@@ -1,90 +0,0 @@
-.. _misc_info_schema_tables:
-
-=================================
- Misc. INFORMATION_SCHEMA Tables
-=================================
-
-This page lists the ``INFORMATION_SCHEMA`` tables added to standard *MySQL* by *Percona Server for MySQL* that don't exist elsewhere in the documentation.
-
-.. _temp_tables:
-
-Temporary tables
-================
-
-.. note::
-
- This feature implementation is considered ALPHA quality.
-
-Only the temporary tables that were explicitly created with `CREATE TEMPORARY TABLE` or `ALTER TABLE` are shown, and not the ones created to process complex queries.
-
-.. _GLOBAL_TEMPORARY_TABLES:
-
-.. rubric:: ``INFORMATION_SCHEMA.GLOBAL_TEMPORARY_TABLES``
-
-.. list-table::
-      :header-rows: 1
-
-      * - Column Name
-        - Description
-      * - 'SESSION_ID'
-        - '*MySQL* connection id'
-      * - 'TABLE_SCHEMA'
-        - 'Schema in which the temporary table is created'
-      * - 'TABLE_NAME'
-        - 'Name of the temporary table'
-      * - 'ENGINE'
-        - 'Engine of the temporary table'
-      * - 'NAME'
-        - 'Internal name of the temporary table'
-      * - 'TABLE_ROWS'
-        - 'Number of rows of the temporary table'
-      * - 'AVG_ROW_LENGTH'
-        - 'Average row length of the temporary table'
-      * - 'DATA_LENGTH'
-        - 'Size of the data (Bytes)'
-      * - 'INDEX_LENGTH'
-        - 'Size of the indexes (Bytes)'
-      * - 'CREATE_TIME'
-        - 'Date and time of creation of the temporary table'
-      * - 'UPDATE_TIME'
-        - 'Date and time of the latest update of the temporary table'
-
-The feature was ported from *Percona Server for MySQL* 5.7 in :ref:`8.0.12-1`.
-
-This table holds information on the temporary tables that exist for all connections. You don't need the ``SUPER`` privilege to query this table.
-
-.. _TEMPORARY_TABLES:
-
-.. rubric:: ``INFORMATION_SCHEMA.TEMPORARY_TABLES``
-
-.. list-table::
-      :header-rows: 1
-
-      * - Column Name
-        - Description
-      * - 'SESSION_ID'
-        - '*MySQL* connection id'
-      * - 'TABLE_SCHEMA'
-        - 'Schema in which the temporary table is created'
-      * - 'TABLE_NAME'
-        - 'Name of the temporary table'
-      * - 'ENGINE'
-        - 'Engine of the temporary table'
-      * - 'NAME'
-        - 'Internal name of the temporary table'
-      * - 'TABLE_ROWS'
-        - 'Number of rows of the temporary table'
-      * - 'AVG_ROW_LENGTH'
-        - 'Average row length of the temporary table'
-      * - 'DATA_LENGTH'
-        - 'Size of the data (Bytes)'
-      * - 'INDEX_LENGTH'
-        - 'Size of the indexes (Bytes)'
-      * - 'CREATE_TIME'
-        - 'Date and time of creation of the temporary table'
-      * - 'UPDATE_TIME'
-        - 'Date and time of the latest update of the temporary table'
-
-The feature was ported from *Percona Server for MySQL* 5.7 in :ref:`8.0.12-1`.
-
-This table holds information on the temporary tables existing for the running connection.
diff --git a/doc/source/diagnostics/process_list.rst b/doc/source/diagnostics/process_list.rst
deleted file mode 100644
index 09d6fe3ed2fb..000000000000
--- a/doc/source/diagnostics/process_list.rst
+++ /dev/null
@@ -1,65 +0,0 @@
-.. _process_list:
-
-=============
-Process List
-=============
-
-This page describes Percona changes to both the standard *MySQL* ``SHOW PROCESSLIST`` command and the standard *MySQL* ``INFORMATION_SCHEMA`` table ``PROCESSLIST``.
-
-Version Specific Information
-============================
-
-  * `8.0.12-1`: The feature was ported from *Percona Server for MySQL* 5.7.
-
-INFORMATION_SCHEMA Tables
-=========================
-
-.. _PROCESSLIST:
-
-``INFORMATION_SCHEMA.PROCESSLIST``
-
-This table implements modifications to the standard MySQL ``INFORMATION_SCHEMA`` table ``PROCESSLIST``.
-
-.. list-table::
-      :header-rows: 1
-
-      * - Column Name
-        - Description
-      * - 'ID'
-        - 'The connection identifier.'
-      * - 'USER'
-        - 'The MySQL user who issued the statement.'
-      * - 'HOST'
-        - 'The host name of the client issuing the statement.'
-      * - 'DB'
-        - 'The default database, if one is selected, otherwise NULL.'
-      * - 'COMMAND'
-        - 'The type of command the thread is executing.'
-      * - 'TIME'
-        - 'The time in seconds that the thread has been in its current state.'
-      * - 'STATE'
-        - 'An action, event, or state that indicates what the thread is doing.'
-      * - 'INFO'
-        - 'The statement that the thread is executing, or NULL if it is not executing any statement.'
-      * - 'TIME_MS'
-        - 'The time in milliseconds that the thread has been in its current state.'
-      * - 'ROWS_EXAMINED'
-        - 'The number of rows examined by the statement being executed (*NOTE:* This column is not updated for each examined row so it does not necessarily show an up-to-date value while the statement is executing. It only shows a correct value after the statement has completed.).'
-      * - 'ROWS_SENT'
-        - 'The number of rows sent by the statement being executed.'
-      * - 'TID'
-        - 'The Linux Thread ID. For Linux, this corresponds to light-weight process ID (LWP ID) and can be seen in the ``ps -L`` output. In case when :ref:`threadpool` is enabled, "TID" is not null for only currently executing statements and statements received via "extra" connection.'
-
-Example Output
-==============
-
-Table :ref:`PROCESSLIST`: ::
-
-  mysql> SELECT * FROM INFORMATION_SCHEMA.PROCESSLIST;
-
-  +----+------+-----------+--------------------+---------+------+-----------+---------------------------+---------+-----------+---------------+
-  | ID | USER | HOST      | DB                 | COMMAND | TIME | STATE     | INFO                      | TIME_MS | ROWS_SENT | ROWS_EXAMINED |
-  +----+------+-----------+--------------------+---------+------+-----------+---------------------------+---------+-----------+---------------+
-  | 12 | root | localhost | information_schema | Query   |    0 | executing | select * from processlist |       0 |         0 |             0 |
-  +----+------+-----------+--------------------+---------+------+-----------+---------------------------+---------+-----------+---------------+
-
diff --git a/doc/source/diagnostics/show_engines.rst b/doc/source/diagnostics/show_engines.rst
deleted file mode 100644
index 84df955736c2..000000000000
--- a/doc/source/diagnostics/show_engines.rst
+++ /dev/null
@@ -1,33 +0,0 @@
-.. _show_engines:
-
-======================
- Show Storage Engines
-======================
-
-This feature changes the comment field displayed when the ``SHOW STORAGE ENGINES`` command is executed and |XtraDB| is the storage engine.
-
-Before the Change: ::
-
-  mysql> show storage engines;
-  +------------+---------+----------------------------------------------------------------+--------------+------+------------+
-  | Engine     | Support | Comment                                                        | Transactions | XA   | Savepoints |
-  +------------+---------+----------------------------------------------------------------+--------------+------+------------+
-  | InnoDB     | YES     | Supports transactions, row-level locking, and foreign keys     | YES          | YES  | YES        |
-  ...
-  +------------+---------+----------------------------------------------------------------+--------------+------+------------+
-
-After the Change: ::
-
-  mysql> show storage engines;
-  +------------+---------+----------------------------------------------------------------------------+--------------+------+------------+ 
-  | Engine     | Support | Comment                                                                    | Transactions |   XA | Savepoints |
-  +------------+---------+----------------------------------------------------------------------------+--------------+------+------------+
-  | InnoDB     | YES     | Percona-XtraDB, Supports transactions, row-level locking, and foreign keys |          YES | YES  | YES        |
-  ...
-  +------------+---------+----------------------------------------------------------------------------+--------------+------+------------+
-
-Version-Specific Information
-============================
-
-  * `8.0.12-1`: The feature was ported from *Percona Server for MySQL* 5.7.
-
diff --git a/doc/source/diagnostics/slow_extended.rst b/doc/source/diagnostics/slow_extended.rst
deleted file mode 100644
index 9a8839d262fe..000000000000
--- a/doc/source/diagnostics/slow_extended.rst
+++ /dev/null
@@ -1,488 +0,0 @@
-.. _slow_extended:
-
-================
- Slow Query Log
-================
-
-This feature adds microsecond time resolution and additional statistics to the slow query log output. It lets you enable or disable the slow query log at runtime, adds logging for the replica SQL thread, and adds fine-grained control over what and how much to log into the slow query log.
-
-You can use *Percona-Toolkit*'s `pt-query-digest <http://www.percona.com/doc/percona-toolkit/2.1/pt-query-digest.html>`_ tool to aggregate similar queries together and report on those that consume the most execution time.
-
-
-Version Specific Information
-============================
-
-  * `8.0.12-1`: The feature was ported from *Percona Server for MySQL* 5.7.
-
-System Variables
-================
-
-.. _log_slow_filter:
-
-.. rubric:: ``log_slow_filter``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - Yes
-   * - Config file
-     - Yes
-   * - Scope
-     - Global, Session
-   * - Dynamic
-     - Yes
-
-Filters the slow log by the query's execution plan. The value is a comma-delimited string, and can contain any combination of the following values:
-
-  * ``full_scan``:
-    The query performed a full table scan.
-
-  * ``full_join``:
-    The query performed a full join (a join without indexes).
-
-  * ``tmp_table``:
-    The query created an implicit internal temporary table.
-
-  * ``tmp_table_on_disk``:
-    The query's temporary table was stored on disk.
-
-  * ``filesort``:
-    The query used a filesort.
-
-  * ``filesort_on_disk``:
-    The filesort was performed on disk.
-
-Values are OR'ed together. If the string is empty, then the filter is disabled. If it is not empty, then queries will only be logged to the slow log if their execution plan matches one of the types of plans present in the filter.
-
-For example, to log only queries that perform a full table scan, set the value to ``full_scan``. To log only queries that use on-disk temporary storage for intermediate results, set the value to ``tmp_table_on_disk,filesort_on_disk``.
-
-.. _log_slow_rate_type:
-
-.. rubric:: ``log_slow_rate_type``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - Yes
-   * - Config file
-     - Yes
-   * - Scope
-     - Global
-   * - Dynamic
-     - Yes
-   * - Data type
-     - Enumerated
-   * - Default
-     - ``session``
-   * - Range
-     - ``session``, ``query``
-
-Specifies semantic of :ref:`log_slow_rate_limit` - ``session`` or ``query``.
-
-.. _log_slow_rate_limit:
-
-.. rubric:: ``log_slow_rate_limit``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - Yes
-   * - Config file
-     - Yes
-   * - Scope
-     - Global, session
-   * - Dynamic
-     - Yes
-   * - Default
-     - 1
-   * - Range
-     - 1-1000
-
-Behavior of this variable depends from :ref:`log_slow_rate_type`.
-
-Specifies that only a fraction of ``session/query`` should be logged. Logging is enabled for every nth ``session/query``. By default, n is 1, so logging is enabled for every ``session/query``. Please note: when :ref:`log_slow_rate_type` is ``session`` rate limiting is disabled for the replication thread.
-
-Logging all queries might consume I/O bandwidth and cause the log file to grow large.
- * When :ref:`log_slow_rate_type` is ``session``, this option lets you log full sessions, so you have complete records of sessions for later analysis; but you can rate-limit the number of sessions that are logged. Note that this feature will not work well if your application uses any type of connection pooling or persistent connections. Note that you change :ref:`log_slow_rate_limit` in ``session`` mode, you should reconnect for get effect.
-
- * When :ref:`log_slow_rate_type` is ``query``, this option lets you log just some queries for later analysis. For example, if you set the value to 100, then one percent of queries will be logged.
-
-Note that every query has global unique ``query_id`` and every connection can has it own (session) :ref:`log_slow_rate_limit`.
-Decision "log or no" calculated in following manner:
-
- * if ``log_slow_rate_limit`` is 1 - log every query
-
- * If ``log_slow_rate_limit`` > 1 - randomly log every 1/``log_slow_rate_limit`` query. 
-
-This allows flexible setup logging behavior.
-
-For example, if you set the value to 100, then one percent of ``sessions/queries`` will be logged. In *Percona Server for MySQL* information about the :ref:`log_slow_rate_limit` has been added to the slow query log. This means that if the :ref:`log_slow_rate_limit` is effective it will be reflected in the slow query log for each written query. Example of the output looks like this: ::
- 
-  Log_slow_rate_type: query  Log_slow_rate_limit: 10
-
-.. _log_slow_sp_statements:
-
-.. rubric:: ``log_slow_sp_statements``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - Yes
-   * - Config file
-     - Yes
-   * - Scope
-     - Global
-   * - Dynamic
-     - Yes
-   * - Data type
-     - Boolean
-   * - Default
-     - TRUE
-   * - Range
-     - TRUE/FALSE
-
-If ``TRUE``, statements executed by stored procedures are logged to the slow if it is open.
-
-.. _improved_sp_reporting:
-
-*Percona Server for MySQL* implemented improvements for logging of stored procedures to the slow query log:
- * Each query from a stored procedure is now logged to the slow query log individually
- * ``CALL`` itself isn't logged to the slow query log anymore as this would be counting twice for the same query which would lead to incorrect results
- * Queries that were called inside of stored procedures are annotated in the slow query log with the stored procedure name in which they run.
-
-Example of the improved stored procedure slow query log entry:
-
-.. code-block:: mysql
-
-   mysql> DELIMITER //
-   mysql> CREATE PROCEDURE improved_sp_log()
-          BEGIN
-           SELECT * FROM City;
-           SELECT * FROM Country;
-          END//
-   mysql> DELIMITER ;
-   mysql> CALL improved_sp_log();
-
-When we check the slow query log after running the stored procedure ,with variable:`log_slow_sp_statements` set to ``TRUE``, it should look like this: ::
-
-   # Time: 150109 11:38:55
-   # User@Host: root[root] @ localhost []
-   # Thread_id: 40  Schema: world  Last_errno: 0  Killed: 0
-   # Query_time: 0.012989  Lock_time: 0.000033  Rows_sent: 4079  Rows_examined: 4079  Rows_affected: 0  Rows_read: 4079
-   # Bytes_sent: 161085
-   # Stored routine: world.improved_sp_log
-   SET timestamp=1420803535;
-   SELECT * FROM City;
-   # User@Host: root[root] @ localhost []
-   # Thread_id: 40  Schema: world  Last_errno: 0  Killed: 0
-   # Query_time: 0.001413  Lock_time: 0.000017  Rows_sent: 4318  Rows_examined: 4318  Rows_affected: 0  Rows_read: 4318
-   # Bytes_sent: 194601
-   # Stored routine: world.improved_sp_log
-   SET timestamp=1420803535;
-
-If variable :ref:`log_slow_sp_statements` is set to ``FALSE``:
-
- * Entry is added to a slow-log for a ``CALL`` statement only and not for any of the individual statements run in that stored procedure
- * Execution time is reported for the ``CALL`` statement as the total execution time of the ``CALL`` including all its statements
-
-If we run the same stored procedure with the variable :ref:`log_slow_sp_statements` is set to ``FALSE`` slow query log should look like this: ::
-
-  # Time: 150109 11:51:42
-  # User@Host: root[root] @ localhost []
-  # Thread_id: 40  Schema: world  Last_errno: 0  Killed: 0
-  # Query_time: 0.013947  Lock_time: 0.000000  Rows_sent: 4318  Rows_examined: 4318  Rows_affected: 0  Rows_read: 4318
-  # Bytes_sent: 194612
-  SET timestamp=1420804302;
-  CALL improved_sp_log();
-
-.. note::
-
- Support for logging stored procedures doesn't involve triggers, so they won't be logged even if this feature is enabled.
-
-.. _log_slow_verbosity:
-
-.. rubric:: ``log_slow_verbosity``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - Yes
-   * - Config file
-     - Yes
-   * - Scope
-     - Global, session
-   * - Dynamic
-     - Yes
-
-Specifies how much information to include in your slow log. The value is a comma-delimited string, and can contain any combination of the following values:
-
-  * ``microtime``:
-    Log queries with microsecond precision.
-
-  * ``query_plan``:
-    Log information about the query's execution plan.
-
-  * ``innodb``:
-    Log *InnoDB* statistics.
-
-  * ``minimal``:
-    Equivalent to enabling just ``microtime``.
-
-  * ``standard``:
-    Equivalent to enabling ``microtime,query_plan``.
-
-  * ``full``:
-    Equivalent to all other values OR'ed together without the ``profiling`` and ``profiling_use_getrusage`` options.
-
-  * ``profiling``:
-    Enables profiling of all queries in all connections.
-
-  * ``profiling_use_getrusage``:
-    Enables usage of the getrusage function.
-
-  * ``query_info``: 
-    Enables printing ``Query_tables`` and ``Query_digest`` into the slow query log. These fields are disabled by default.
-
-Values are OR'ed together.
-
-For example, to enable microsecond query timing and *InnoDB* statistics, set this option to ``microtime,innodb`` or ``standard``. To turn all options on, set the option to ``full``.
-
-.. _slow_query_log_use_global_control:
-
-.. rubric:: ``slow_query_log_use_global_control``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - Yes
-   * - Config file
-     - Yes
-   * - Scope
-     - Global
-   * - Dynamic
-     - Yes
-   * - Default
-     - None
-
-Specifies which variables have global scope instead of local. For such variables, the global variable value is used in the current session, but without copying this value to the session value. Value is a "flag" variable - you can specify multiple values separated by commas
-
-  * ``none``:
-    All variables use local scope
-
-  * ``log_slow_filter``:
-    Global variable :ref:`log_slow_filter` has effect (instead of local)
-
-  * ``log_slow_rate_limit``:
-    Global variable :ref:`log_slow_rate_limit` has effect (instead of local)
-
-  * ``log_slow_verbosity``:
-    Global variable :ref:`log_slow_verbosity` has effect (instead of local)
-
-  * ``long_query_time``:
-    Global variable :ref:`long_query_time` has effect (instead of local)
-
-  * ``min_examined_row_limit``:
-    Global variable ``min_examined_row_limit`` has effect (instead of local)
-
-  * ``all``
-    Global variables has effect (instead of local)
-
-.. _slow_query_log_always_write_time:
-
-.. rubric:: ``slow_query_log_always_write_time``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - Yes
-   * - Config file
-     - Yes
-   * - Scope
-     - Global
-   * - Dynamic
-     - Yes
-   * - Default
-     - 10
-
-This variable can be used to specify the query execution time after which the query will be written to the slow query log. It can be used to specify an additional execution time threshold for the slow query log, that, when exceeded, will cause a query to be logged unconditionally, that is, :ref:`log_slow_rate_limit` will not apply to it.
-
-Other Information
-=================
-
-Changes to the Log Format
--------------------------
-
-The feature adds more information to the slow log output. Here is a sample log entry: ::
-
-  # Time: 130601  8:01:06.058915
-  # User@Host: root[root] @ localhost []  Id:    42
-  # Schema: imdb  Last_errno: 0  Killed: 0
-  # Query_time: 7.725616  Lock_time: 0.000328  Rows_sent: 4  Rows_examined: 1543720  Rows_affected: 0
-  # Bytes_sent: 272  Tmp_tables: 0  Tmp_disk_tables: 0  Tmp_table_sizes: 0
-  # Full_scan: Yes  Full_join: No  Tmp_table: No  Tmp_table_on_disk: No
-  # Filesort: No  Filesort_on_disk: No  Merge_passes: 0
-  SET timestamp=1370073666;
-  SELECT id,title,production_year FROM title WHERE title = 'Bambi';
-
-
-Another example (:ref:`log_slow_verbosity` ``=profiling``): ::
-
-  # Time: 130601  8:03:20.700441
-  # User@Host: root[root] @ localhost []  Id:    43
-  # Schema: imdb  Last_errno: 0  Killed: 0
-  # Query_time: 7.815071  Lock_time: 0.000261  Rows_sent: 4  Rows_examined: 1543720  Rows_affected: 0
-  # Bytes_sent: 272
-  # Profile_starting: 0.000125 Profile_starting_cpu: 0.000120 
-  Profile_checking_permissions: 0.000021 Profile_checking_permissions_cpu: 0.000021 
-  Profile_Opening_tables: 0.000049 Profile_Opening_tables_cpu: 0.000048 Profile_init: 0.000048 
-  Profile_init_cpu: 0.000049 Profile_System_lock: 0.000049 Profile_System_lock_cpu: 0.000048 
-  Profile_optimizing: 0.000024 Profile_optimizing_cpu: 0.000024 Profile_statistics: 0.000036 
-  Profile_statistics_cpu: 0.000037 Profile_preparing: 0.000029 Profile_preparing_cpu: 0.000029 
-  Profile_executing: 0.000012 Profile_executing_cpu: 0.000012 Profile_Sending_data: 7.814583 
-  Profile_Sending_data_cpu: 7.811634 Profile_end: 0.000013 Profile_end_cpu: 0.000012 
-  Profile_query_end: 0.000014 Profile_query_end_cpu: 0.000014 Profile_closing_tables: 0.000023 
-  Profile_closing_tables_cpu: 0.000023 Profile_freeing_items: 0.000051 
-  Profile_freeing_items_cpu: 0.000050 Profile_logging_slow_query: 0.000006 
-  Profile_logging_slow_query_cpu: 0.000006 
-  # Profile_total: 7.815085 Profile_total_cpu: 7.812127 
-  SET timestamp=1370073800;
-  SELECT id,title,production_year FROM title WHERE title = 'Bambi';
-
-Notice that the ``Killed: `` keyword is followed by zero when the
-query successfully completes. If the query was killed, the ``Killed:``
-keyword is followed by a number other than zero:
-
-====================  =================================================
-Killed Numeric Code   Exception
-====================  =================================================
-0                     NOT_KILLED
-1                     KILL_BAD_DATA
-1053                  ER_SERVER_SHUTDOWN (see |MySQL| Documentation)
-1317                  ER_QUERY_INTERRUPTED (see |MySQL| Documentation)
-3024                  ER_QUERY_TIMEOUT (see |MySQL| Documentation)
-Any other number      KILLED_NO_VALUE (Catches all other cases)
-====================  =================================================
-
-.. seealso::
-
-   |MySQL| Documentation: |MySQL| Server Error Codes
-      https://dev.mysql.com/doc/mysql-errors/8.0/en/server-error-reference.html
-
-Connection and Schema Identifier
---------------------------------
-
-Each slow log entry now contains a connection identifier, so you can trace all the queries coming from a single connection. This is the same value that is shown in the Id column in ``SHOW FULL PROCESSLIST`` or returned from the ``CONNECTION_ID()`` function.
-
-Each entry also contains a schema name, so you can trace all the queries whose default database was set to a particular schema. ::
-
-  # Id: 43  Schema: imdb
-
-Microsecond Time Resolution and Extra Row Information
------------------------------------------------------
-
-This is the original functionality offered by the ``microslow`` feature. ``Query_time`` and ``Lock_time`` are logged with microsecond resolution.
-
-The feature also adds information about how many rows were examined for ``SELECT`` queries, and how many were analyzed and affected for ``UPDATE``, ``DELETE``, and ``INSERT`` queries, ::
-
-  # Query_time: 0.962742  Lock_time: 0.000202  Rows_sent: 4  Rows_examined: 1543719  Rows_affected: 0
-
-Values and context:
-
-  * ``Rows_examined``:
-    Number of rows scanned - ``SELECT``
-
-  * ``Rows_affected``:
-    Number of rows changed - ``UPDATE``, ``DELETE``, ``INSERT``
-
-Memory Footprint
-----------------
-
-The feature provides information about the amount of bytes sent for the result of the query and the number of temporary tables created for its execution - differentiated by whether they were created on memory or on disk - with the total number of bytes used by them. :: 
-
-  # Bytes_sent: 8053  Tmp_tables: 1  Tmp_disk_tables: 0  Tmp_table_sizes: 950528
-
-Values and context:
-
-  * ``Bytes_sent``:
-    The amount of bytes sent for the result of the query
-
-  * ``Tmp_tables``:
-    Number of temporary tables created on memory for the query
-
-  * ``Tmp_disk_tables``:
-    Number of temporary tables created on disk for the query
-
-  * ``Tmp_table_sizes``:
-    Total Size in bytes for all temporary tables used in the query
-
-
-Query Plan Information
-----------------------
-
-Each query can be executed in various ways. For example, it may use indexes or do a full table scan, or a temporary table may be needed. These are the things that you can usually see by running ``EXPLAIN`` on the query. The feature will now allow you to see the most important facts about the execution in the log file. ::
-
-  # Full_scan: Yes  Full_join: No  Tmp_table: No  Tmp_table_on_disk: No
-  # Filesort: No  Filesort_on_disk: No  Merge_passes: 0
-
-The values and their meanings are documented with the :ref:`log_slow_filter` option.
-
-*InnoDB* Usage Information
---------------------------
-
-The final part of the output is the *InnoDB* usage statistics. *MySQL* currently shows many per-session statistics for operations with ``SHOW SESSION STATUS``, but that does not include those of |InnoDB|, which are always global and shared by all threads. This feature lets you see those values for a given query. ::
-
-  #   InnoDB_IO_r_ops: 6415  InnoDB_IO_r_bytes: 105103360  InnoDB_IO_r_wait: 0.001279
-  #   InnoDB_rec_lock_wait: 0.000000  InnoDB_queue_wait: 0.000000
-  #   InnoDB_pages_distinct: 6430
-
-Values:
-
-  * ``innodb_IO_r_ops``:
-    Counts the number of page read operations scheduled. The actual number of read operations may be different, but since this can be done asynchronously, there is no good way to measure it.
-
-  * ``innodb_IO_r_bytes``:
-    Similar to innodb_IO_r_ops, but the unit is bytes.
-
-  * ``innodb_IO_r_wait``:
-    Shows how long (in seconds) it took *InnoDB* to actually read the data from storage.
-
-  * ``innodb_rec_lock_wait``:
-    Shows how long (in seconds) the query waited for row locks.
-
-  * ``innodb_queue_wait``:
-    Shows how long (in seconds) the query spent either waiting to enter the *InnoDB* queue or inside that queue waiting for execution.
-
-  * ``innodb_pages_distinct``:
-    Counts approximately the number of unique pages the query accessed. The approximation is based on a small hash array representing the entire buffer pool, because it could take a lot of memory to map all the pages. The inaccuracy grows with the number of pages accessed by a query, because there is a higher probability of hash collisions.
-
-If the query did not use *InnoDB* tables, that information is written into the log instead of the above statistics.
-
-Related Reading
-===============
-
-  * `Impact of logging on MySQL's performance <http://www.mysqlperformanceblog.com/2009/02/10/impact-of-logging-on-mysql%E2%80%99s-performance/>`_
-
-  * `log_slow_filter Usage <http://www.mysqlperformanceblog.com/2008/09/22/finding-what-created_tmp_disk_tables-with-log_slow_filter/>`_
-
-  * `Added microseconds to the slow query log event time <https://jira.percona.com/browse/PS-1136>`_
diff --git a/doc/source/diagnostics/stacktrace.rst b/doc/source/diagnostics/stacktrace.rst
deleted file mode 100644
index 7474fc842038..000000000000
--- a/doc/source/diagnostics/stacktrace.rst
+++ /dev/null
@@ -1,21 +0,0 @@
-.. stacktrace:
-
-=================================
-Stack Trace
-=================================
-
-Developers use the stack trace in the debug process, either an interactive investigation or during the post-mortem. No configuration is required to generate a stack trace. 
-
-Implemented in *Percona Server for MySQL* 8.0.21-12, stack trace adds the following: 
-
-.. tabularcolumns:: |p{5cm}|p{11cm}|
-
-.. list-table::
-   :header-rows: 1
-
-   * - Name 
-     - Description
-   * - Prints binary BuildID
-     - The Strip utility removes unneeded sections and debugging information to reduce the size. This method is standard with containers where the size of the image is essential. The BuildID lets you resolve the stack trace when the Strip utility removes the binary symbols table.
-   * - Print the server version information
-     - The version information establishes the starting point for analysis. Some applications, such as MySQL, only print this information to a log on startup, and when the crash occurs, the size of the log may be large, rotated, or truncated.  
diff --git a/doc/source/diagnostics/thread_based_profiling.rst b/doc/source/diagnostics/thread_based_profiling.rst
deleted file mode 100644
index c5fe6fb82499..000000000000
--- a/doc/source/diagnostics/thread_based_profiling.rst
+++ /dev/null
@@ -1,17 +0,0 @@
-.. _thread_based_profiling:
-
-=========================
- Thread Based Profiling
-=========================
-
-*Percona Server for MySQL* now uses thread based profiling by default, instead of process based profiling. This was implemented because with process based profiling, threads on the server, other than the one being profiled, can affect the profiling information. 
-
-Thread based profiling is using the information provided by the kernel `getrusage <http://kernel.org/doc/man-pages/online/pages/man2/getrusage.2.html>`_ function. Since the 2.6.26 kernel version, thread based resource usage is available with the **RUSAGE_THREAD**. This means that the thread based profiling will be used if you're running the 2.6.26 kernel or newer, or if the **RUSAGE_THREAD** has been ported back.
-
-This feature is enabled by default if your system supports it, in other cases it uses process based profiling.
-
-Version Specific Information
-============================
-
-  * `8.0.12-1`: The feature was ported from *Percona Server for MySQL* 5.7.
-
diff --git a/doc/source/diagnostics/user_stats.rst b/doc/source/diagnostics/user_stats.rst
deleted file mode 100644
index a7d4c0a6d9d0..000000000000
--- a/doc/source/diagnostics/user_stats.rst
+++ /dev/null
@@ -1,477 +0,0 @@
-.. _user_stats:
-
-=================
- User Statistics
-=================
-
-This feature adds several ``INFORMATION_SCHEMA`` tables, several commands, and the userstat variable. The tables and commands can be used to understand the server activity better and identify the source of the load.
-
-The functionality is disabled by default, and must be enabled by setting ``userstat`` to ``ON``. It works by keeping several hash tables in memory. To avoid contention over global mutexes, each connection has its own local statistics, which are occasionally merged into the global statistics, and the local statistics are then reset to 0.
-
-
-Version Specific Information
-============================
-
-  * `8.0.12-1`: The feature was ported from *Percona Server for MySQL* 5.7.
-
-Other Information
-=================
-
-  * Author/Origin:
-     *Google*; *Percona* added the ``INFORMATION_SCHEMA`` tables and the :ref:`userstat` variable.
-
-System Variables
-================
-
-.. _userstat:
-
-.. rubric:: ``userstat``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - Yes
-   * - Config file
-     - Yes
-   * - Scope
-     - Global
-   * - Dynamic
-     - Yes
-   * - Data type
-     - BOOLEAN
-   * - Default
-     - OFF
-   * - Range
-     - ON/OFF
-
-Enables or disables collection of statistics. The default is ``OFF``, meaning no statistics are gathered. This is to ensure that the statistics collection doesn't cause any extra load on the server unless desired.
-
-.. _thread_statistics:
-
-.. rubric:: ``thread_statistics``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - Yes
-   * - Config file
-     - Yes
-   * - Scope
-     - Global
-   * - Dynamic
-     - Yes
-   * - Data type
-     - BOOLEAN
-   * - Default
-     - OFF
-   * - Range
-     - ON/OFF
-
-Enables or disables collection of thread statistics. The default is ``OFF``, meaning no thread statistics are gathered. This is to ensure that the statistics collection doesn't cause any extra load on the server unless desired. Variable :ref:`userstat` needs to be enabled as well in order for thread statistics to be collected.
-
-INFORMATION_SCHEMA Tables
-=========================
-
-.. _CLIENT_STATISTICS:
-
-.. rubric:: ``INFORMATION_SCHEMA.CLIENT_STATISTICS``
-
-.. list-table::
-      :header-rows: 1
-
-      * - Column Name
-        - Description
-      * - 'CLIENT'
-        - 'The IP address or hostname from which the connection originated.'
-      * - 'TOTAL_CONNECTIONS'
-        - 'The number of connections created for this client.'
-      * - 'CONCURRENT_CONNECTIONS'
-        - 'The number of concurrent connections for this client.'
-      * - 'CONNECTED_TIME'
-        - 'The cumulative number of seconds elapsed while there were connections from this client.'
-      * - 'BUSY_TIME'
-        - 'The cumulative number of seconds there was activity on connections from this client.'
-      * - 'CPU_TIME'
-        - 'The cumulative CPU time elapsed, in seconds, while servicing this client's connections.'
-      * - 'BYTES_RECEIVED'
-        - 'The number of bytes received from this client's connections.'
-      * - 'BYTES_SENT'
-        - 'The number of bytes sent to this client's connections.'
-      * - 'BINLOG_BYTES_WRITTEN'
-        - 'The number of bytes written to the binary log from this client's connections.'
-      * - 'ROWS_FETCHED'
-        - 'The number of rows fetched by this client's connections.'
-      * - 'ROWS_UPDATED'
-        - 'The number of rows updated by this client's connections.'
-      * - 'TABLE_ROWS_READ'
-        - 'The number of rows read from tables by this client's connections. (It may be different from ``ROWS_FETCHED``.)'
-      * - 'SELECT_COMMANDS'
-        - 'The number of ``SELECT`` commands executed from this client's connections.'
-      * - 'UPDATE_COMMANDS'
-        - 'The number of ``UPDATE`` commands executed from this client's connections.'
-      * - 'OTHER_COMMANDS'
-        - 'The number of other commands executed from this client's connections.'
-      * - 'COMMIT_TRANSACTIONS'
-        - 'The number of ``COMMIT`` commands issued by this client's connections.'
-      * - 'ROLLBACK_TRANSACTIONS'
-        - 'The number of ``ROLLBACK`` commands issued by this client's connections.'
-      * - 'DENIED_CONNECTIONS'
-        - 'The number of connections denied to this client.'
-      * - 'LOST_CONNECTIONS'
-        - 'The number of this client's connections that were terminated uncleanly.'
-      * - 'ACCESS_DENIED'
-        - 'The number of times this client's connections issued commands that were denied.'
-      * - 'EMPTY_QUERIES'
-        - 'The number of times this client's connections sent empty queries to the server.'
-
-This table holds statistics about client connections. The Percona version of the feature restricts this table's visibility to users who have the ``SUPER`` or ``PROCESS`` privilege.
-
-Example: ::
-
-  mysql> SELECT * FROM INFORMATION_SCHEMA.CLIENT_STATISTICS\G
-  *************************** 1. row ***************************
-                  CLIENT: 10.1.12.30
-       TOTAL_CONNECTIONS: 20
-  CONCURRENT_CONNECTIONS: 0
-          CONNECTED_TIME: 0
-               BUSY_TIME: 93
-                CPU_TIME: 48
-          BYTES_RECEIVED: 5031
-              BYTES_SENT: 276926
-    BINLOG_BYTES_WRITTEN: 217
-            ROWS_FETCHED: 81
-            ROWS_UPDATED: 0
-         TABLE_ROWS_READ: 52836023
-         SELECT_COMMANDS: 26
-         UPDATE_COMMANDS: 1
-          OTHER_COMMANDS: 145
-     COMMIT_TRANSACTIONS: 1
-   ROLLBACK_TRANSACTIONS: 0
-      DENIED_CONNECTIONS: 0
-        LOST_CONNECTIONS: 0
-           ACCESS_DENIED: 0
-           EMPTY_QUERIES: 0
-
-
-INFORMATION_SCHEMA Tables
-=========================
-
-.. _INDEX_STATISTICS:
-
-.. rubric:: ``INFORMATION_SCHEMA.INDEX_STATISTICS``
-
-.. list-table::
-      :header-rows: 1
-
-      * - Column Name
-        - Description
-      * - 'TABLE_SCHEMA'
-        - 'The schema (database) name.'
-      * - 'TABLE_NAME'
-        - 'The table name.'
-      * - 'INDEX_NAME'
-        - 'The index name (as visible in ``SHOW CREATE TABLE``).'
-      * - 'ROWS_READ'
-        - 'The number of rows read from this index.'
-
-This table shows statistics on index usage. An older version of the feature contained a single column that had the ``TABLE_SCHEMA``, ``TABLE_NAME`` and ``INDEX_NAME`` columns concatenated together. The *Percona* version of the feature separates these into three columns. Users can see entries only for tables to which they have ``SELECT`` access.
-
-This table makes it possible to do many things that were difficult or impossible previously. For example, you can use it to find unused indexes and generate DROP commands to remove them.
-
-Example: ::
-
-  mysql> SELECT * FROM INFORMATION_SCHEMA.INDEX_STATISTICS
-     WHERE TABLE_NAME='tables_priv';
-  +--------------+-----------------------+--------------------+-----------+
-  | TABLE_SCHEMA | TABLE_NAME            | INDEX_NAME         | ROWS_READ |
-  +--------------+-----------------------+--------------------+-----------+
-  | mysql        | tables_priv           | PRIMARY            |         2 |
-  +--------------+-----------------------+--------------------+-----------+
-
-.. note:: 
-
-   Current implementation of index statistics doesn't support partitioned tables.
-
-.. _TABLE_STATISTICS:
-
-.. rubric:: ``INFORMATION_SCHEMA.TABLE_STATISTICS``
-
-.. list-table::
-      :header-rows: 1
-
-      * - Column Name
-        - Description
-      * - 'TABLE_SCHEMA'
-        - 'The schema (database) name.'
-      * - 'TABLE_NAME'
-        - 'The table name.'
-      * - 'ROWS_READ'
-        - 'The number of rows read from the table.'
-      * - 'ROWS_CHANGED'
-        - 'The number of rows changed in the table.'
-      * - 'ROWS_CHANGED_X_INDEXES'
-        - 'The number of rows changed in the table, multiplied by the number of indexes changed.'
-
-This table is similar in function to the ``INDEX_STATISTICS`` table.
-
-Example: ::
-
-  mysql> SELECT * FROM INFORMATION_SCHEMA.TABLE_STATISTICS
-     WHERE TABLE_NAME=``tables_priv``;
-  +--------------+-------------------------------+-----------+--------------+------------------------+
-  | TABLE_SCHEMA | TABLE_NAME                    | ROWS_READ | ROWS_CHANGED | ROWS_CHANGED_X_INDEXES |
-  +--------------+-------------------------------+-----------+--------------+------------------------+
-  | mysql        | tables_priv                   |         2 |            0 |                      0 | 
-  +--------------+-------------------------------+-----------+--------------+------------------------+
-
-.. note:: 
-
-   Current implementation of table statistics doesn't support partitioned tables.
-
-.. _THREAD_STATISTICS:
-
-.. rubric:: ``INFORMATION_SCHEMA.THREAD_STATISTICS``
-
-.. list-table::
-      :header-rows: 1
-
-      * - Column Name
-        - Description
-      * - 'THREAD_ID'
-        - 'Thread ID'
-      * - 'TOTAL_CONNECTIONS'
-        - 'The number of connections created from this thread.'
-      * - 'CONNECTED_TIME'
-        - 'The cumulative number of seconds elapsed while there were connections from this thread.'
-      * - 'BUSY_TIME'
-        - 'The cumulative number of seconds there was activity from this thread.'
-      * - 'CPU_TIME'
-        - 'The cumulative CPU time elapsed while servicing this thread.'
-      * - 'BYTES_RECEIVED'
-        - 'The number of bytes received from this thread.'
-      * - 'BYTES_SENT'
-        - 'The number of bytes sent to this thread.'
-      * - 'BINLOG_BYTES_WRITTEN'
-        - 'The number of bytes written to the binary log from this thread.'
-      * - 'ROWS_FETCHED'
-        - 'The number of rows fetched by this thread.'
-      * - 'ROWS_UPDATED'
-        - 'The number of rows updated by this thread.'
-      * - 'TABLE_ROWS_READ'
-        - 'The number of rows read from tables by this tread.'
-      * - 'SELECT_COMMANDS'
-        - 'The number of ``SELECT`` commands executed from this thread.'
-      * - 'UPDATE_COMMANDS'
-        - 'The number of ``UPDATE`` commands executed from this thread.'
-      * - 'OTHER_COMMANDS'
-        - 'The number of other commands executed from this thread.'
-      * - 'COMMIT_TRANSACTIONS'
-        - 'The number of ``COMMIT`` commands issued by this thread.'
-      * - 'ROLLBACK_TRANSACTIONS'
-        - 'The number of ``ROLLBACK`` commands issued by this thread.'
-      * - 'DENIED_CONNECTIONS'
-        - 'The number of connections denied to this thread.'
-      * - 'LOST_CONNECTIONS'
-        - 'The number of thread connections that were terminated uncleanly.'
-      * - 'ACCESS_DENIED'
-        - 'The number of times this thread issued commands that were denied.'
-      * - 'EMPTY_QUERIES'
-        - 'The number of times this thread sent empty queries to the server.'
-      * - 'TOTAL_SSL_CONNECTIONS'
-        - 'The number of thread connections that used SSL.'
-
-In order for this table to be populated with statistics, additional variable :ref:`thread_statistics` should be set to ``ON``.
-
-.. _USER_STATISTICS:
-
-.. rubric:: ``INFORMATION_SCHEMA.USER_STATISTICS``
-
-.. list-table::
-      :header-rows: 1
-
-      * - Column Name
-        - Description
-      * - 'USER'
-        - 'The username. The value ``#mysql_system_user#`` appears when there is no username (such as for the replica SQL thread).'
-      * - 'TOTAL_CONNECTIONS'
-        - 'The number of connections created from this user.'
-      * - 'CONCURRENT_CONNECTIONS'
-        - 'The number of concurrent connections for this user.'
-      * - 'CONNECTED_TIME'
-        - 'The cumulative number of seconds elapsed while there were connections from this user.'
-      * - 'BUSY_TIME'
-        - 'The cumulative number of seconds there was activity on connections from this user.'
-      * - 'CPU_TIME'
-        - 'The cumulative CPU time elapsed, in seconds, while servicing this user's connections.'
-      * - 'BYTES_RECEIVED'
-        - 'The number of bytes received from this user's connections.'
-      * - 'BYTES_SENT'
-        - 'The number of bytes sent to this user's connections.'
-      * - 'BINLOG_BYTES_WRITTEN'
-        - 'The number of bytes written to the binary log from this user's connections.'
-      * - 'ROWS_FETCHED'
-        - 'The number of rows fetched by this user's connections.'
-      * - 'ROWS_UPDATED'
-        - 'The number of rows updated by this user's connections.'
-      * - 'TABLE_ROWS_READ'
-        - 'The number of rows read from tables by this user's connections. (It may be different from ``ROWS_FETCHED``.)'
-      * - 'SELECT_COMMANDS'
-        - 'The number of ``SELECT`` commands executed from this user's connections.'
-      * - 'UPDATE_COMMANDS'
-        - 'The number of ``UPDATE`` commands executed from this user's connections.'
-      * - 'OTHER_COMMANDS'
-        - 'The number of other commands executed from this user's connections.'
-      * - 'COMMIT_TRANSACTIONS'
-        - 'The number of ``COMMIT`` commands issued by this user's connections.'
-      * - 'ROLLBACK_TRANSACTIONS'
-        - 'The number of ``ROLLBACK`` commands issued by this user's connections.'
-      * - 'DENIED_CONNECTIONS'
-        - 'The number of connections denied to this user.'
-      * - 'LOST_CONNECTIONS'
-        - 'The number of this user's connections that were terminated uncleanly.'
-      * - 'ACCESS_DENIED'
-        - 'The number of times this user's connections issued commands that were denied.'
-      * - 'EMPTY_QUERIES'
-        - 'The number of times this user's connections sent empty queries to the server.'
-
-This table contains information about user activity. The *Percona* version of the patch restricts this table's visibility to users who have the ``SUPER`` or ``PROCESS`` privilege.
-
-The table gives answers to questions such as which users cause the most load, and whether any users are being abusive. It also lets you measure how close to capacity the server may be. For example, you can use it to find out whether replication is likely to start falling behind.
-
-Example: ::
-
-  mysql> SELECT * FROM INFORMATION_SCHEMA.USER_STATISTICS\G
-  *************************** 1. row ***************************
-                    USER: root
-       TOTAL_CONNECTIONS: 5592
-  CONCURRENT_CONNECTIONS: 0
-          CONNECTED_TIME: 6844
-               BUSY_TIME: 179
-                CPU_TIME: 72
-          BYTES_RECEIVED: 603344
-              BYTES_SENT: 15663832
-    BINLOG_BYTES_WRITTEN: 217
-            ROWS_FETCHED: 9793
-            ROWS_UPDATED: 0
-         TABLE_ROWS_READ: 52836023
-         SELECT_COMMANDS: 9701
-         UPDATE_COMMANDS: 1
-          OTHER_COMMANDS: 2614
-     COMMIT_TRANSACTIONS: 1
-   ROLLBACK_TRANSACTIONS: 0
-      DENIED_CONNECTIONS: 0
-        LOST_CONNECTIONS: 0
-           ACCESS_DENIED: 0
-           EMPTY_QUERIES: 0
-
-Commands Provided
-=================
-
-  * ``FLUSH CLIENT_STATISTICS``
-
-  * ``FLUSH INDEX_STATISTICS``
-
-  * ``FLUSH TABLE_STATISTICS``
-
-  * ``FLUSH THREAD_STATISTICS``
-
-  * ``FLUSH USER_STATISTICS``
-
-These commands discard the specified type of stored statistical information.
-
-  * ``SHOW CLIENT_STATISTICS``
-  * ``SHOW INDEX_STATISTICS``
-  * ``SHOW TABLE_STATISTICS``
-  * ``SHOW THREAD_STATISTICS``
-  * ``SHOW USER_STATISTICS``
-
-These commands are another way to display the information you can get from the ``INFORMATION_SCHEMA`` tables. The commands accept ``WHERE`` clauses. They also accept but ignore ``LIKE`` clauses.
-
-Status Variables
-================
-
-.. _Com_show_client_statistics:
-
-.. rubric:: ``Com_show_client_statistics``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Scope
-     - Global/Session
-   * - Data type
-     - numeric
-
-The :ref:`Com_show_client_statistics` statement counter variable indicates the number of times the statement ``SHOW CLIENT_STATISTICS`` has been executed.
-
-.. _Com_show_index_statistics:
-
-.. rubric:: ``Com_show_index_statistics``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Scope
-     - Global/Session
-   * - Data type
-     - numeric
-
-The :ref:`Com_show_index_statistics` statement counter variable indicates the number of times the statement ``SHOW INDEX_STATISTICS`` has been executed.
-
-.. _Com_show_table_statistics:
-
-.. rubric:: ``Com_show_table_statistics``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Scope
-     - Global/Session
-   * - Data type
-     - numeric
-
-The :ref:`Com_show_table_statistics` statement counter variable indicates the number of times the statement ``SHOW TABLE_STATISTICS`` has been executed.
-
-.. _Com_show_thread_statistics:
-
-.. rubric:: ``Com_show_thread_statistics``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Scope
-     - Global/Session
-   * - Data type
-     - numeric
-
-The :ref:`Com_show_thread_statistics` statement counter variable indicates the number of times the statement ``SHOW THREAD_STATISTICS`` has been executed.
-
-.. _Com_show_user_statistics:
-
-.. rubric:: ``Com_show_user_statistics``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Scope
-     - Global/Session
-   * - Data type
-     - numeric
-
-The :ref:`Com_show_user_statistics` statement counter variable indicates the number of times the statement ``SHOW USER_STATISTICS`` has been executed.
diff --git a/doc/source/ext/psdom.py b/doc/source/ext/psdom.py
deleted file mode 100644
index e2e163fa8a8d..000000000000
--- a/doc/source/ext/psdom.py
+++ /dev/null
@@ -1,387 +0,0 @@
-# -*- coding: utf-8 -*-
-"""
-    The Percona Server domain.
-
-    :copyright: Copyright 2011 by Percona Inc.
-    :license: GPL3, see LICENSE for details.
-"""
-
-import re
-import string
-
-from docutils import nodes
-from docutils.parsers.rst import directives
-
-from sphinx import addnodes
-from sphinx.roles import XRefRole
-from sphinx.locale import l_, _
-from sphinx.domains import Domain, ObjType, Index
-from sphinx.directives import ObjectDescription
-from sphinx.util.nodes import make_refnode
-from sphinx.util.compat import Directive
-from sphinx.util.docfields import Field, GroupedField, TypedField
-
-
-# RE to split at word boundaries
-wsplit_re = re.compile(r'\W+')
-tern_re = re.compile(r'.*(\.|\:\:).*(\.).*')
-
-class PSschemaObject(ObjectDescription):
-    """
-    Description of a general PS object.
-    """
-    option_spec = {
-        'noindex': directives.flag,
-    }
-
-
-    def handle_signature(self, sig, signode):
-        """Transform a PSschema signature into RST nodes."""
-        # first try the function pointer signature regex, it's more specific
-
-        name = sig
-
-        signode += addnodes.desc_name('', '')
-
-        objectname = self.env.temp_data.get('psdom:object')
-        ot = self.objtype
-        ws = wsplit_re.split(sig)
-
-        if ot == 'db':
-            sig_prefix = "database "
-        else:
-            sig_prefix =  ot + " "
-
-        signode += addnodes.desc_annotation(sig_prefix, sig_prefix)
-
-        # for part in filter(None, ws):
-        #     tnode = nodes.Text(part, part)
-        #     pnode = addnodes.pending_xref(
-        #         '', refdomain='psdom', reftype='type', reftarget=part,
-        #         modname=None, classname=None)
-        #     pnode = tnode
-        #     signode += pnode
-        
-        if len(ws) > 2:
-            dbname, tablename, columnname = ws
-            name = columnname
-            fullname = tablename + "." + columnname
-        elif len(ws) == 2:
-            if ot == 'table':
-                dbname, tablename = ws
-                dbname += "."
-                name = tablename
-                signode['table'] = tablename
-                signode += addnodes.desc_addname(dbname, dbname)
-                signode += addnodes.desc_name(tablename, tablename)
-                # fullname = dbname + "." + tablename 
-                fullname = tablename
-            if ot == 'column':
-                tablename, columnname = ws
-                tablename += " "
-                signode += addnodes.desc_addname(tablename, tablename)
-                signode += addnodes.desc_name(columnname, columnname)
-                signode['table'] = tablename
-                fullname = tablename + "." + columnname
-        else:
-            if ot == 'table':
-                tablename = ws[0]
-                signode['table'] = tablename
-                dbname = self.options.get(
-                    'db', self.env.temp_data.get('psdom:db'))
-                dbname += "."
-                self.env.temp_data['psdom:table'] = tablename
-                signode += addnodes.desc_addname(dbname, dbname)
-                signode += addnodes.desc_name(tablename, tablename)
-                signode['table'] = tablename
-            if ot == 'column':
-                columnname = ws[0]
-                signode['column'] = columnname
-                tablename = self.options.get(
-                    'table', self.env.temp_data.get('psdom:table'))
-                tablename += "."
-                signode += addnodes.desc_addname(tablename, tablename)
-                signode += addnodes.desc_name(columnname, columnname)
-            if ot == 'db':
-                dbname = ws[0]
-                signode['db'] = dbname
-                name = dbname
-                self.env.temp_data['psdom:db'] = dbname
-                signode += addnodes.desc_name(dbname, dbname)
-            fullname = ws[0]
-
-        signode['fullname'] = fullname
-
-        return fullname
-
-    def get_index_text(self, name):
-        if self.objtype == 'db':
-            return _('%s (database)') % name
-        elif self.objtype == 'table':
-            return _('%s (table)') % name
-        elif self.objtype == 'column':
-            return _('%s (column)') % name
-        else:
-            return ''
-
-    def add_target_and_index(self, name, sig, signode):
-        # note target
-        if name not in self.state.document.ids:
-            signode['names'].append(name)
-            signode['ids'].append(name)
-            signode['first'] = (not self.names)
-            self.state.document.note_explicit_target(signode)
-            inv = self.env.domaindata['psdom']['objects']
-            if name in inv:
-                self.env.warn(
-                    self.env.docname,
-                    'duplicate PSschema object description of %s, ' % name +
-                    'other instance in ' + self.env.doc2path(inv[name][0]),
-                    self.lineno)
-            inv[name] = (self.env.docname, self.objtype)
-
-        indextext = self.get_index_text(name)
-        if indextext:
-            self.indexnode['entries'].append(('single', indextext, name, '', None))
-
-
-class PSconfigObject(ObjectDescription):
-    """
-    Description of a general PS Config object.
-    """
-    option_spec = {
-        'noindex': directives.flag,
-    }
-
-    def handle_signature(self, sig, signode):
-        """Transform a PSconfig signature into RST nodes."""
-        # first try the function pointer signature regex, it's more specific
-
-        name = sig
-        ot = self.objtype
-
-        sig_prefix =  ot + " "
-        signode += addnodes.desc_annotation(sig_prefix, sig_prefix)
-
-        signode += addnodes.desc_name(name, name)
-        signode['fullname'] = name
-
-        return name
-
-    def get_index_text(self, name):
-        if self.objtype == 'option':
-            return _('%s (option)') % name
-        elif self.objtype == 'variable':
-            return _('%s (variable)') % name
-        else:
-            return ''
-
-    def add_target_and_index(self, name, sig, signode):
-        # note target
-        if name not in self.state.document.ids:
-            signode['names'].append(name)
-            signode['ids'].append(name)
-            signode['first'] = (not self.names)
-            self.state.document.note_explicit_target(signode)
-            inv = self.env.domaindata['psdom']['objects']
-            if name in inv:
-                self.env.warn(
-                    self.env.docname,
-                    'duplicate PSconfig object description of %s, ' % name +
-                    'other instance in ' + self.env.doc2path(inv[name][0]),
-                    self.lineno)
-            inv[name] = (self.env.docname, self.objtype)
-
-        indextext = self.get_index_text(name)
-        if indextext:
-            self.indexnode['entries'].append(('single', indextext, name, '', None))
-
-
-class PSTable(PSschemaObject):
-
-    doc_field_types = [
-        TypedField('column', label=l_('Columns'), rolename='obj',
-                   names=('col', 'column', 'cols'),
-                   typerolename='obj', typenames=('paramtype', 'type')),
-        Field('inpatch', label=l_('Included in Patch'), has_arg=False,
-              names=('inpatch')),
-        TypedField('versioninfo', label=l_('Version Info'), rolename='obj',
-                   names=('version', 'versioninfo'),
-                   typerolename='obj', typenames=('paramtype', 'type')),
-    ]
-
-class PSDatabase(PSschemaObject):
-
-    doc_field_types = [
-        TypedField('tbl', label=l_('Tables'),
-                   names=('tbl', 'table',),
-                   typerolename='obj', typenames=('paramtype', 'type')),
-        Field('engine', label=l_('Storage Engine'), has_arg=False,
-              names=('engine')),
-        Field('inpatch', label=l_('Included in Patch'), has_arg=False,
-              names=('inpatch')),
-    ]
-
-class PSColumn(PSschemaObject):
-
-    doc_field_types = [
-        TypedField('coltype', label=l_('Type'), rolename='obj',
-                   names=('coltype', 'type'),
-                   typerolename='obj', typenames=('paramtype', 'type')),
-        Field('inpatch', label=l_('Included in Patch'), has_arg=False,
-              names=('inpatch')),
-    ]
-
-class PSVariable(PSconfigObject):
-
-    doc_field_types = [
-        Field('scope', label=l_('Scope'), has_arg=False,
-              names=('scope', 'varscope')),
-        Field('cmdline', label=l_('Command Line'), has_arg=False,
-              names=('cmdline', 'cline', 'cli')),
-        Field('configfile', label=l_('Config File'), has_arg=False,
-              names=('conffile', 'configfile', 'conf', 'cfile')),
-        Field('dynamic', label=l_('Dynamic'), has_arg=False,
-              names=('dynvar', 'dyn')),
-        Field('vartype', label=l_('Variable Type'), has_arg=False,
-              names=('vartype', 'vtype')),
-        Field('default', label=l_('Default Value'), has_arg=False,
-              names=('default', 'df')),
-        Field('range', label=l_('Range'), has_arg=False,
-              names=('range', 'range')),
-        Field('allowed', label=l_('Allowed Values'), has_arg=False,
-              names=('allowed', 'av')),
-        Field('unit', label=l_('Units'), has_arg=False,
-              names=('unit', 'un')),
-        Field('inpatch', label=l_('Included in Patch'), has_arg=False,
-              names=('inpatch')),
-        TypedField('versioninfo', label=l_('Version Info'), rolename='obj',
-                   names=('version', 'versioninfo'),
-                   typerolename='obj', typenames=('paramtype', 'type')),
-    ]
-
-class PSOption(PSconfigObject):
-    pass
-
-class PSReleaseNotes(Directive):
-    """
-    Directive to mark description of Release Notes.
-    """
-
-    has_content = False
-    required_arguments = 1
-    optional_arguments = 0
-    final_argument_whitespace = False
-    option_spec = {
-        'platform': lambda x: x,
-        'noindex': directives.flag,
-    }
-
-    def run(self):
-        env = self.state.document.settings.env
-        rnname = self.arguments[0].strip()
-        noindex = 'noindex' in self.options
-        env.temp_data['psdome:rn'] = rnname
-        ret = []
-        if not noindex:
-            env.domaindata['psdom']['objects'][rnname] = \
-                (env.docname, self.options.get('platform', ''))
-            # make a duplicate entry in 'objects' to facilitate searching for the
-            # module in PythonDomain.find_obj()
-            env.domaindata['psdom']['objects'][rnname] = (env.docname, 'rn')
-            targetnode = nodes.target('', '', ids=['release-' + rnname])
-            self.state.document.note_explicit_target(targetnode)
-            # the platform and synopsis aren't printed; in fact, they are only used
-            # in the modindex currently
-            ret.append(targetnode)
-            indextext = _('%s (release notes)') % rnname
-            inode = addnodes.index(entries=[('single', indextext,
-                                             'module-' + rnname, '', None)])
-            ret.append(inode)
-        return ret
-
-class PSXRefRole(XRefRole):
-    def process_link(self, env, refnode, has_explicit_title, title, target):
-        if not has_explicit_title:
-            target = target.lstrip('~') # only has a meaning for the title
-            # if the first character is a tilde, don't display the module/class
-            # parts of the contents
-            if title[0:1] == '~':
-                title = title[1:]
-                dot = title.rfind('.')
-                if dot != -1:
-                    title = title[dot+1:]
-        return title, target
-
-
-class PerconaServerDomain(Domain):
-    """Percona Server domain."""
-    name = 'psdom'
-    label = 'Percona Server'
-    object_types = {
-        'db':        ObjType(l_('db'),       'db'),
-        'table':     ObjType(l_('table'),    'table'),
-        'column':    ObjType(l_('column'),   'column'),
-        'option':    ObjType(l_('option'),   'option'),
-        'variable':  ObjType(l_('variable'), 'data'),
-    }
-
-    directives = {
-        'db':       PSDatabase,
-        'table':    PSTable,
-        'column':   PSColumn,
-        'option':   PSVariable,
-        'variable': PSVariable,
-        'rn':       PSReleaseNotes
-    }
-    roles = {
-        'db' :      PSXRefRole(),
-        'table':    PSXRefRole(),
-        'column':   PSXRefRole(),
-        'option':   PSXRefRole(),
-        'variable': PSXRefRole(),
-        'rn': PSXRefRole(),
-    }
-    initial_data = {
-        'objects': {},  # fullname -> docname, objtype
-    }
-
-    def clear_doc(self, docname):
-        for fullname, (fn, _) in self.data['objects'].iteritems():
-            if fn == docname:
-                del self.data['objects'][fullname]
-
-    def resolve_xref(self, env, fromdocname, builder,
-                     typ, target, node, contnode):
-        # strip pointer asterisk
-        target = target.rstrip(' *')
-        if target not in self.data['objects']:
-            return None
-        obj = self.data['objects'][target]
-        return make_refnode(builder, fromdocname, obj[0], target,
-                            contnode, target)
-
-    def get_objects(self):
-        for refname, (docname, type) in self.data['objects'].items():
-            yield (refname, refname, type, docname, refname, 1)
-
-    def find_obj(self, env, obj, name, typ, searchorder=0):
-        if name[-2:] == '()':
-            name = name[:-2]
-        objects = self.data['objects']
-        newname = None
-        if searchorder == 1:
-            if obj and obj + '.' + name in objects:
-                newname = obj + '.' + name
-            else:
-                newname = name
-        else:
-            if name in objects:
-                newname = name
-            elif obj and obj + '.' + name in objects:
-                newname = obj + '.' + name
-        return newname, objects.get(newname)
-
-def setup(app):
-    app.add_config_value('databases', {}, 'env')
-    app.add_domain(PerconaServerDomain)
diff --git a/doc/source/faq.rst b/doc/source/faq.rst
deleted file mode 100644
index 8c68934a67d6..000000000000
--- a/doc/source/faq.rst
+++ /dev/null
@@ -1,41 +0,0 @@
-.. _faq:
-
-==========================
-Frequently Asked Questions
-==========================
-
-Q: Will |Percona Server| with |XtraDB| invalidate our |MySQL| support?
-======================================================================
-
-A: We don't know the details of your support contract. You should check with
-your *Oracle* representative. We have heard anecdotal stories from |MySQL|
-Support team members that they have customers who use |Percona Server| with
-|XtraDB|, but you should not base your decision on that.
-
-Q: Will we have to *GPL* our whole application if we use |Percona Server| with |XtraDB|?
-========================================================================================
-
-A: This is a common misconception about the *GPL*. We suggest reading the *Free
-Software Foundation* 's excellent reference material on the `GPL Version 2
-<http://www.gnu.org/licenses/old-licenses/gpl-2.0.html>`_, which is the license
-that applies to |MySQL| and therefore to |Percona Server| with |XtraDB|. That
-document contains links to many other documents which should answer your
-questions. |Percona| is unable to give legal advice about the *GPL*.
-
-Q: Do I need to install |Percona| client libraries?
-===================================================
-
-A: No, you don't need to change anything on the clients. |Percona Server| is
-100% compatible with all existing client libraries and connectors.
-
-Q: When using the |Percona XtraBackup| to setup a replication replica on Debian based systems I'm getting: "ERROR 1045 (28000): Access denied for user 'debian-sys-maint'@'localhost' (using password: YES)"
-
-A: In case you're using init script on |debian| based system to start ``mysqld``,
-be sure that the password for ``debian-sys-maint`` user has been updated and
-it's the same as that user's password from the server that the backup has been
-taken from. The password can be seen and updated in
-:file:`/etc/mysql/debian.cnf`. For more information on how to set up a
-replication replica using |Percona XtraBackup| see `this how-to
-<http://www.percona.com/doc/percona-xtrabackup/2.1/howtos/setting_up_replication.html>`_.
-
-.. include:: .res/replace.txt
diff --git a/doc/source/feature_comparison.rst b/doc/source/feature_comparison.rst
deleted file mode 100644
index 156a979f2420..000000000000
--- a/doc/source/feature_comparison.rst
+++ /dev/null
@@ -1,199 +0,0 @@
-=====================================
- |Percona Server| Feature Comparison
-=====================================
-
-|Percona Server| is a free, fully compatible, enhanced, and open source drop-in replacement for any MySQL database. It provides superior performance, scalability, and instrumentation.
-
-|Percona Server| is trusted by thousands of enterprises to provide better performance and concurrency for their most demanding workloads. It delivers higher value to MySQL server users with optimized performance, greater performance scalability and availability, enhanced backups, and increased visibility.
-
-We provide these benefits by significantly enhancing |Percona Server| as
-compared to the standard |MySQL| database server:
-
-+---------------------------------------+-------------------------+--------------+
-|Features                               | |Percona Server| 8.0.13 |MySQL 8.0.13  |
-+=======================================+=========================+==============+
-|Open source                            | Yes                     | Yes          |      
-+---------------------------------------+-------------------------+--------------+
-|ACID Compliance                        | Yes                     | Yes          |                     
-+---------------------------------------+-------------------------+--------------+
-|Multi-Version Concurrency Control      | Yes                     | Yes          |                      
-+---------------------------------------+-------------------------+--------------+
-|Row-Level Locking                      | Yes                     | Yes          |
-+---------------------------------------+-------------------------+--------------+
-|Automatic Crash Recovery               | Yes                     | Yes          |
-+---------------------------------------+-------------------------+--------------+
-|Table Partitioning                     | Yes                     | Yes          |
-+---------------------------------------+-------------------------+--------------+
-|Views                                  | Yes                     | Yes          |
-+---------------------------------------+-------------------------+--------------+
-|Subqueries                             | Yes                     | Yes          |
-+---------------------------------------+-------------------------+--------------+
-|Triggers                               | Yes                     | Yes          |
-+---------------------------------------+-------------------------+--------------+
-|Stored Procedures                      | Yes                     | Yes          |
-+---------------------------------------+-------------------------+--------------+
-|Foreign Keys                           | Yes                     | Yes          |
-+---------------------------------------+-------------------------+--------------+
-|Window Functions                       | Yes                     | Yes          |
-+---------------------------------------+-------------------------+--------------+
-|Common Table Expressions               | Yes                     | Yes          |
-+---------------------------------------+-------------------------+--------------+
-|Geospatial Features (GIS, SPRS)        | Yes                     | Yes          |
-+---------------------------------------+-------------------------+--------------+
-|GTID Replication                       | Yes                     | Yes          |
-+---------------------------------------+-------------------------+--------------+
-|Group Replication                      | Yes                     | Yes          |
-+---------------------------------------+-------------------------+--------------+
-|MyRocks Storage Engine                 | Yes                     | No           |
-+---------------------------------------+-------------------------+--------------+
-|TokuDB Storage Engine                  | Yes                     | No           |
-+---------------------------------------+-------------------------+--------------+
-
-Improvements for Developers
-================================================================================
-
-+---------------------------------------+-------------------------+--------------+
-|Feature                                | |Percona Server| 8.0.13 |MySQL 8.0.13  |
-+=======================================+=========================+==============+
-|NoSQL Socket-Level Interface           | Yes                     | Yes          |
-+---------------------------------------+-------------------------+--------------+
-|X API Support                          | Yes                     | Yes          |
-+---------------------------------------+-------------------------+--------------+
-|JSON Functions                         | Yes                     | Yes          |
-+---------------------------------------+-------------------------+--------------+
-|InnoDB Full-Text Search Improvements   | Yes                     | No           |
-+---------------------------------------+-------------------------+--------------+
-|Extra Hash/Digest Functions            | Yes                     | No           |
-+---------------------------------------+-------------------------+--------------+
-
-Extra Diagnostic Features
-================================================================================
-
-+---------------------------------------+------------------------+--------------+
-|Feature                                ||Percona Server| 8.0.13 |MySQL 8.0.13  |
-+=======================================+========================+==============+
-|INFORMATION_SCHEMA Tables              | 95                     | 65           |
-+---------------------------------------+------------------------+--------------+
-|Global Performance and Status Counters | 853                    | 434          |
-+---------------------------------------+------------------------+--------------+
-|Optimizer Histograms                   | Yes                    | Yes          |
-+---------------------------------------+------------------------+--------------+
-|Per-Table Performance Counters         | Yes                    | No           |
-+---------------------------------------+------------------------+--------------+
-|Per-Index Performance Counters         | Yes                    | No           |
-+---------------------------------------+------------------------+--------------+
-|Per-User Performance Counters          | Yes                    | No           |
-+---------------------------------------+------------------------+--------------+
-|Per-Client Performance Counters        | Yes                    | No           |
-+---------------------------------------+------------------------+--------------+
-|Per-Thread Performance Counters        | Yes                    | No           |
-+---------------------------------------+------------------------+--------------+
-|Enhanced SHOW ENGINE INNODB STATUS     | Yes                    | No           |
-+---------------------------------------+------------------------+--------------+
-|Temporary tables Information           | Yes                    | No           |
-+---------------------------------------+------------------------+--------------+
-|Extended Slow Query Logging            | Yes                    | No           |
-+---------------------------------------+------------------------+--------------+
-|User Statistics                        | Yes                    | No           |
-+---------------------------------------+------------------------+--------------+
-
-Performance & Scalability Enhancements
-================================================================================
-
-+--------------------------------------------------+------------------------+--------------+
-| Feature                                          ||Percona Server| 8.0.13 |MySQL 8.0.13  |
-+==================================================+========================+==============+
-|InnoDB Resource Groups                            | Yes                    | Yes          |
-+--------------------------------------------------+------------------------+--------------+
-|Configurable Page Sizes                           | Yes                    | Yes          |
-+--------------------------------------------------+------------------------+--------------+
-|Contention-Aware Transaction Scheduling           | Yes                    | Yes          |
-+--------------------------------------------------+------------------------+--------------+
-|Improved Scalability by Splitting Mutexes         | Yes                    | Yes          |
-+--------------------------------------------------+------------------------+--------------+
-|Improved MEMORY Storage Engine                    | Yes                    | No           |
-+--------------------------------------------------+------------------------+--------------+
-|Improved Flushing                                 | Yes                    | No           |
-+--------------------------------------------------+------------------------+--------------+
-|Parallel Doublewrite Buffer                       | Yes                    | No           |
-+--------------------------------------------------+------------------------+--------------+
-|Configurable Fast Index Creation                  | Yes                    | No           |
-+--------------------------------------------------+------------------------+--------------+
-|Per-Column Compression for VARCHAR/BLOB and JSON  | Yes                    | No           |
-+--------------------------------------------------+------------------------+--------------+
-|Compressed Columns with Dictionaries              | Yes                    | No           |
-+--------------------------------------------------+------------------------+--------------+
-
-Security Features
-================================================================================
-
-+--------------------------------------+------------------------+----------------+
-| Feature                              ||Percona Server| 8.0.13 |MySQL 8.0.13    |
-+======================================+========================+================+
-|SQL Roles                             | Yes                    | Yes            |
-+--------------------------------------+------------------------+----------------+
-|SHA-2 Based Password Hashing          | Yes                    | Yes            |
-+--------------------------------------+------------------------+----------------+
-|Password Rotation Policy              | Yes                    | Yes            |
-+--------------------------------------+------------------------+----------------+
-|PAM Authentication                    | Yes                    | Enterprise Only|
-+--------------------------------------+------------------------+----------------+
-|Audit Logging Plugin                  | Yes                    | Enterprise Only|
-+--------------------------------------+------------------------+----------------+
-
-Encryption Features
-================================================================================
-
-+------------------------------------------------------------------+------------------------+----------------+
-| Feature                                                          ||Percona Server| 8.0.13 |MySQL 8.0.13    |
-+==================================================================+========================+================+
-|Storing Keyring in a File                                         | Yes                    | Yes            |
-+------------------------------------------------------------------+------------------------+----------------+
-|Storing Keyring in Hashicorp Vault                                | Yes                    | No             |
-+------------------------------------------------------------------+------------------------+----------------+
-|Encrypt InnoDB Data                                               | Yes                    | Yes            |
-+------------------------------------------------------------------+------------------------+----------------+
-|Encrypt InnoDB Logs                                               | Yes                    | Yes            |
-+------------------------------------------------------------------+------------------------+----------------+
-|Encrypt Built-in InnoDB Tablespaces (General, System, Undo, Temp) | Yes                    | No             |
-+------------------------------------------------------------------+------------------------+----------------+
-|Encrypt Binary Logs                                               | Yes                    | No             |
-+------------------------------------------------------------------+------------------------+----------------+
-|Encrypt Temporary Files                                           | Yes                    | No             |
-+------------------------------------------------------------------+------------------------+----------------+
-|Key Rotation with Scrubbing                                       | Yes                    | No             |
-+------------------------------------------------------------------+------------------------+----------------+
-|Enforce Encryption                                                | Yes                    | No             |
-+------------------------------------------------------------------+------------------------+----------------+
-
-Operational Improvements
-================================================================================
-
-+------------------------------------------------------------------+------------------------+----------------+
-| Feature                                                          ||Percona Server| 8.0.13 |MySQL 8.0.13    |
-+==================================================================+========================+================+
-|Atomic DDL                                                        | Yes                    | Yes            |
-+------------------------------------------------------------------+------------------------+----------------+
-|Transactional Data Dictionary                                     | Yes                    | Yes            |
-+------------------------------------------------------------------+------------------------+----------------+
-|Instant DDL                                                       | Yes                    | Yes            |
-+------------------------------------------------------------------+------------------------+----------------+
-|SET PERSIST                                                       | Yes                    | Yes            |
-+------------------------------------------------------------------+------------------------+----------------+
-|Invisible Indexes                                                 | Yes                    | Yes            |
-+------------------------------------------------------------------+------------------------+----------------+
-|Changed Page Tracking                                             | Yes                    | No             |
-+------------------------------------------------------------------+------------------------+----------------+
-|Threadpool                                                        | Yes                    | Enterprise Only|
-+------------------------------------------------------------------+------------------------+----------------+
-|Backup Locks                                                      | Yes                    | Yes            |
-+------------------------------------------------------------------+------------------------+----------------+
-|Extended SHOW GRANTS                                              | Yes                    | No             |
-+------------------------------------------------------------------+------------------------+----------------+
-|Improved Handling of Corrupted Tables                             | Yes                    | No             |
-+------------------------------------------------------------------+------------------------+----------------+
-|Ability to Kill Idle Transactions                                 | Yes                    | No             |
-+------------------------------------------------------------------+------------------------+----------------+
-|Improvements to START TRANSACTION WITH CONSISTENT SNAPSHOT        | Yes                    | No             |
-+------------------------------------------------------------------+------------------------+----------------+
-
diff --git a/doc/source/flexibility/binlog_space.rst b/doc/source/flexibility/binlog_space.rst
deleted file mode 100644
index 6f044af160e9..000000000000
--- a/doc/source/flexibility/binlog_space.rst
+++ /dev/null
@@ -1,52 +0,0 @@
-.. _binlog_space:
-
-============================================================
-Limiting the disk space used by binary log files
-============================================================
-
-.. contents::
-   :local:
-
-It is a challenge to control how much disk space is used by the binary logs. The size of a binary log can vary because a single transaction must be written to a single binary log and cannot be split between multiple binary log files.
-
-.. _binlog_space_limit:
-
-binlog_space_limit(=x) definition
--------------------------------------------
-
-.. list-table::
-   :header-rows: 1
-
-   * - Attribute
-     - Description
-   * - Uses the command line 
-     - Yes
-   * - Uses the configuration file
-     - Yes
-   * - Scope
-     - Global
-   * - Dynamic
-     - No
-   * - Variable type
-     - ULONG_MAX
-   * - Default value
-     - 0 (unlimited)
-   * - Maximum value - 64-bit platform
-     - 18446744073709547520
-
-
-This variable places an upper limit on the total size in bytes of all binary logs. When the limit is reached, the oldest binary logs are purged until the total size is under the limit or only the active log remains.
-
-The default value of ``0`` disables the feature. No limit is set on the log space. The binary logs accumulate indefinitely until the disk space is full. 
-
-Example
------------
-
-Set the `binlog_space_limit` to 30000 in the ``my.cnf`` file: ::
-
-    [mysqld]
-    bin = 15G
-
-.. seealso:: For more information, see the `Percona Blog - Percona Server for MySQL Highlights - binlog_space_limit <https://www.percona.com/blog/2019/07/03/percona-server-for-mysql-highlights-binlog_space_limit/>`__.
-     
-
diff --git a/doc/source/flexibility/binlogging_replication_improvements.rst b/doc/source/flexibility/binlogging_replication_improvements.rst
deleted file mode 100644
index 8d024260a97e..000000000000
--- a/doc/source/flexibility/binlogging_replication_improvements.rst
+++ /dev/null
@@ -1,337 +0,0 @@
-.. _binlogging_replication_improvements:
-
-=======================================
-Binlogging and replication improvements
-=======================================
-
-Due to continuous development, *Percona Server for MySQL* incorporated a number of
-improvements related to replication and binary logs handling. This resulted in replication specifics, which distinguishes it from *MySQL*.
-
-Safety of statements with a ``LIMIT`` clause
-============================================
-
-Summary of the Fix
-*******************
-
-*MySQL* considers all ``UPDATE/DELETE/INSERT ... SELECT`` statements with
-``LIMIT`` clause to be unsafe, no matter wether they are really producing
-non-deterministic result or not, and switches from statement-based logging
-to row-based one. *Percona Server for MySQL* is more accurate, it acknowledges such
-instructions as safe when they include ``ORDER BY PK`` or ``WHERE``
-condition. This fix has been ported from the upstream bug report
-:mysqlbug:`42415` (:psbug:`44`).
-
-Performance improvement on relay log position update
-====================================================
-
-Summary of the Fix
-*******************
-
-*MySQL* always updated relay log position in multi-source replications setups
-regardless of whether the committed transaction has already been executed or
-not. Percona Server omits relay log position updates for the already logged
-GTIDs.
-
-Details
-*******
-
-Particularly, such unconditional relay log position updates caused additional
-fsync operations in case of ``relay-log-info-repository=TABLE``, and with the
-higher number of channels transmitting such duplicate (already executed)
-transactions the situation became proportionally worse. Bug fixed :psbug:`1786`
-(upstream :mysqlbug:`85141`).
-
-Performance improvement on source and connection status updates
-===============================================================
-
-Summary of the Fix
-*******************
-
-Replica nodes configured to update source status and connection information
-only on log file rotation did not experience the expected reduction in load.
-*MySQL* was additionally updating this information in case of multi-source
-replication when replica had to skip the already executed GTID event.
-
-Details
-*******
-
-The configuration with ``master_info_repository=TABLE`` and
-``sync_master_info=0`` makes replica to update source status and connection
-information in this table on log file rotation and not after each
-sync_master_info event, but it didn't work on multi-source replication setups.
-Heartbeats sent to the replica to skip GTID events which it had already executed
-previously, were evaluated as relay log rotation events and reacted with
-``mysql.slave_master_info`` table sync. This inaccuracy could produce huge (up
-to 5 times on some setups) increase in write load on the replica, before this
-problem was fixed in *Percona Server for MySQL*. Bug fixed :psbug:`1812` (upstream
-:mysqlbug:`85158`).
-
-.. _percona-server.binary-log.flush.writing:
-
-Writing ``FLUSH`` Commands to the Binary Log
-================================================================================
-
-``FLUSH`` commands, such as ``FLUSH SLOW LOGS``, are not written to the
-binary log if the system variable :ref:`binlog_skip_flush_commands` is set
-to **ON**.
-
-In addition, the following changes were implemented in the behavior of
-``read_only`` and `super_read_only` modes:
-
-- When ``read_only`` is set to **ON**, any ``FLUSH ...`` command executed by a
-  normal user (without the ``SUPER`` privilege) are not written to the binary
-  log regardless of the value of the :ref:`binlog_skip_flush_command` variable.
-- When `super_read_only` is set to **ON**, any ``FLUSH ...`` command executed by
-  any user (even by those with the ``SUPER`` privilege) are not written to the
-  binary log regardless of the value of the :ref:`binlog_skip_flush_commands` variable.
-
-An attempt to run a ``FLUSH`` command without either ``SUPER`` or ``RELOAD``
-privileges results in the ``ER_SPECIFIC_ACCESS_DENIED_ERROR`` exception
-regardless of the value of the :ref:`binlog_skip_flush_commands` variable.
-
-.. _binlog_skip_flush_commands:
-
-.. rubric:: ``binlog_skip_flush_commands``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - Yes
-   * - Config file
-     - Yes
-   * - Scope
-     - Global
-   * - Dynamic
-     - Yes
-   * - Default
-     - OFF
-
-This variable was introduced in :ref:`8.0.15-5`.
-
-When :ref:`binlog_skip_flush_commands` is set to **ON**, ``FLUSH ...`` commands are not written to the binary
-log. See :ref:`percona-server.binary-log.flush.writing` for more information
-about what else affects the writing of ``FLUSH`` commands to the binary log.
-
-.. note::
-
-   ``FLUSH LOGS``, ``FLUSH BINARY LOGS``, ``FLUSH TABLES WITH READ LOCK``, and
-   ``FLUSH TABLES ... FOR EXPORT`` are not written to the binary log no matter
-   what value the :ref:`binlog_skip_flush_commands` variable contains. The ``FLUSH`` command is not
-   recorded to the binary log and the value of :ref:`binlog_skip_flush_commands` is ignored if the ``FLUSH`` command is run with the ``NO_WRITE_TO_BINLOG`` keyword (or its
-   alias ``LOCAL``).
-
-   .. seealso::
-
-      *MySQL* Documentation: FLUSH Syntax
-         https://dev.mysql.com/doc/refman/8.0/en/flush.html
-
-.. _ps.binlog_ddl_skip_rewrite:
-
-Maintaining Comments with DROP TABLE
-=====================================
-
-When you issue a ``DROP TABLE`` command, the binary log stores the command but removes comments and encloses the table name in quotation marks. If you require the binary log to maintain the comments and not add quotation marks, enable ``binlog_ddl_skip_rewrite``.
-
-.. _binlog_ddl_skip_rewrite:
-
-.. rubric:: ``binlog_ddl_skip_rewrite``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - Yes
-   * - Config file
-     - Yes
-   * - Scope
-     - Global
-   * - Dynamic
-     - Yes
-   * - Default
-     - OFF
-
-This variable was introduced in :ref:`8.0.26-16`.
-
-If the variable is enabled, single table ``DROP TABLE`` DDL statements are logged in the binary log with comments. Multi-table ``DROP TABLE`` DDL statements are not supported and return an error.
-
-.. sourcecode:: sql 
-
-  SET binlog_ddl_skip_rewrite = ON;
-  /*comment at start*/DROP TABLE t /*comment at end*/;
-
-.. _percona-server.binary-log.UDF:
-
-Binary Log User Defined Functions
-================================================================================
-
-To implement Point in Time recovery, we have added the ``binlog_utils_udf``. The following user-defined functions are included:
-
-.. list-table::
-   :widths: 20 20 50
-   :header-rows: 1
-
-   * - Name
-     - Returns
-     - Description
-   * - get_binlog_by_gtid()
-     - Binlog file name as STRING
-     - Returns the binlog file name that contains the specified GTID
-   * - get_last_gtid_from_binlog()
-     - GTID as STRING
-     - Returns the last GTID found in the specified binlog
-   * - get_gtid_set_by_binlog()
-     - GTID set as STRING
-     - Returns all GTIDs found in the specified binlog
-   * - get_binlog_by_gtid_set()
-     - Binlog file name as STRING
-     - Returns the file name of the binlog which contains at least one GTID from the specified set. 
-   * - get_first_record_timestamp_by_binlog()
-     - Timestamp as INTEGER
-     - Returns the timestamp of the first event in the specified binlog
-   * - get_last_record_timestamp_by_binlog()
-     - Timestamp as INTEGER
-     - Returns the timestamp of the last event in the specified binlog
-
-.. note::
-
-    All functions returning timestamps return their values as microsecond precision UNIX time. In other words, they represent the number of microseconds since 1-JAN-1970.
-
-    All functions accepting a binlog name as the parameter accepts only short names, without a path component. If the path separator ('/') is found in the input, an error is returned. This serves the purpose of restricting the locations from where binlogs can be read. They are always read from the current binlog directory (`@@log_bin_basename system variable <https://dev.mysql.com/doc/refman/8.0/en/replication-options-binary-log.html#sysvar_log_bin_basename>`_).
-
-    All functions returning binlog file names return the name in short form, without a path component.
-
-The basic syntax for ``get_binlog_by_gtid()`` is the following:
-
-* get_binlog_by_gtid(string) [AS] alias
-
-  Usage: SELECT get_binlog_by_gtid(string) [AS] alias
-
-  Example:
-
-  .. code-block:: mysql
-
-      CREATE FUNCTION get_binlog_by_gtid RETURNS STRING SONAME 'binlog_utils_udf.so';
-      SELECT get_binlog_by_gtid("F6F54186-8495-47B3-8D9F-011DDB1B65B3:1") AS result;
-      +--------------+
-      | result       |
-      +==============+
-      | binlog.00001 |
-      +--------------+
-
-      DROP FUNCTION get_binlog_by_gtid;
-
-The basic syntax for ``get_last_gtid_from_binlog()`` is the following:
-
-* get_last_gtid_from_binlog(string) [AS] alias
-
-  Usage: SELECT get_last_gtid_from_binlog(string) [AS] alias
-
-  Example:
-
-  .. code-block:: mysql
-
-      CREATE FUNCTION get_last_gtid_from_binlog RETURNS STRING SONAME 'binlog_utils_udf.so';
-      SELECT get_last_gtid_from_binlog("binlog.00001") AS result;
-      +-----------------------------------------+
-      | result                                  |
-      +=========================================+
-      | F6F54186-8495-47B3-8D9F-011DDB1B65B3:10 |
-      +-----------------------------------------+
-
-      DROP FUNCTION get_last_gtid_from_binlog;
-
-The basic syntax for ``get_gtid_set_by_binlog()`` is the following:
-
-* get_gtid_set_by_binlog(string) [AS] alias
-
-  Usage: SELECT get_gtid_set_by_binlog(string) [AS] alias
-
-  Example:
-
-  .. code-block:: mysql
-
-      CREATE FUNCTION get_gtid_set_by_binlog RETURNS STRING SONAME 'binlog_utils_udf.so';
-      SELECT get_gtid_set_by_binlog("binlog.00001") AS result;
-      +-------------------------+
-      | result                  |
-      +=========================+
-      | 11ea-b9a7:7,11ea-b9a7:8 |
-      +-------------------------+
-
-      DROP FUNCTION get_gtid_set_by_binlog;
-
-The basic syntax for ``get_binlog_by_gtid_set()`` is the following:
-
-* get_binlog_by_gtid_set(string) [AS] alias
-
-  Usage: SELECT get_binlog_by_gtid_set(string) [AS] alias
-
-  Example:
-
-  .. code-block:: mysql
-
-      CREATE FUNCTION get_binlog_by_gtid_set RETURNS STRING SONAME 'binlog_utils_udf.so';
-      SELECT get_binlog_by_gtid_set("11ea-b9a7:7,11ea-b9a7:8") AS result;
-      +---------------------------------------------------------------+
-      | result                                                        |
-      +===============================================================+
-      | bin.000003                                                    |
-      +---------------------------------------------------------------+
-
-      DROP FUNCTION get_binlog_by_gtid_set;
-
-The basic syntax for ``get_first_record_timestamp_by_binlog()`` is the following:
-
-* get_first_record_timestamp_by_binlog(TIMESTAMP) [AS] alias
-
-  Usage: SELECT get_first_record_timestamp_by_binlog(TIMESTAMP) [AS] alias
-
-  Example:
-
-  .. code-block:: mysql
-
-      CREATE FUNCTION get_first_record_timestamp_by_binlog RETURNS STRING SONAME 'binlog_utils_udf.so';
-      SELECT FROM_UNIXTIME(get_first_record_timestamp_by_binlog("bin.00003") DIV 1000000) AS result;
-      +---------------------+
-      | result              |
-      +=====================+
-      | 2020-12-03 09:10:40 |
-      +---------------------+
-
-      DROP FUNCTION get_first_record_timestamp_by_binlog;
-
-The basic syntax for ``get_last_record_timestamp_by_binlog()`` is the following:
-
-* get_last_record_timestamp_by_binlog(TIMESTAMP) [AS] alias
-
-  Usage: SELECT get_last_record_timestamp_by_binlog(TIMESTAMP) [AS] alias
-
-  Example:
-
-  .. code-block:: mysql
-
-      CREATE FUNCTION get_last_record_timestamp_by_binlog RETURNS STRING SONAME 'binlog_utils_udf.so';
-      SELECT FROM_UNIXTIME(get_last_record_timestamp_by_binlog("bin.00003") DIV 1000000) AS result;
-      +---------------------+
-      | result              |
-      +=====================+
-      | 2020-12-04 04:18:56 |
-      +---------------------+
-
-      DROP FUNCTION get_last_record_timestamp_by_binlog;
-
-Limitations
-====================
-
-Do not use one or more dot characters (.) when defining the values for the following variables:
-
-* `log_bin <https://dev.mysql.com/doc/refman/8.0/en/replication-options-binary-log.html#option_mysqld_log-bin>`__  
-
-* `log_bin_index <https://dev.mysql.com/doc/refman/8.0/en/replication-options-binary-log.html#option_mysqld_log-bin-index>`__ 
-
-MySQL and **XtraBackup** handle the value in different ways and this difference causes unpredictable behavior.
\ No newline at end of file
diff --git a/doc/source/flexibility/compressed_columns.rst b/doc/source/flexibility/compressed_columns.rst
deleted file mode 100644
index 71f3e2038aaa..000000000000
--- a/doc/source/flexibility/compressed_columns.rst
+++ /dev/null
@@ -1,365 +0,0 @@
-.. _compressed_columns:
-
-================================================================================
-Compressed columns with dictionaries
-================================================================================
-
-The ``per-column compression`` feature is a data type modifier, independent from
-user-level SQL and *InnoDB* data compression, that causes the data stored in the
-column to be compressed on writing to storage and decompressed on reading. For
-all other purposes, the data type is identical to the one without the modifier,
-i.e. no new data types are created. Compression is done by using the ``zlib``
-library.
-
-Additionally, it is possible to pre-define a set of strings for each compressed
-column to achieve a better compression ratio on relatively small individual
-data items.
-
-This feature provides:
-
-* a better compression ratio for text data which consist of a large number of
-  predefined words (e.g. JSON or XML) using compression methods with static
-  dictionaries
-* a way to select columns in the table to compress (in contrast to the *InnoDB*
-  row compression method)
-
-.. To Reviewer: Is the following statement still relevant?
-
-This feature is based on a patch provided by Weixiang Zhai.
-
-Specifications
-==============
-
-The feature is limited to InnoDB/XtraDB storage engine and to columns of the
-following data types:
-
-- ``BLOB`` (including ``TINYBLOB``, ``MEDIUMBLOB``, ``LONGBLOG``)
-- ``TEXT`` (including ``TINYTEXT``, ``MEDUUMTEXT``, ``LONGTEXT``)
-- ``VARCHAR`` (including ``NATIONAL VARCHAR``)
-- ``VARBINARY``
-- ``JSON``
-
-A compressed column is declared by using the syntax that extends the existing
-``COLUMN_FORMAT`` modifier: ``COLUMN_FORMAT COMPRESSED``. If this modifier is
-applied to an unsupported column type or storage engine, an error is returned.
-
-The compression can be specified:
-
-* when creating a table:
-  ``CREATE TABLE ... (..., foo BLOB COLUMN_FORMAT COMPRESSED, ...);``
-
-* when altering a table and modifying a column to the compressed format:
-  ``ALTER TABLE ... MODIFY [COLUMN] ... COLUMN_FORMAT COMPRESSED``, or
-  ``ALTER TABLE ... CHANGE [COLUMN] ... COLUMN_FORMAT COMPRESSED``.
-
-Unlike Oracle MySQL, compression is applicable to generated stored columns. Use
-this syntax extension as follows:
-
-.. code-block:: mysql
-
-   mysql> CREATE TABLE t1(
-	  id INT,
-	  a BLOB,
-	  b JSON COLUMN_FORMAT COMPRESSED,
-	  g BLOB GENERATED ALWAYS AS (a) STORED COLUMN_FORMAT COMPRESSED WITH COMPRESSION_DICTIONARY numbers
-        ) ENGINE=InnoDB;
-
-To decompress a column, specify a value other than ``COMPRESSED`` to
-``COLUMN_FORMAT``: ``FIXED``, ``DYNAMIC``, or ``DEFAULT``. If there is a column
-compression/decompression request in an ``ALTER TABLE``, it is forced to the
-``COPY`` algorithm.
-
-Two new variables: :ref:`innodb_compressed_columns_zip_level` and
-:ref:`innodb_compressed_columns_threshold` have been implemented.
-
-.. _compression_dictionary:
-
-Compression dictionary support
-==============================
-
-To achieve a better compression ratio on relatively small individual data items,
-it is possible to predefine a compression dictionary, which is a set of strings
-for each compressed column.
-
-Compression dictionaries can be represented as a list of words in the form of a
-string (comma or any other character can be used as a delimiter although not
-required). In other words, ``a,bb,ccc``, ``a bb ccc`` and ``abbccc`` will have
-the same effect. However, the latter is more compact. Quote symbol
-quoting is handled by regular SQL quoting. The maximum supported dictionary length
-is 32506 bytes (``zlib`` limitation).
-
-The compression dictionary is stored in a new system *InnoDB* table.  As this
-table is of the data dictionary kind, concurrent reads are allowed, but writes
-are serialized, and reads are blocked by writes. Table read through old read
-views are not supported, similar to *InnoDB* internal DDL transactions.
-
-Interaction with `innodb_force_recovery` variable
------------------------------------------------------------
-
-Compression dictionary operations are treated like DDL operations with the
-exception when `innodb_force_value` is set to ``3``: with values
-less than ``3``, compression dictionary operations are allowed, and with
-values >= ``3``, they are forbidden.
-
-.. note::
-
-  Prior to :ref:`8.0.15-6` using Compression dictionary operations
-  with `innodb_force_recovery` variable set to value > 0 would result in
-  an error.
-
-Example
--------
-
-In order to use the compression dictionary you need to create it. This
-can be done by running:
-
-.. code-block:: mysql
-
-   mysql> SET @dictionary_data = 'one' 'two' 'three' 'four';
-   Query OK, 0 rows affected (0.00 sec)
-
-   mysql> CREATE COMPRESSION_DICTIONARY numbers (@dictionary_data);
-   Query OK, 0 rows affected (0.00 sec)
-
-To create a table that has both compression and compressed dictionary support
-you should run:
-
-.. code-block:: mysql
-
-   mysql> CREATE TABLE t1(
-           id INT,
-           a BLOB COLUMN_FORMAT COMPRESSED,
-           b BLOB COLUMN_FORMAT COMPRESSED WITH COMPRESSION_DICTIONARY numbers
-         ) ENGINE=InnoDB;
-
-The following example shows how to insert a sample of JSON data into the table:
-
-.. code-block:: mysql
-
-   SET @json_value =
-   '[\n'
-   ' {\n'
-   ' "one" = 0,\n'
-   ' "two" = 0,\n'
-   ' "three" = 0,\n'
-   ' "four" = 0\n'
-   ' },\n'
-   ' {\n'
-   ' "one" = 0,\n'
-   ' "two" = 0,\n'
-   ' "three" = 0,\n'
-   ' "four" = 0\n'
-   ' },\n'
-   ' {\n'
-   ' "one" = 0,\n'
-   ' "two" = 0,\n'
-   ' "three" = 0,\n'
-   ' "four" = 0\n'
-   ' },\n'
-   ' {\n'
-   ' "one" = 0,\n'
-   ' "two" = 0,\n'
-   ' "three" = 0,\n'
-   ' "four" = 0\n'
-   ' }\n'
-   ']\n'
-   ;
-
-.. code-block:: mysql
-
-   mysql> INSERT INTO t1 VALUES(0, @json_value, @json_value);
-   Query OK, 1 row affected (0.01 sec)
-
-
-INFORMATION_SCHEMA Tables
-=========================
-
-This feature implements two new ``INFORMATION_SCHEMA`` tables.
-
-.. _COMPRESSION_DICTIONARY:
-
-.. rubric:: ``INFORMATION_SCHEMA.COMPRESSION_DICTIONARY``
-
-.. list-table::
-      :header-rows: 1
-
-      * - Column Name
-        - Description
-      * - 'BIGINT(21)_UNSIGNED dict_version'
-        - 'dictionary version'
-      * - 'VARCHAR(64) dict_name'
-        - 'dictionary name'
-      * - 'BLOB dict_data'
-        - 'compression dictionary string'
-
-This table provides a view over the internal compression dictionary. The
-``SUPER`` privilege is required to query it.
-
-.. _COMPRESSION_DICTIONARY_TABLES:
-
-.. rubric:: ``INFORMATION_SCHEMA.COMPRESSION_DICTIONARY_TABLES``
-
-.. list-table::
-      :header-rows: 1
-
-      * - Column Name
-        - Description
-      * - 'BIGINT(21)_UNSIGNED table_schema'
-        - 'table schema'
-      * - 'BIGINT(21)_UNSIGNED table_name'
-        - 'table ID from ``INFORMATION_SCHEMA.INNODB_SYS_TABLES``'
-      * - 'BIGINT(21)_UNSIGNED column_name'
-        - 'column position (starts from ``0`` as in ``INFORMATION_SCHEMA.INNODB_SYS_COLUMNS``)'
-      * - 'BIGINT(21)_UNSIGNED dict_name'
-        - 'dictionary ID'
-
-This table provides a view over the internal table that stores the mapping
-between the compression dictionaries and the columns using them. The ``SUPER``
-privilege is require to query it.
-
-Limitations
-===========
-
-Compressed columns cannot be used in indices (neither on their own nor as parts
-of composite keys).
-
-.. note::
-
-  ``CREATE TABLE t2 AS SELECT * FROM t1`` will create a new table with a
-  compressed column, whereas ``CREATE TABLE t2 AS SELECT CONCAT(a,'') AS a FROM
-  t1`` will not create compressed columns.
-
-  At the same time, after executing ``CREATE TABLE t2 LIKE t1`` statement,
-  ``t2.a`` will have ``COMPRESSED`` attribute.
-
-``ALTER TABLE ... DISCARD/IMPORT TABLESPACE`` is not supported for tables with
-compressed columns. To export and import tablespaces with compressed columns,
-you need to uncompress them first with: ``ALTER TABLE ... MODIFY ...
-COLUMN_FORMAT DEFAULT``.
-
-mysqldump command line parameters
-=================================
-
-By default, with no additional options, ``mysqldump`` will generate a *MySQL*
-compatible SQL output.
-
-All ``/*!50633 COLUMN_FORMAT COMPRESSED */`` and ``/*!50633 COLUMN_FORMAT
-COMPRESSED WITH COMPRESSION_DICTIONARY <dictionary> */`` won't be in the dump.
-
-When a new option :ref:`enable-compressed-columns` is specified, all
-``/*!50633 COLUMN_FORMAT COMPRESSED */`` will be left intact and all ``/*!50633
-COLUMN_FORMAT COMPRESSED WITH COMPRESSION_DICTIONARY <dictionary> */`` will be
-transformed into ``/*!50633 COLUMN_FORMAT COMPRESSED */``. In this mode the
-dump will contain the necessary SQL statements to create compressed columns,
-but without dictionaries.
-
-When a new :ref:`enable-compressed-columns-with-dictionaries` option is
-specified, dump will contain all compressed column attributes and compression
-dictionary.
-
-Moreover, the following dictionary creation fragments will be added before
-``CREATE TABLE`` statements which are going to use these dictionaries for the
-first time.
-
-.. code-block:: mysql
-
-  /*!50633 DROP COMPRESSION_DICTIONARY IF EXISTS <dictionary>; */
-  /*!50633 CREATE COMPRESSION_DICTIONARY <dictionary>(...); */
-
-Two new options :ref:`add-drop-compression-dictionary` and
-:ref:`skip-add-drop-compression-dictionary` will control if ``/*!50633 DROP
-COMPRESSION_DICTIONARY IF EXISTS <dictionary> */`` part from previous paragraph
-will be skipped or not. By default, :ref:`add-drop-compression-dictionary`
-mode will be used.
-
-When both :ref:`enable-compressed-columns-with-dictionaries` and
-``--tab=<dir>`` (separate file for each table) options are specified, necessary
-compression dictionaries will be created in each output file using the
-following fragment (regardless of the values of
-:ref:`add-drop-compression-dictionary` and
-:ref:`skip-add-drop-compression-dictionary` options).
-
-.. code-block:: mysql
-
-  /*!50633 CREATE COMPRESSION_DICTIONARY IF NOT EXISTS <dictionary>(...); */
-
-Version Specific Information
-============================
-
-  * :ref:`8.0.13-3`: The feature was ported from *Percona Server for MySQL* 5.7.
-
-System Variables
-================
-
-.. _innodb_compressed_columns_zip_level:
-
-.. rubric:: ``innodb_compressed_columns_zip_level``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - Yes
-   * - Config file
-     - Yes
-   * - Scope
-     - Global
-   * - Dynamic
-     - Yes
-   * - Data type
-     - Numeric
-   * - Default
-     - 6
-   * - Range
-     - ``0``-``9``
-
-This variable is used to specify the compression level used for compressed
-columns. Specifying ``0`` will use no compression, ``1`` the fastest and ``9``
-the best compression. Default value is ``6``.
-
-.. _innodb_compressed_columns_threshold:
-
-.. rubric:: ``innodb_compressed_columns_threshold``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - Yes
-   * - Config file
-     - Yes
-   * - Scope
-     - Global
-   * - Dynamic
-     - Yes
-   * - Data type
-     - Numeric
-   * - Default
-     - 96
-   * - Range
-     - ``1`` - ``2^64-1`` (or ``2^32-1`` for 32-bit release)
-
-By default a value being inserted will be compressed if its length exceeds
-:ref:`innodb_compressed_columns_threshold` bytes. Otherwise, it will be
-stored in raw (uncompressed) form.
-
-Please also notice that because of the nature of some data, its compressed
-representation can be longer than the original value. In this case it does not
-make sense to store such values in compressed form as *Percona Server for MySQL* would
-have to waste both memory space and CPU resources for unnecessary
-decompression. Therefore, even if the length of such non-compressible values
-exceeds :ref:`innodb_compressed_columns_threshold`, they will be stored in
-an uncompressed form (however, an attempt to compress them will still be made).
-
-This parameter can be tuned in order to skip unnecessary attempts of data
-compression for values that are known in advance by the user to have bad
-compression ratio of their first N bytes.
-
-.. seealso::
-
-   How to find a good/optimal dictionary for zlib 'setDictionary' when processing a given set of data?
-      http://stackoverflow.com/questions/2011653/how-to-find-a-good-optimal-dictionary-for-zlib-setdictionary-when-processing-a
diff --git a/doc/source/flexibility/extended_mysqlbinlog.rst b/doc/source/flexibility/extended_mysqlbinlog.rst
deleted file mode 100644
index 3da2fdc5dd32..000000000000
--- a/doc/source/flexibility/extended_mysqlbinlog.rst
+++ /dev/null
@@ -1,36 +0,0 @@
-.. _extended_mysqlbinlog:
-
-========================
-Extended ``mysqlbinlog``
-========================
-
-*Percona Server for MySQL* has implemented compression support for
-:command:`mysqlbinlog`. This is similar to support that both ``mysql`` and
-``mysqldump`` programs include (the ``-C``, ``--compress`` options "Use
-compression in server/client protocol"). Using the compressed protocol helps
-reduce the bandwidth use and speed up transfers. 
-
-*Percona Server for MySQL* has also implemented support for ``SSL``.
-:command:`mysqlbinlog` now accepts the ``SSL`` connection options as all the
-other client programs. This feature can be useful with
-``--read-from-remote-server`` option. Following ``SSL`` options are now
-available:
-
- * :option:`--ssl` - Enable SSL for connection (automatically enabled with
-   other flags).
- * :option:`--ssl-ca=name` - CA file in PEM format (check OpenSSL docs,
-   implies --ssl).
- * :option:`--ssl-capath=name` - CA directory (check OpenSSL docs, implies
-   --ssl).
- * :option:`--ssl-cert=name` - X509 cert in PEM format (implies --ssl).
- * :option:`--ssl-cipher=name` - SSL cipher to use (implies --ssl).
- * :option:`--ssl-key=name` - X509 key in PEM format (implies --ssl).
- * :option:`--ssl-verify-server-cert` - Verify server's "Common Name" in its
-   cert against hostname used when connecting. This option is disabled by
-   default.
-
-Version Specific Information
-============================
-
-* `8.0.12-1`: The feature was ported from *Percona Server for MySQL* 5.7
-
diff --git a/doc/source/flexibility/extended_mysqldump.rst b/doc/source/flexibility/extended_mysqldump.rst
deleted file mode 100644
index e00923effde8..000000000000
--- a/doc/source/flexibility/extended_mysqldump.rst
+++ /dev/null
@@ -1,52 +0,0 @@
-.. _extended_mysqldump:
-
-================================================================================
-Extended ``mysqldump``
-================================================================================
-
-.. _mysqldump_backup_locks:
-
-Backup Locks support
-================================================================================
-
-When used together with the :ref:`--single-transaction` option, the
-:ref:`lock-for-backup` option makes ``mysqldump`` issue ``LOCK
-TABLES FOR BACKUP`` before starting the dump operation to prevent
-unsafe statements that would normally result in an inconsistent
-backup.
-
-More information can be found on the :ref:`backup_locks` feature documentation.
-
-.. _mysqldump_compressed_columns:
-
-Compressed Columns support
-================================================================================
-
-:command:`mysqldump` supports the :ref:`compressed_columns` feature. More
-information about the relevant options can be found on the
-:ref:`compressed_columns` feature page.
-
-.. _mysqldump_order_by_primary_desc:
-
-Taking backup by descending primary key order
-================================================================================
-
-:ref:`--order-by-primary-desc` tells ``mysqldump`` to take the backup by
-descending primary key order (``PRIMARY KEY DESC``) which can be useful if
-the storage engine is using the reverse order column for a primary key.
-
-RocksDB support
-================================================================================
-
-:command:`mysqldump` detects when MyRocks is installed and available.
-If there is a session variable named
-:ref:`rocksdb_skip_fill_cache` :command:`mysqldump` sets it to **1**.
-
-:command:`mysqldump` will now automatically enable session the variable
-:ref:`rocksdb_bulk_load` if it is supported by the target server.
-
-Version Specific Information
-================================================================================
-
-* `8.0.12-1`: The feature was ported from *Percona Server for MySQL* 5.7
-
diff --git a/doc/source/flexibility/extended_select_into_outfile.rst b/doc/source/flexibility/extended_select_into_outfile.rst
deleted file mode 100644
index 5e5e23db6a3d..000000000000
--- a/doc/source/flexibility/extended_select_into_outfile.rst
+++ /dev/null
@@ -1,25 +0,0 @@
-.. _extended_select_into_outfile:
-
-===========================================
-Extended ``SELECT INTO OUTFILE/DUMPFILE``
-===========================================
-
-*Percona Server for MySQL* has extended the ``SELECT INTO ... OUTFILE`` and ``SELECT INTO
-DUMPFILE`` `commands <http://dev.mysql.com/doc/refman/8.0/en/select-into.html>`_
-to add the support for UNIX sockets and named pipes. Before this was implemented
-the database would return an error for such files.
-
-This feature allows using ``LOAD DATA LOCAL INFILE`` in combination with
-``SELECT INTO OUTFILE`` to quickly load multiple partitions across the network
-or in other setups, without having to use an intermediate file which wastes
-space and I/O.
-
-Version Specific Information
-============================
-
-* `8.0.12-1`: The feature was ported from *Percona Server for MySQL* 5.7.
-
-Other Reading
-=============
-
-* *MySQL* bug: :mysqlbug:`44835`
diff --git a/doc/source/flexibility/extended_set_var.rst b/doc/source/flexibility/extended_set_var.rst
deleted file mode 100644
index bfa80867951f..000000000000
--- a/doc/source/flexibility/extended_set_var.rst
+++ /dev/null
@@ -1,47 +0,0 @@
-.. _extended_set_var:
-.. _set-statement-for.upstream.replacing:
-
-================================================================================
-Extended SET VAR Optimizer Hint
-================================================================================
-
-*Percona Server for MySQL* 8.0 extends the ``SET_VAR`` introduced in *MySQL* 8.0
-effectively replacing the ``SET STATEMENT ... FOR`` statement. ``SET_VAR`` is an
-optimizer hint that can be applied to session variables.
-
-*Percona Server for MySQL* 8.0 extends the ``SET_VAR`` hint to support the
-following:
-
-- The ``OPTIMIZE TABLE`` statement
-- MyISAM session variables
-- Plugin or Storage Engine variables
-- InnoDB Session variables
-- The ``ALTER TABLE`` statement
-- ``CALL stored_proc()`` statement
-- The ``ANALYZE TABLE`` statement
-- The ``CHECK TABLE`` statement
-- The ``LOAD INDEX`` statement (used for MyISAM)
-- The ``CREATE TABLE`` statement
-
-*Percona Server for MySQL* 8.0 also supports setting the following variables by
-using ``SET_VAR``:
-
-.. hlist::
-   :columns: 2
-
-
-   - innodb_lock_wait_timeout
-   - innodb_tmpdir
-   - innodb_ft_user_stopword_table
-   - block_encryption_mode
-   - histogram_generation_max_mem_size
-   - myisam_sort_buffer_size
-   - myisam_repair_threads
-   - myisam_stats_method
-   - preload_buffer_size (used by MyISAM only)
-  
-.. seealso::
-
-   *MySQL* Documentation: Variable-setting hint syntax
-      https://dev.mysql.com/doc/refman/8.0/en/optimizer-hints.html#optimizer-hints-set-var
-   
diff --git a/doc/source/flexibility/improved_memory_engine.rst b/doc/source/flexibility/improved_memory_engine.rst
deleted file mode 100644
index a3546da09837..000000000000
--- a/doc/source/flexibility/improved_memory_engine.rst
+++ /dev/null
@@ -1,193 +0,0 @@
-.. _improved_memory_engine:
-
-====================================
- ``Improved MEMORY`` Storage Engine
-====================================
-
-As of ``MySQL`` 5.5.15, a *Fixed Row Format* (``FRF``) is still being used in the ``MEMORY`` storage engine. The fixed row format imposes restrictions on the type of columns as it assigns on advance a limited amount of memory per row. This renders a ``VARCHAR`` field in a ``CHAR`` field in practice and makes impossible to have a ``TEXT`` or ``BLOB`` field with that engine implementation.
-
-To overcome this limitation, the *Improved MEMORY Storage Engine* is introduced in this release for supporting **true** ``VARCHAR``, ``VARBINARY``, ``TEXT`` and ``BLOB`` fields in ``MEMORY`` tables.
-
-This implementation is based on the *Dynamic Row Format* (``DFR``) introduced by the `mysql-heap-dynamic-rows <http://code.google.com/p/mysql-heap-dynamic-rows/>`_ patch.
-
-``DFR`` is used to store column values in a variable-length form, thus helping to decrease memory footprint of those columns and making possible ``BLOB`` and ``TEXT`` fields and real ``VARCHAR`` and ``VARBINARY``.
-
-Unlike the fixed implementation, each column value in ``DRF`` only uses as much space as required. This is, for variable-length values, up to 4 bytes is used to store the actual value length, and then only the necessary number of blocks is used to store the value.
-
-Rows in ``DFR`` are represented internally by multiple memory blocks, which means that a single row can consist of multiple blocks organized into one set. Each row occupies at least one block, there can not be multiple rows within a single block. Block size can be configured when creating a table (see below).
-
-This ``DFR`` implementation has two caveats regarding to ordering and indexes.
-
-Caveats
-=======
-
-Ordering of Rows
-----------------
-
-In the absence of ``ORDER BY``, records may be returned in a different order than the previous ``MEMORY`` implementation.
-
-This is not a bug. Any application relying on a specific order without an ``ORDER BY`` clause may deliver unexpected results. A specific order without ``ORDER BY`` is a side effect of a storage engine and query optimizer implementation which may and will change between minor *MySQL* releases.
-
-
-Indexing
---------
-
-It is currently impossible to use indexes on ``BLOB`` columns due to some limitations of the *Dynamic Row Format*. Trying to create such an index will fail with the following error: ::
-
-  BLOB column '<name>' can't be used in key specification with the used table type.
-
-Restrictions
-============
-
-For performance reasons, a mixed solution is implemented: the fixed format is used at the beginning of the row, while the dynamic one is used for the rest of it.
-
-The size of the fixed-format portion of the record is chosen automatically on ``CREATE TABLE`` and cannot be changed later. This, in particular, means that no indexes can be created later with ``CREATE INDEX`` or ``ALTER TABLE`` when the dynamic row format is used. 
-
-All values for columns used in indexes are stored in fixed format at the first block of the row, then the following columns are handled with ``DRF``.
-
-This sets two restrictions to tables:
-
-  * the order of the fields and therefore,
-
-  * the minimum size of the block used in the table.
-
-Ordering of Columns
--------------------
-
-The columns used in fixed format must be defined before the dynamic ones in the ``CREATE TABLE`` statement. If this requirement is not met, the engine will not be able to add blocks to the set for these fields and they will be treated as fixed.
-
-Minimum Block Size
-------------------
-
-The block size has to be big enough to store all fixed-length information in the first block. If not, the ``CREATE TABLE`` or ``ALTER TABLE`` statements will fail (see below).
-
-Limitations
-===========
-
-*MyISAM* tables are still used for query optimizer internal temporary tables where the ``MEMORY`` tables could be used now instead: for temporary tables containing large ``VARCHAR``s, ``BLOB``, and ``TEXT`` columns.
-
-Setting Row Format
-==================
-
-Taking the restrictions into account, the *Improved MEMORY Storage Engine* will choose ``DRF`` over ``FRF`` at the moment of creating the table according to following criteria:
-
-  * There is an implicit request of the user in the column types **OR**
-
-  * There is an explicit request of the user **AND** the overhead incurred by ``DFR`` is beneficial.
-
-Implicit Request
-----------------
-
-The implicit request by the user is taken when there is at least one ``BLOB`` or ``TEXT`` column in the table definition. If there are none of these columns and no relevant option is given, the engine will choose ``FRF``.
-
-For example, this will yield the use of the dynamic format: ::
-
-  mysql> CREATE TABLE t1 (f1 VARCHAR(32), f2 TEXT, PRIMARY KEY (f1)) ENGINE=HEAP;
-
-While this will not: ::
-
-  mysql> CREATE TABLE t1 (f1 VARCHAR(16), f2 VARCHAR(16), PRIMARY KEY (f1)) ENGINE=HEAP;
-
-Explicit Request
-----------------
-
-The explicit request is set with one of the following options in the ``CREATE TABLE`` statement:
-
-  * ``KEY_BLOCK_SIZE = <value>``
-
-    * Requests the DFR with the specified block size (in bytes)
-
-Despite its name, the ``KEY_BLOCK_SIZE`` option refers to a block size used to store data rather then indexes. The reason for this is that an existing ``CREATE TABLE`` option is reused to avoid introducing new ones.
-
-*The Improved MEMORY Engine* checks whether the specified block size is large enough to keep all key column values. If it is too small, table creation will abort with an error.
-
-After ``DRF`` is requested explicitly and there are no ``BLOB`` or ``TEXT`` columns in the table definition, the *Improved MEMORY Engine* will check if using the dynamic format provides any space saving benefits as compared to the fixed one:
-
-  * if the fixed row length is less than the dynamic block size (plus the dynamic row overhead - platform dependent) **OR**
-
-  * there isn't any variable-length columns in the table or ``VARCHAR`` fields are declared with length 31 or less,
-
-the engine will revert to the fixed format as it is more space efficient in such case. The row format being used by the engine can be checked using ``SHOW TABLE STATUS``.
-
-Examples
-========
-
-On a 32-bit platform: ::
-
-  mysql> CREATE TABLE t1 (f1 VARCHAR(32), f2 VARCHAR(32), f3 VARCHAR(32), f4 VARCHAR(32),
-                          PRIMARY KEY (f1)) KEY_BLOCK_SIZE=124 ENGINE=HEAP;
-  
-  mysql> SHOW TABLE STATUS LIKE 't1';
-  Name	Engine	Version	   Rows	Avg_row_length	Data_length	Max_data_length	Index_length	Data_free	Auto_increment	Create_time	Update_time	Check_time	Collation	Checksum	Create_options	Comment
-  t1	MEMORY	10	   X	0	X	0	0	NULL	NULL	NULL	NULL	latin1_swedish_ci	NULL	row_format=DYNAMIC KEY_BLOCK_SIZE=124	
-
-On a 64-bit platform: ::
-
-  mysql> CREATE TABLE t1 (f1 VARCHAR(32), f2 VARCHAR(32), f3 VARCHAR(32), f4 VARCHAR(32),
-                          PRIMARY KEY (f1)) KEY_BLOCK_SIZE=124 ENGINE=HEAP;
-  
-  mysql> SHOW TABLE STATUS LIKE 't1';
-  Name	Engine	Version	   Rows	Avg_row_length	Data_length	Max_data_length	Index_length	Data_free	Auto_increment	Create_time	Update_time	Check_time	Collation	Checksum	Create_options	Comment	
-  t1	MEMORY	10	   X	0	X	0	0	NULL	NULL	NULL	NULL	latin1_swedish_ci	NULL	KEY_BLOCK_SIZE=124	
-
-Implementation Details
-======================
-
-*MySQL* *MEMORY* tables keep data in arrays of fixed-size chunks. These chunks are organized into two groups of ``HP_BLOCK`` structures:
-
-  * ``group1`` contains indexes, with one ``HP_BLOCK`` per key (part of ``HP_KEYDEF``),
-
-  * ``group2`` contains record data, with a single ``HP_BLOCK`` for all records.
-
-While columns used in indexes are usually small, other columns in the table may need to accommodate larger data. Typically, larger data is placed into ``VARCHAR`` or ``BLOB`` columns.
-
-*The Improved MEMORY Engine* implements the concept of dataspace, ``HP_DATASPACE``, which incorporates the ``HP_BLOCK`` structures for the record data, adding more information for managing variable-sized records.
-
-Variable-size records are stored in multiple “chunks”, which means that a single record of data (a database “row”) can consist of multiple chunks organized into one “set”, contained in ``HP_BLOCK`` structures.
-
-In variable-size format, one record is represented as one or many chunks depending on the actual data, while in fixed-size mode, one record is always represented as one chunk. The index structures would always point to the first chunk in the chunkset.
-
-Variable-size records are necessary only in the presence of variable-size columns. The *Improved Memory Engine* will be looking for ``BLOB`` or ``VARCHAR`` columns with a declared length of 32 or more. If no such columns are found, the table will be switched to the fixed-size format. You should always put such columns at the end of the table definition in order to use the variable-size format.
-
-Whenever data is being inserted or updated in the table, the *Improved Memory Engine* will calculate how many chunks are necessary.
-
-For ``INSERT`` operations, the engine only allocates new chunksets in the recordspace. For ``UPDATE`` operations it will modify the length of the existing chunkset if necessary, unlinking unnecessary chunks at the end, or allocating and adding more if a larger length is needed.
-
-When writing data to chunks or copying data back to a record, fixed-size columns are copied in their full format, while ``VARCHAR`` and ``BLOB`` columns are copied based on their actual length, skipping any ``NULL`` values.
-
-When allocating a new chunkset of N chunks, the engine will try to allocate chunks one-by-one, linking them as they become allocated. For allocating a single chunk, it will attempt to reuse a deleted (freed) chunk. If no free chunks are available, it will try to allocate a new area inside a ``HP_BLOCK``.
-
-When freeing chunks, the engine will place them at the front of a free list in the dataspace, each one containing a reference to the previously freed chunk.
-
-The allocation and contents of the actual chunks varies between fixed and variable-size modes:
-
-  * Format of a fixed-size chunk:
-
-    * ``uchar[]``
-
-      * With ``sizeof=chunk_dataspace_length``, but at least ``sizeof(uchar*)`` bytes. It keeps actual data or pointer to the next deleted chunk, where ``chunk_dataspace_length`` equals to full record length
-
-    * ``uchar`` 
-
-      * Status field (1 means “in use”, 0 means “deleted”)
-
-  * Format of a variable-size chunk:
-
-      * ``uchar[]``
-
-        * With ``sizeof=chunk_dataspace_length``, but at least ``sizeof(uchar*)`` bytes. It keeps actual data or pointer to the next deleted chunk, where ``chunk_dataspace_length`` is set according to table's ``key_block_size``
-
-    * ``uchar*`` 
-
-      * Pointer to the next chunk in this chunkset, or NULL for the last chunk
-
-    * ``uchar``
-
-      * Status field (1 means “first”, 0 means “deleted”, 2 means “linked”)
-
-Total chunk length is always aligned to the next ``sizeof(uchar*)``.
-
-See Also
-========
-
-  * `Dynamic row format for MEMORY tables <http://www.mysqlperformanceblog.com/2011/09/06/dynamic-row-format-for-memory-tables/>`_
diff --git a/doc/source/flexibility/innodb_fts_improvements.rst b/doc/source/flexibility/innodb_fts_improvements.rst
deleted file mode 100644
index ee759e4122c8..000000000000
--- a/doc/source/flexibility/innodb_fts_improvements.rst
+++ /dev/null
@@ -1,69 +0,0 @@
-.. _innodb_fts_improvements:
-
-====================================
-InnoDB Full-Text Search Improvements
-====================================
-
-.. contents::
-   :local:
-
-.. _ignoring_stopword_list:
-
-======================
-Ignoring Stopword List
-======================
-
-By default all Full-Text Search indexes check the `stopwords list
-<https://dev.mysql.com/doc/refman/8.0/en/fulltext-stopwords.html>`_,
-to see if any indexed elements *contain* one of the words on that list.
-
-Using this list for n-gram indexes isn't always suitable, as an example, any
-item that contains ``a`` or ``i`` will be ignored. Another word that can't be
-searched is ``east``, this one will find no matches because ``a`` is on the
-FTS stopword list.
-
-To resolve this issue, *Percona Server for MySQL* has the
-:ref:`innodb_ft_ignore_stopwords` variable to control whether
-*InnoDB* Full-Text Search should ignore the stopword list.
-
-Although this variable is introduced to resolve n-gram issues, it affects
-all Full-Text Search indexes as well.
-
-Being a stopword doesn't just mean to be a one of the predefined
-words from the list. Tokens shorter than `innodb_ft_min_token_size
-<https://dev.mysql.com/doc/refman/8.0/en/innodb-parameters.html#sysvar_innodb_ft_min_token_size>`_
-or longer than `innodb_ft_max_token_size
-<https://dev.mysql.com/doc/refman/8.0/en/innodb-parameters.html#sysvar_innodb_ft_max_token_size>`_
-are also considered stopwords. Therefore, when
-:ref:`innodb_ft_ignore_stopwords` is set to ``ON`` even for non-ngram
-FTS, ``innodb_ft_min_token_size`` / ``innodb_ft_max_token_size`` will be
-ignored meaning that in this case very short and very long words will
-also be indexed.
-
-System Variables
-================
-
-.. _innodb_ft_ignore_stopwords:
-
-.. rubric:: ``innodb_ft_ignore_stopwords``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - Yes
-   * - Config file
-     - Yes
-   * - Scope
-     - Session, Global
-   * - Dynamic
-     - Yes
-   * - Data type
-     - Boolean
-   * - Default
-     - ``OFF``
-
-When enabled, this variable will instruct *InnoDB* Full Text Search
-parser to ignore the stopword list when building/updating an FTS index.
diff --git a/doc/source/flexibility/log_warnings_suppress.rst b/doc/source/flexibility/log_warnings_suppress.rst
deleted file mode 100644
index 3ddcaf674547..000000000000
--- a/doc/source/flexibility/log_warnings_suppress.rst
+++ /dev/null
@@ -1,61 +0,0 @@
-.. _log_warning_suppress:
-
-===========================
- Suppress Warning Messages
-===========================
-
-This feature is intended to provide a general mechanism (using ``log_warnings_silence``) to disable certain warning messages to the log file. Currently, it is only implemented for disabling message #1592 warnings. This feature does not influence warnings delivered to a client. Please note that warning code needs to be a string:
-
-.. code-block:: mysql
-
-  mysql> SET GLOBAL log_warnings_suppress = '1592';
-  Query OK, 0 rows affected (0.00 sec)
-
-
-Version Specific Information
-============================
-
-  * `8.0.12-1`: The feature was ported from *Percona Server for MySQL* 5.7
-
-System Variables
-================
-
-.. _log_warnings_suppress:
-
-.. rubric:: ``log_warnings_suppress``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - Yes
-   * - Config file
-     - Yes
-   * - Scope
-     - Global
-   * - Dynamic
-     - Yes
-   * - Data type
-     - SET
-   * - Default
-     - ``(empty string)``
-   * - Range
-     - ``(empty string)``, ``1592``
-
-It is intended to provide a more general mechanism for disabling warnings than existed previously with variable :ref:`suppress_log_warning_1592`.
-When set to the empty string, no warnings are disabled. When set to ``1592``, warning #1592 messages (unsafe statement for binary logging) are suppressed.
-In the future, the ability to optionally disable additional warnings may also be added.
-
-
-Related Reading
-===============
-
-  * `MySQL bug 42851 <http://bugs.mysql.com/bug.php?id=42851>`_
-
-  * `MySQL InnoDB replication <http://dev.mysql.com/doc/refman/8.0/en/innodb-and-mysql-replication.html>`_
-
-  * `InnoDB Startup Options and System Variables <http://dev.mysql.com/doc/refman/8.0/en/innodb-parameters.html>`_
-
-  * `InnoDB Error Handling <http://dev.mysql.com/doc/refman/8.0/en/innodb-error-handling.html>`_
diff --git a/doc/source/flexibility/proxy_protocol_support.rst b/doc/source/flexibility/proxy_protocol_support.rst
deleted file mode 100644
index 89361f10ada8..000000000000
--- a/doc/source/flexibility/proxy_protocol_support.rst
+++ /dev/null
@@ -1,53 +0,0 @@
-.. _proxy_protocol_support:
-
-============================
- Support for PROXY protocol
-============================
-
-The proxy protocol allows an intermediate proxying server speaking proxy protocol (ie. HAProxy) between the server and the ultimate client (i.e. mysql client etc) to provide the source client address to the server, which normally would only see the proxying server address instead.
-
-As the proxy protocol amounts to spoofing the client address, it is disabled by default, and can be enabled on per-host or per-network basis for the trusted source addresses where trusted proxy servers are known to run. Unproxied connections are not allowed from these source addresses.
-
-.. note:: 
-
-   You need to ensure proper firewall ACL's in place when this feature is enabled. 
-
-Proxying is supported for TCP over IPv4 and IPv6 connections only. UNIX socket connections can not be proxied and do not fall under the effect of proxy-protocol-networks='*'.
-
-As a special exception, it is forbidden for the proxied IP address to be ``127.0.0.1`` or ``::1``.
-
-Version Specific Information
-============================
-
-  * `8.0.12-1`: The feature was ported from *Percona Server for MySQL* 5.7.
-
-System Variables
-================
-
-.. _proxy_protocol_networks:
-
-.. rubric:: ``proxy_protocol_networks``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - Yes
-   * - Config file
-     - Yes
-   * - Scope
-     - Global
-   * - Dynamic
-     - No
-   * - Default
-     - ``(empty string)``
-
-This variable is a global-only, read-only variable, which is either a ``*`` (to enable proxying globally, a non-recommended setting), or a list of comma-separated IPv4 and IPv6 network and host addresses, for which proxying is enabled. Network addresses are specified in CIDR notation, i.e. ``192.168.0.0/24``. To prevent source host spoofing, the setting of this variable must be as restrictive as possible to include only trusted proxy hosts.
-
-Related Reading
-===============
-
-  * `PROXY protocol specification <http://www.haproxy.org/download/1.5/doc/proxy-protocol.txt>`_
-
diff --git a/doc/source/flexibility/sequence_table.rst b/doc/source/flexibility/sequence_table.rst
deleted file mode 100644
index 8431fdb03852..000000000000
--- a/doc/source/flexibility/sequence_table.rst
+++ /dev/null
@@ -1,124 +0,0 @@
-.. _sequence_table:
-
-===============================================================================
-SEQUENCE_TABLE(n) Function
-===============================================================================
-
-*Percona Server for MySQL* 8.0.20-11 adds the SEQUENCE_TABLE() function.
-
-A sequence of numbers can be defined as an arithmetic progression when the common difference between two consecutive terms is always the same.
-
-The function is an inline table-valued function. A single SELECT statement generates a multi-row result set. In contrast, a scalar function (like `EXP(x) <https://dev.mysql.com/doc/refman/8.0/en/mathematical-functions.html#function_exp>`_ or `LOWER(str) <https://dev.mysql.com/doc/refman/8.0/en/string-functions.html#function_lower>`_ always  returns a single value of a specific data type.
-
-The `JSON_TABLE() <https://dev.mysql.com/doc/refman/8.0/en/json-table-functions.html>`_ is the only table function available in Oracle MySQL Server. ``JSON_TABLE`` and ``SEQUENCE_TABLE()`` are the only table functions available in Percona Server.
-
-The basic syntax is the following:
-
-* SEQUENCE_TABLE(n) [AS] alias
- 
-  *Usage*:
-  SELECT ... FROM SEQUENCE_TABLE(n) [AS] alias
-
-    .. code-block:: mysql
-
-        SEQUENCE_TABLE(
-            n
-        ) [AS] alias
-    
-``n:`` The number of generated values.
-
-As with any `derived tables <https://dev.mysql.com/doc/refman/8.0/en/derived-tables.html>`_, a table function requires an `alias <https://dev.mysql.com/doc/refman/8.0/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. ::
-
-    SELECT * FROM SEQUENCE_TABLE(n) AS tt;
-    SELECT <expr(value)> 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 then ``n``. In this example, enter the following statement to generate a sequence:
-
-..  code-block:: mysql
-
-    mysql> SELECT * FROM SEQUENCE_TABLE(3) AS tt;
-    +-------+
-    | value |
-    +-------+
-    |     0 |
-    |     1 |
-    |     2 |
-    +-------+
-    
-You can define  the initial term using the ``WHERE`` clause. The following example starts the sequence with ``4``.
-
-.. code-block:: mysql
-
-    SELECT value AS result FROM SEQUENCE_TABLE(8) AS tt WHERE value >= 4;
-    +--------+
-    | result |
-    +--------+
-    |      4 |
-    |      5 |
-    |      6 |
-    |      7 |
-    +--------+
-    
-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:
-
-.. code-block:: mysql
-
-    SELECT value AS result FROM SEQUENCE_TABLE(8) AS tt WHERE value % 2 = 0;
-    +--------+
-    | result |
-    +--------+
-    |      0 |
-    |      2 |
-    |      4 |
-    |      6 |
-    +--------+
-
-The following is an example of using the function to populate a table with a set of random numbers:
-
-.. code-block:: mysql
-
-    mysql> SELECT FLOOR(RAND()) * 100) AS result FROM SEQUENCE_TABLE(4) AS tt;
-    +--------+
-    | result |
-    +--------+
-    |     24 |
-    |     56 |
-    |     70 |
-    |     25 |
-    +--------+
-
-You can populate a table with a set of pseudo-random strings with the following statement:
-
-.. code-block:: mysql
-
-    mysql> SELECT MD5(value) AS result FROM SEQUENCE_TABLE(4) AS tt;
-    +----------------------------------+
-    | result                           |
-    +----------------------------------+
-    | f17d9c990f40f8ac215f2ecdfd7d0451 |
-    | 2e5751b7cfd7f053cd29e946fb2649a4 |
-    | b026324c6904b2a9cb4b88d6d61c81d1 |
-    | 26ab0db90d72e28ad0ba1e22ee510510 |
-    +----------------------------------+
-
-You can add the sequence as a column to a new table or an existing table, as shown in this example:
-
-.. code-block:: mysql
-
-    mysql> CREATE TABLE t1 AS SELECT * FROM SEQUENCE_TABLE(4) AS tt;
-    
-    mysql> SELECT * FROM t1;
-    +-------+
-    | value |
-    +-------+
-    |     0 |
-    |     1 |
-    |     2 |
-    |     3 |
-    +-------+
-
-There are many uses for a sequence when populating tables.
diff --git a/doc/source/flexibility/slowlog_rotation.rst b/doc/source/flexibility/slowlog_rotation.rst
deleted file mode 100644
index 1401ab99c9a0..000000000000
--- a/doc/source/flexibility/slowlog_rotation.rst
+++ /dev/null
@@ -1,70 +0,0 @@
-.. _slowlog_rotation:
-
-========================================
- Slow Query Log Rotation and Expiration
-========================================
-
-.. note:: 
-
-   This feature is currently **technical preview** quality.
-
-This feature was implemented in *Percona Server for MySQL* 8.0.27-18.
-
-Percona has implemented two new variables, :ref:`max_slowlog_size` and :ref:`max_slowlog_files` to provide users with ability to control the slow query log disk usage. These variables have the same behavior as the `max_binlog_size variable <https://dev.mysql.com/doc/refman/8.0/en/replication-options-binary-log.html#sysvar_max_binlog_size>`__ and the `max_binlog_files variable <https://dev.mysql.com/doc/refman/8.0/en/replication-options-binary-log.html#sysvar_max_binlog_size>`__ used for controlling the binary log.
-
-System Variables
-================
-
-.. _max_slowlog_size:
-
-.. rubric:: ``max_slowlog_size``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - Yes
-   * - Config file
-     - Yes
-   * - Scope
-     - Global
-   * - Dynamic
-     - Yes
-   * - Data type
-     - numeric
-   * - Default
-     - 0 (unlimited)
-   * - Range
-     - 0 - 1073741824
-
-The server rotates the slow query log when the log's size reaches this value. The default value is ``0``. If you limit the size and this feature is enabled, the server renames the slow query log file to `slow_query_log_file`.000001. 
-
-.. _max_slowlog_files:
-
-.. rubric:: ``max_slowlog_files``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - Yes
-   * - Config file
-     - Yes
-   * - Scope
-     - Global
-   * - Dynamic
-     - Yes
-   * - Data type
-     - numeric
-   * - Default
-     - 0 (unlimited)
-   * - Range
-     - 0 - 102400
-
-This variable limits the total amount of slow query log files and is used with :ref:`max_slowlog_size`. 
-
-The server creates and adds slow query logs until reaching the range's upper value. When the upper value is reached, the server creates a new slow query log file with a higher sequence number and deletes the log file with the lowest sequence number maintaining the total amount defined in the range.
\ No newline at end of file
diff --git a/doc/source/glossary.rst b/doc/source/glossary.rst
deleted file mode 100644
index 5f9a57d4f83f..000000000000
--- a/doc/source/glossary.rst
+++ /dev/null
@@ -1,103 +0,0 @@
-==========
- Glossary
-==========
-
-.. glossary::
-
-  ACID
-    Set of properties that guarantee database transactions are 
-    processed reliably. Stands for :term:`Atomicity`,
-    :term:`Consistency`, :term:`Isolation`, :term:`Durability`.
-
-  Atomicity
-    Atomicity means that database operations are applied following a
-    "all or nothing" rule. A transaction is either fully applied or not
-    at all.
-
-  Consistency
-    Consistency means that each transaction that modifies the database
-    takes it from one consistent state to another.
-
-  Durability
-    Once a transaction is committed, it will remain so.
-
-  Foreign Key
-    A referential constraint between two tables. Example: A purchase
-    order in the purchase_orders table must have been made by a customer
-    that exists in the customers table.
-
-  Isolation
-    The Isolation requirement means that no transaction can interfere
-    with another.
-
-  InnoDB
-    A :term:`Storage Engine` for MySQL and derivatives (:term:`Percona
-    Server`, :term:`MariaDB`) originally written by Innobase Oy, since 
-    acquired by Oracle. It provides :term:`ACID` compliant storage engine
-    with :term:`foreign key` support. As of :term:`MySQL` version 5.5, 
-    InnoDB became the default storage engine on all platforms.
-
-  Jenkins
-    `Jenkins <http://www.jenkins-ci.org>`_ is a continuous integration
-    system that we use to help ensure the continued quality of the
-    software we produce. It helps us achieve the aims of:
-
-     * no failed tests in trunk on any platform,
-     * aid developers in ensuring merge requests build and test on all platforms,
-     * no known performance regressions (without a damn good explanation).
-
-  LSN
-    Log Serial Number. A term used in relation to the :term:`InnoDB` or
-    :term:`XtraDB` storage engines.
-
-  MariaDB
-    A fork of :term:`MySQL` that is maintained primarily by Monty
-    Program AB. It aims to add features, fix bugs while maintaining 100%
-    backwards compatibility with MySQL.
-
-  my.cnf
-    The file name of the default MySQL configuration file.
-
-  MyISAM
-    A :term:`MySQL` :term:`Storage Engine` that was the default until
-    MySQL 5.5.
-
-  MySQL
-    An open source database that has spawned several distributions and
-    forks. MySQL AB was the primary maintainer and distributor until
-    bought by Sun Microsystems, which was then acquired by Oracle. As
-    Oracle owns the MySQL trademark, the term MySQL is often used for
-    the Oracle distribution of MySQL as distinct from the drop-in
-    replacements such as :term:`MariaDB` and :term:`Percona Server`.
-
-  NUMA
-    Non-Uniform Memory Access 
-    (`NUMA <http://en.wikipedia.org/wiki/Non-Uniform_Memory_Access>`_) is a
-    computer memory design used in multiprocessing, where the memory access
-    time depends on the memory location relative to a processor. Under NUMA,
-    a processor can access its own local memory faster than non-local memory,
-    that is, memory local to another processor or memory shared between
-    processors. The whole system may still operate as one unit, and all memory
-    is basically accessible from everywhere, but at a potentially higher latency
-    and lower performance.
-
-  Percona Server for MySQL
-    Percona's branch of :term:`MySQL` with performance and management improvements.
-
-  Percona Server
-    See :term:`Percona Server for MySQL`
-
-  Storage Engine
-    A :term:`Storage Engine` is a piece of software that implements the
-    details of data storage and retrieval for a database system. This
-    term is primarily used within the :term:`MySQL` ecosystem due to it
-    being the first widely used relational database to have an
-    abstraction layer around storage. It is analogous to a Virtual File
-    System layer in an Operating System. A VFS layer allows an operating
-    system to read and write multiple file systems (e.g. FAT, NTFS, XFS,
-    ext3) and a Storage Engine layer allows a database server to access
-    tables stored in different engines (e.g. :term:`MyISAM`, InnoDB).
-
-  XtraDB
-    Percona's improved version of :term:`InnoDB` providing performance,
-    features and reliability above what is shipped by Oracle in InnoDB.
diff --git a/doc/source/index.rst b/doc/source/index.rst
deleted file mode 100644
index a0c87eabce9e..000000000000
--- a/doc/source/index.rst
+++ /dev/null
@@ -1,252 +0,0 @@
-.. Percona Server documentation master file, created by
-   sphinx-quickstart on Mon Aug  8 01:24:46 2011.
-   You can adapt this file completely to your liking, but it should at least
-   contain the root `toctree` directive.
-
-.. _dochome:
-
-================================================================================
-|Percona Server| |version| - Documentation
-================================================================================
-
-|Percona Server| is a free, fully compatible, enhanced, and open source drop-in replacement for any MySQL database. It provides superior performance, scalability, and instrumentation.
-
-|Percona Server| is trusted by thousands of enterprises to provide better performance and concurrency for their most demanding workloads. It delivers higher value to MySQL server users with optimized performance, greater performance scalability and availability, enhanced backups, and increased visibility.
-
-Introduction
-================================================================================
-
-.. toctree::
-   :maxdepth: 1
-   :glob:
-
-   percona_xtradb
-   ps-versions-comparison
-   feature_comparison
-   changed_in_version
-
-Installation
-================================================================================
-
-.. toctree::
-   :maxdepth: 2
-   :glob:
-
-   installation
-   installation/post-installation
-
-In-place upgrades
-================================================================================
-
-.. toctree::
-   :maxdepth: 2
-   :glob:
-
-   upgrading_guide
-   upgrading_using_percona_repos
-   upgrading_tokudb_myrocks
-   upgrading_using_standalone_packages
-
-Run in Docker
-================================================================================
-
-.. toctree::
-   :maxdepth: 1
-   :glob:
-
-   installation/docker
-
-Scalability Improvements
-================================================================================
-
-.. toctree::
-   :maxdepth: 1
-   :glob:
-
-   scalability/innodb_io
-
-Performance Improvements
-================================================================================
-
-.. toctree::
-   :maxdepth: 1
-   :glob:
-
-   performance/adaptive_network_buffers
-   performance/aio_page_requests
-   performance/threadpool
-   performance/xtradb_performance_improvements_for_io-bound_highly-concurrent_workloads
-   performance/prefix_index_queries_optimization
-   performance/query_limit_records
-   performance/jemalloc-profiling
-   performance/procfs-plugin
-
-
-Flexibility Improvements
-================================================================================
-
-.. toctree::
-   :maxdepth: 1
-   :glob:
-
-   flexibility/binlogging_replication_improvements  
-   flexibility/compressed_columns
-    flexibility/extended_mysqlbinlog  
-    flexibility/extended_mysqldump
-   flexibility/extended_select_into_outfile  
-   flexibility/extended_set_var
-   flexibility/improved_memory_engine   
-   flexibility/log_warnings_suppress
-   flexibility/binlog_space
-   flexibility/proxy_protocol_support
-   flexibility/sequence_table
-   flexibility/slowlog_rotation
-
-Reliability Improvements
-================================================================================
-
-.. toctree::
-   :maxdepth: 1
-   :glob:
-
-   reliability/log_connection_error
-   reliability/innodb_corrupt_table_action
-
-Management Improvements
-================================================================================
-
-.. toctree::
-   :maxdepth: 1
-   :glob:
-
-   management/udf_percona_toolkit
-   management/kill_idle_trx
-   management/changed_page_tracking
-   management/enforce_engine
-   management/pam_plugin
-   management/innodb_expanded_fast_index_creation
-   management/backup_locks
-   management/audit_log_plugin
-   management/start_transaction_with_consistent_snapshot
-   management/extended_show_grants
-   management/utility_user
-
-Security Improvements
-================================================================================
-
-.. toctree::
-  :maxdepth: 1
-  :glob:
-
-  security/pam_plugin
-  security/simple-ldap
-  security/simple-ldap-variables
-  security/selinux
-  security/apparmor
-  security/data-at-rest-encryption
-  security/vault
-  security/using-keyring-plugin
-  security/using-kmip
-  security/encryption-functions
-  security/using-amz-kms
-  security/rotating-master-key
-  security/encrypting-tables
-  security/encrypting-tablespaces
-  security/encrypting-system-tablespace
-  security/encrypting-temporary-files
-  security/encrypting-binlogs
-  security/encrypting-redo-log
-  security/encrypting-undo-tablespace
-  security/encrypting-threads
-  security/encrypting-doublewrite-buffers
-  security/verifying-encryption
-  security/ssl-improvement
-  security/data-masking
-  security/system-variables
-
-Diagnostics Improvements
-================================================================================
-
-.. toctree::
-   :maxdepth: 1
-   :glob:
-
-   diagnostics/user_stats
-   diagnostics/slow_extended
-   diagnostics/innodb_show_status
-   diagnostics/show_engines
-   diagnostics/process_list
-   diagnostics/misc_info_schema_tables
-   diagnostics/thread_based_profiling
-   diagnostics/innodb_fragmentation_count
-   diagnostics/stacktrace
-   diagnostics/libcoredumper
-
-Percona MyRocks
-================================================================================
-
-.. toctree::
-   :maxdepth: 1
-   :glob:
-
-   MyRocks Introduction <myrocks/index>
-   MyRocks Installation <myrocks/install>
-   MyRocks Supported Features <myrocks/added-features>
-   MyRocks Limitations <myrocks/limitations>
-   MyRocks Differences <myrocks/differences>
-   MyRocks Information Schema Tables <myrocks/information-schema-tables>
-   MyRocks Server Variables <myrocks/variables>
-   MyRocks Status Variables <myrocks/status_variables>
-   MyRocks Gap Locks Detection <myrocks/gap_locks_detection>
-   MyRocks Data Loading <myrocks/data_loading>
-   MyRocks ZenFS <myrocks/zenfs>
-   
-TokuDB
-================================================================================
-
-.. toctree::
-   :maxdepth: 1
-   :glob:
-
-   tokudb/tokudb_intro
-   tokudb/tokudb_installation
-   tokudb/using_tokudb
-   tokudb/fast_updates
-   tokudb/tokudb_files_and_file_types
-   tokudb/tokudb_file_management
-   tokudb/tokudb_background_analyze_table
-   tokudb/tokudb_variables
-   tokudb/tokudb_status_variables
-   tokudb/tokudb_fractal_tree_indexing
-   tokudb/tokudb_troubleshooting
-   tokudb/tokudb_performance_schema
-   tokudb/tokudb_faq
-   tokudb/removing_tokudb
-
-Release notes
-================================================================================
-
-.. toctree::
-   :maxdepth: 1
-   :glob:
-
-   release-notes/release-notes_index
-
-Reference
-================================================================================
-
-.. toctree::
-   :maxdepth: 1
-   :glob:
-
-   upstream-bug-fixes
-   ps-variables
-   development
-   trademark-policy
-   index_info_schema_tables
-   faq
-   copyright
-   glossary
-
-* :ref:`genindex`
-* :ref:`modindex`
diff --git a/doc/source/index_info_schema_tables.rst b/doc/source/index_info_schema_tables.rst
deleted file mode 100644
index eeb4b9623e5f..000000000000
--- a/doc/source/index_info_schema_tables.rst
+++ /dev/null
@@ -1,37 +0,0 @@
-.. _index_info_schema_tables:
-
-========================================
- Index of ``INFORMATION_SCHEMA`` Tables
-========================================
-
-This is a list of the ``INFORMATION_SCHEMA TABLES`` that exist in *Percona Server for MySQL* with *XtraDB*. The entry for each table points to the page in the documentation where it's described.
-
-  * :ref:`CLIENT_STATISTICS`
-
-  * :ref:`GLOBAL_TEMPORARY_TABLES`
-
-  * :ref:`INDEX_STATISTICS`
-
-  * :ref:`INNODB_CHANGED_PAGES`
-
-  * :ref:`PROCFS`
-
-  * :ref:`QUERY_RESPONSE_TIME`
-
-  * :ref:`TABLE_STATISTICS`
-
-  * :ref:`TEMPORARY_TABLES`
-
-  * :ref:`THREAD_STATISTICS`
-
-  * :ref:`USER_STATISTICS`
-
-  * :ref:`XTRADB_INTERNAL_HASH_TABLES`
-
-  * :ref:`XTRADB_READ_VIEW`
-
-  * :ref:`XTRADB_RSEG`
-
-  * :ref:`XTRADB_ZIP_DICT`
-
-  * :ref:`XTRADB_ZIP_DICT_COLS`
diff --git a/doc/source/installation.rst b/doc/source/installation.rst
deleted file mode 100644
index 10ad3428a70d..000000000000
--- a/doc/source/installation.rst
+++ /dev/null
@@ -1,227 +0,0 @@
-.. _installation:
-
-=====================================
-Installing |Percona Server| |release|
-=====================================
-
-This page provides the information on how to you can install |Percona Server|. Following options are available:
-
-* :ref:`installing_from_binaries` (recommended)
-* Installing |Percona Server| from Downloaded :ref:`rpm <standalone_rpm>` or :ref:`apt <standalone_deb>` Packages
-* :ref:`installing_from_binary_tarball`
-* :ref:`installing_from_source_tarball`
-* :ref:`source_from_git`
-* :ref:`compile_from_source`
-
-Before installing, you might want to read the :doc:`release-notes/release-notes_index`.
-
-.. _installing_from_binaries:
-
-Installing |Percona Server| from Repositories
-=============================================
-
-|Percona| provides repositories for :program:`yum` (``RPM`` packages for *Red Hat*, *CentOS* and *Amazon Linux AMI*) and :program:`apt` (:file:`.deb` packages for *Ubuntu* and *Debian*) for software such as |Percona Server|, |Percona XtraBackup|, and *Percona Toolkit*. This makes it easy to install and update your software and its dependencies through your operating system's package manager. This is the recommended way of installing where possible.
-
-Following guides describe the installation process for using the official Percona repositories for :file:`.deb` and :file:`.rpm` packages.
-
-.. toctree::
-   :maxdepth: 1
-   :titlesonly:
-
-   installation/apt_repo
-   installation/yum_repo
-
-.. _installing_from_binary_tarball:
-
-Installing |Percona Server| from a Binary Tarball
-===================================================
-
-In |Percona Server| 8.0.20-11 and later, select the **Percona Server for MySQL** 8.0 version number and the type of tarball for your installation. The multiple binary tarballs from earlier versions have been replaced with the following:
-
- 
-.. tabularcolumns:: |p{0.08\linewidth}|p{0.30\linewidth}|p{0.10\linewidth}|p{0.40\linewidth}|
-
-.. list-table::
-   :header-rows: 1
-
-   * - Type
-     - Name
-     - Operating systems
-     - Description
-   * - Full
-     - Percona-Server-<version number>-Linux.x86_64.glibc2.12.tar.gz
-     - Built for CentOS 6
-     - Contains binaries, libraries, test files, and debug symbols
-   * - Minimal
-     - Percona-Server-<version number>-Linux.x86_64.glibc2.12-minimal.tar.gz
-     - Built for CentOS 6
-     - Contains binaries and libraries but does not include test files, or debug symbols
-   * - Full
-     - Percona-Server-<version number>-Linux.x86_64.glibc2.17.tar.gz
-     - Compatible with any supported operating system except for CentOS 6
-     - Contains binaries, libraries, test files, and debug symbols
-   * - Minimal
-     - Percona-Server-<version number>-Linux.x86_64.glibc2.17-minimal.tar.gz
-     - Compatible with any supported operating system except for CentOS 6
-     - Contains binaries and libraries but does not include test files or debug symbols
-
-Implemented in *Percona for MySQL* 8.0.26-16, the following binary tarballs
-are available for the MyRocks ZenFS installation. See :ref:`zenfs` for more information and the installation procedure.
-
-.. tabularcolumns:: |p{0.08\linewidth}|p{0.30\linewidth}|p{0.40\linewidth}|
-
-.. list-table::
-   :header-rows: 1
-
-   * - Type
-     - Name
-     - Description
-   * - Full
-     - Percona-Server-<version number>-Linux.x86_64.glibc2.31-zenfs.tar.gz
-     - Contains the binaries, libraries, test files, and debug symbols
-   * - Minimal
-     - Percona-Server-<version number>-Linux.x86_64.glibc2.31-zenfs-minimal.tar.gz
-     - Contains the binaries and libraries but does not include test files or debug symbols
-
-At this time, you can enable the ZenFS plugin in the following distributions:
-
-.. list-table::
-   :widths: auto
-   :header-rows: 1
-
-   * - Distribution Name
-     - Notes
-   * - Debian 11.1
-     - Able to run the ZenFS plugin
-   * - Ubuntu 20.04.3
-     - Requires the 5.11 HWE kernel patched with the ``allow blk-zoned ioctls without CAPT_SYS_ADMIN`` patch
-
-If you do not enable the ZenFS functionality on Ubuntu 20.04, the binaries with ZenFS support can run on the standard 5.4 kernel. `Other Linux distributions <https://zonedstorage.io/docs/distributions/linux/>`__ are adding support for ZenFS, but Percona does not provide installation packages for those distributions.
-
-In |Percona Server| before 8.0.20-11, multiple tarballs are provided based on the  *OpenSSL* library available in the distribution:
-
- * ssl100 - for *Debian* prior to 9 and *Ubuntu* prior to 14.04 versions (``libssl.so.1.0.0 => /usr/lib/x86_64-linux-gnu/libssl.so.1.0.0``);
- * ssl102 - for *Debian* 9 and *Ubuntu* versions starting from 14.04 (``libssl.so.1.1 => /usr/lib/libssl.sl.1.1``)
- * ssl101 - for *CentOS* 6 and *CentOS* 7 (``libssl.so.10 => /usr/lib64/libssl.so.10``);
- * ssl102 - for *CentOS* 8 and *RedHat* 8  (``libssl.so.1.1 => /usr/lib/libssl.so.1.1.1b``);
-
-You can download the binary tarballs from the ``Linux - Generic`` `section <https://www.percona.com/downloads/Percona-Server-8.0/LATEST/binary/tarball/>`_ on the download page.
-
-Fetch and extract the correct binary tarball. For example for *Debian 10*:
-
-.. code-block:: bash
-
-  $ wget https://downloads.percona.com/downloads/Percona-Server-8.0/Percona-Server-8.0.26-16/binary/tarball/Percona-Server-8.0.26-16-Linux.x86_64.glibc2.12.tar.gz
-
-.. _installing_from_source_tarball:
-
-Installing |Percona Server| from a Source Tarball
-=================================================
-
-Fetch and extract the source tarball. For example: ::
-
-  $ wget https://downloads.percona.com/downloads/Percona-Server-8.0/Percona-Server-8.0.26-16/binary/tarball/Percona-Server-8.0.26-16-Linux.x86_64.glibc2.12.tar.gz
-  $ tar xfz Percona-Server-8.0.26-16-Linux.x86_64.glibc2.12.tar.gz
-
-Next, follow the instructions in :ref:`compile_from_source` below.
-
-.. _source_from_git:
-
-Installing |Percona Server| from the Git Source Tree
-====================================================
-
-Percona uses the `Github <http://github.com/>`_ revision
-control system for development. To build the latest |Percona Server|
-from the source tree you will need ``git`` installed on your system.
-
-You can now fetch the latest |Percona Server| 8.0 sources.
-
-.. code-block:: bash
-
-  $ git clone https://github.com/percona/percona-server.git
-  $ cd percona-server
-  $ git checkout 8.0
-  $ git submodule init
-  $ git submodule update
-
-If you are going to be making changes to |Percona Server| 8.0 and wanting
-to distribute the resulting work, you can generate a new source tarball
-(exactly the same way as we do for release): ::
-
-  $ cmake .
-  $ make dist
-
-Next, follow the instructions in :ref:`compile_from_source` below.
-
-.. _compile_from_source:
-
-Compiling |Percona Server| from Source
-======================================
-
-After either fetching the source repository or extracting a source tarball
-(from Percona or one you generated yourself), you will now need to
-configure and build |Percona Server|.
-
-.. important::
-
-   Make sure that :program:`gcc` installed on your system is at least
-   of a version in the 4.9 release series.
-
-First, run cmake to configure the build. Here you can specify all the normal
-build options as you do for a normal |MySQL| build. Depending on what
-options you wish to compile |Percona Server| with, you may need other
-libraries installed on your system. Here is an example using a
-configure line similar to the options that Percona uses to produce
-binaries: ::
-
-  $ cmake . -DCMAKE_BUILD_TYPE=RelWithDebInfo -DBUILD_CONFIG=mysql_release -DFEATURE_SET=community
-
-Now, compile using make ::
-
-  $ make
-
-Install: ::
-
-  $ make install
-
-|Percona Server| 8.0 will now be installed on your system.
-
-Building |Percona Server| Debian/Ubuntu packages
-================================================
-
-If you wish to build your own Debian/Ubuntu (dpkg) packages of |Percona Server|,
-you first need to start with a source tarball, either from the Percona
-website or by generating your own by following the instructions above(
-:ref:`source_from_git`).
-
-Extract the source tarball: ::
-
-  $ tar xfz Percona-Server-8.0.13-3-Linux.x86_64.ssl102.tar.gz
-  $ cd Percona-Server-8.0.13-3
-
-Put the debian packaging in the directory that Debian expects it to be in: ::
-
-  $ cp -ap build-ps/debian debian
-
-Update the changelog for your distribution (here we update for the unstable
-distribution - sid), setting the version number appropriately. The trailing one
-in the version number is the revision of the Debian packaging. ::
-
-  $ dch -D unstable --force-distribution -v "8.0.13-3-1" "Update to 8.0.13-3"
-
-Build the Debian source package: ::
-
-  $ dpkg-buildpackage -S
-
-Use sbuild to build the binary package in a chroot: ::
-
-  $ sbuild -d sid percona-server-8.0_8.0.13-3-1.dsc
-
-You can give different distribution options to ``dch`` and ``sbuild`` to build binary
-packages for all Debian and Ubuntu releases.
-
-.. note::
-
-  :ref:`pam_plugin` is not built with the server by default. In order to build
-  the |Percona Server| with PAM plugin, additional option
-  :option:`-DWITH_PAM=ON` should be used.
diff --git a/doc/source/installation/apt_repo.rst b/doc/source/installation/apt_repo.rst
deleted file mode 100644
index e15a8d230ad0..000000000000
--- a/doc/source/installation/apt_repo.rst
+++ /dev/null
@@ -1,260 +0,0 @@
-.. _apt_repo:
-
-================================================================================
-Installing |Percona Server| on *Debian* and *Ubuntu*
-================================================================================
-
-Ready-to-use packages are available from the |Percona Server| software
-repositories and the `Percona downloads`_ page.
-
-Specific information on the supported platforms, products, and versions is described in `Percona Software and Platform Lifecycle <https://www.percona.com/services/policies/percona-software-platform-lifecycle#mysql>`_.
-
-What's in each DEB package?
-===========================
-
-.. list-table::
-   :widths: 25 75
-   :header-rows: 1
-
-   * - Package
-     - Contains
-   * - percona-server-server
-     - The database server itself, the ``mysqld`` binary and associated files.
-   * - percona-server-common
-     - The files common to the server and client.
-   * - percona-server-client
-     - The command line client.
-   * - percona-server-dbg
-     - Debug symbols for the server.
-   * - percona-server-test
-     - The database test suite.
-   * - percona-server-source
-     - The server source.
-   * - libperconaserverclient21-dev
-     - Header files needed to compile software to use the client library.
-   * - libperconaserverclient21
-     - The client shared library. The version is incremented when there is an
-       ABI change that requires software using the client library to be
-       recompiled or its source code modified.
-
-.. _apt-install:
-
-Installing |Percona Server| from Percona ``apt`` repository
-===========================================================
-
-1. Install ``GnuPG``, the GNU Privacy Guard:
-
-   .. code-block:: bash
-
-      $ sudo apt install gnupg2 curl
-
-2. Fetch the repository packages from Percona web:
-
-   .. code-block:: bash
-
-      $ wget https://repo.percona.com/apt/percona-release_latest.$(lsb_release -sc)_all.deb
-
-#. Install the downloaded package with :program:`dpkg`. To do that, run the following commands as root or with :program:`sudo`:
-
-   .. code-block:: bash
-
-      $ sudo dpkg -i percona-release_latest.$(lsb_release -sc)_all.deb
-
-#. Once you install this package the Percona repositories should be added. You
-   can check the repository setup in the
-   :file:`/etc/apt/sources.list.d/percona-release.list` file.
-
-#. Enable the repository:
-
-   .. code-block:: bash
-
-     $ sudo percona-release setup ps80
-
-#. After that you can install the server package:
-
-   .. code-block:: bash
-
-      $ sudo apt install percona-server-server
-
-.. note::
-
-   |ps-last| comes with the :ref:`TokuDB storage engine <tokudb_intro>` and :ref:`MyRocks storage engine<myrocks_intro>`. These storage engines are installed as plugin.
-
-   Starting with :ref:`8.0.28-19`, the TokuDB storage engine is no longer supported. We have removed the storage engine from the installation packages and disabled the storage engine in our binary builds. For more information, see :ref:`tokudb_intro`.
-
-   For information on how to install and configure |TokuDB|, refer to the :ref:`tokudb_installation` guide.
-
-   For information on how to install and configure |MyRocks|, refer to the :ref:`myrocks_install` guide.
-
-The |Percona Server| distribution contains several useful User Defined Functions (UDF) from Percona Toolkit. After the installation completes, run the following commands to create these functions:
-
-.. code-block:: bash
-
-    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'"
-
-For more details on the UDFs, see `Percona Toolkit UDFS <https://www.percona.com/doc/percona-server/8.0/management/udf_percona_toolkit.html>`_.
-
-Percona ``apt`` Testing repository
---------------------------------------------------------------------------------
-
-Percona offers pre-release builds from the testing repository. To enable it, run
-|percona-release| with the ``testing`` argument. |tip.run-this.root|.
-
-.. code-block:: bash
-
-   $ sudo percona-release enable ps80 testing
-
-Apt-Pinning the packages
---------------------------------------------------------------------------------
-
-In some cases you might need to "pin" the selected packages to avoid the
-upgrades from the distribution repositories. You'll need to make a new file
-:file:`/etc/apt/preferences.d/00percona.pref` and add the following lines in it:
-::
-
-  Package: *
-  Pin: release o=Percona Development Team
-  Pin-Priority: 1001
-
-For more information about the pinning you can check the official `debian wiki
-<http://wiki.debian.org/AptPreferences>`_.
-
-.. _standalone_deb:
-
-Installing |Percona Server| using downloaded deb packages
-================================================================================
-
-Download the packages of the desired series for your architecture from the
-`Percona downloads`_ page. The easiest way is to download bundle which contains
-all the packages. The following example will download |Percona Server|
-:rn:`8.0.13-3` release packages for |debian-last|:
-
-.. code-block:: bash
-
-   $ wget https://www.percona.com/downloads/Percona-Server-8.0/Percona-Server-8.0.13-3/binary/debian/stretch/x86_64/percona-server-8.0.13-3-r63dafaf-stretch-x86_64-bundle.tar
-
-You should then unpack the bundle to get the packages:
-
- .. code-block:: bash
-
-    $ tar xvf percona-server-8.0.13-3-r63dafaf-stretch-x86_64-bundle.tar
-
-After you unpack the bundle you should see the following packages:
-
-  .. code-block:: bash
-
-     $ ls *.deb
-
-  .. admonition:: Output
-
-     .. code-block:: bash
-
-        libperconaserverclient21-dev_8.0.13-3-1.stretch_amd64.deb
-        libperconaserverclient21_8.0.13-3-1.stretch_amd64.deb
-        percona-server-dbg_8.0.13-3-1.stretch_amd64.deb
-        percona-server-client_8.0.13-3-1.stretch_amd64.deb
-        percona-server-common_8.0.13-3-1.stretch_amd64.deb
-        percona-server-server_8.0.13-3-1.stretch_amd64.deb
-        percona-server-source_8.0.13-3-1.stretch_amd64.deb
-        percona-server-test_8.0.13-3-1.stretch_amd64.deb
-        percona-server-tokudb_8.0.13-3-1.stretch_amd64.deb
-
-
-
-Now, you can install |Percona Server| using |dpkg|. |tip.run-this.root|
-
-  .. code-block:: bash
-
-    $ sudo dpkg -i *.deb
-
-This will install all the packages from the bundle. Another option is to
-download/specify only the packages you need for running |Percona Server|
-installation (``libperconaserverclient21_8.0.13-3-1.stretch_amd64.deb``,
-``percona-server-client_8.0.13-3-1.stretch_amd64.deb``,
-``percona-server-common_8.0.13-3-1.stretch_amd64.deb``, and
-``percona-server-server_8.0.13-3-1.stretch_amd64.deb``. Optionally, you can install
-``percona-server-tokudb_8.0.13-3-1.stretch_amd64.deb`` if you want the |TokuDB|
-storage engine).
-
-.. note::
-
-   |Percona Server| |version| comes with the :ref:`TokuDB storage engine
-   <tokudb_intro>`. You can find more information on how to install and enable
-   the |TokuDB| storage in the :ref:`tokudb_installation` guide.
-
-   Starting with :ref:`8.0.28-19`, the TokuDB storage engine is no longer supported. We have removed the storage engine from the installation packages and disabled the storage engine in our binary builds. For more information, see :ref:`tokudb_intro`.
-
-.. warning::
-
-   When installing packages manually like this, you'll need to make sure to
-   resolve all the dependencies and install missing packages yourself. Following
-   packages will need to be installed before you can manually install Percona
-   Server: ``mysql-common``, ``libjemalloc1``, ``libaio1`` and ``libmecab2``
-
-
-Running |Percona Server|
-========================
-
-|Percona Server| stores the data files in :file:`/var/lib/mysql/` by
-default. You can find the configuration file that is used to manage |Percona
-Server| in :file:`/etc/mysql/my.cnf`.
-
-.. note::
-
-   *Debian* and *Ubuntu* installation doesn't automatically create a special
-    ``debian-sys-maint`` user which can be used by the control scripts to
-    control the |Percona Server| ``mysqld`` and ``mysqld_safe`` services like it
-    was the case with previous |Percona Server| versions. If you still require
-    this user you'll need to create it manually.
-
-|tip.run-all.root|
-
-1. Starting the service
-
-   |Percona Server| is started automatically after it gets installed unless it
-   encounters errors during the installation process. You can also manually
-   start it by running: :bash:`service mysql start`
-
-#. Confirming that service is running. You can check the service status by
-   running: :bash:`service mysql status`
-
-#. Stopping the service
-
-   You can stop the service by running: :bash:`service mysql stop`
-
-#. Restarting the service. :bash:`service mysql restart`
-
-.. note::
-
-   |debian-last| and |ubuntu-lts| come with `systemd
-   <http://freedesktop.org/wiki/Software/systemd/>`_ as the default system and
-   service manager. You can invoke all the above commands with ``systemctl``
-   instead of ``service``. Currently both are supported.
-
-Working with AppArmor
-======================
-
-For information on AppArmor, see :ref:`enable-apparmor`.
-
-Uninstalling |Percona Server|
-=============================
-
-To uninstall |Percona Server| you'll need to remove all the installed
-packages. Removing packages with `apt remove` does not remove the
-configuration and data files. Removing the packages with `apt purge` does remove the packages with configuration files and data files (all
-the databases). Depending on your needs you can choose which command better
-suits you.
-
-1. Stop the |Percona Server| service: :bash:`service mysql stop`
-2. Remove the packages
-
-   a) Remove the packages. This will leave the data files (databases, tables, logs, configuration, etc.) behind. In case you don't need them you'll need to remove them manually: :bash:`apt remove percona-server*`
-
-   b) Purge the packages. **NOTE**: This command removes all the packages and delete all the data files (databases, tables, logs, and so on.): :bash:`apt purge percona-server*`
-
-
-.. include:: ../.res/replace.txt
-.. include:: ../.res/replace.program.txt
-.. include:: ../.res/url.txt
diff --git a/doc/source/installation/docker.rst b/doc/source/installation/docker.rst
deleted file mode 100644
index 4fa0c0ce541a..000000000000
--- a/doc/source/installation/docker.rst
+++ /dev/null
@@ -1,307 +0,0 @@
-.. _docker:
-
-================================================
- Running *Percona Server for MySQL* in a Docker Container
-================================================
-
-Docker images of *Percona Server for MySQL* are hosted publicly on Docker Hub at
-https://hub.docker.com/r/percona/percona-server/.
-
-For more information about using Docker, see the `Docker Docs`_.
-
-.. _`Docker Docs`: https://docs.docker.com/
-
-.. note::
-
-   Make sure that you are using the latest version of Docker.  The
-   ones provided via ``apt`` and ``yum`` may be outdated and cause
-   errors.
-
-   By default, Docker will pull the image from Docker Hub if it is not
-   available locally.
-
-
-Using the *Percona Server for MySQL* Images
-=================================
-
-The following procedure describes how to run and access Percona Server 8.0
-using Docker.
-
-Starting an Instance of *Percona Server for MySQL* in a Container
--------------------------------------------------------
-
-To start a container named ``ps`` running the latest version of
-*Percona Server for MySQL* 8.0, with the root password set to ``root``::
-
- [root@docker-host] $ docker run -d \
-   --name ps \
-   -e MYSQL_ROOT_PASSWORD=root \
-   percona/percona-server:8.0
-
-.. important:: ``root`` is not a secure password.
-
-.. note::
-
-    The `docker stop` command sends a `TERM` signal. Docker waits 10 seconds
-    and sends a `KILL` signal. Very large instances cannot dump the data from
-    memory to disk in 10 seconds. If you plan to run a very large instance, add
-    the following option to the `docker run` command.
-
-    --stop-timeout 600
-
-Accessing the Percona Server Container
---------------------------------------
-
-To access the shell in the container::
-
- [root@docker-host] $ docker exec -it ps /bin/bash
-
-From the shell, you can view the error log::
-
- [mysql@ps] $ more /var/log/mysql/error.log
- 2017-08-29T04:20:22.190474Z 0 [Warning] 'NO_ZERO_DATE', 'NO_ZERO_IN_DATE' and 'ERROR_FOR_DIVISION_BY_ZERO' sql modes should be used with strict mode. They will be merged with strict mode in a future release.
- 2017-08-29T04:20:22.190520Z 0 [Warning] 'NO_AUTO_CREATE_USER' sql mode was not set.
- ...
-
-You can also run the MySQL command-line client
-to access the database directly::
-
- [mysql@ps] $ mysql -uroot -proot
- mysql: [Warning] Using a password on the command line interface can be insecure.
- Welcome to the MySQL monitor.  Commands end with ; or \g.
- Your MySQL connection id is 4
- Server version: 8.0.13-3 Percona Server (GPL), Release '17', Revision 'e19a6b7b73f'
-
- Copyright (c) 2009-2017 Percona LLC and/or its affiliates
- Copyright (c) 2000, 2017, Oracle and/or its affiliates. All rights reserved.
-
- Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners.
-
- Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.
-
- mysql>
-
-Accessing *Percona Server for MySQL* from Application in Another Container
-----------------------------------------------------------------
-
-The image exposes the standard MySQL port 3306,
-so container linking makes Percona Server instance available
-from other containers.
-To link a container running your application
-(in this case, from image named ``app/image``)
-with the Percona Server container,
-run it with the following command::
-
- [root@docker-host] $ docker run -d \
-   --name app \
-   --link ps \
-   app/image:latest
-
-This application container will be able to access the Percona Server container
-via port 3306.
-
-Environment Variables
-=====================
-
-When running a Docker container with Percona Server,
-you can adjust the configuration of the instance
-by passing one or more environment variables with the ``docker run`` command.
-
-.. note:: These variables will not have any effect
-   if you start the container with a data directory
-   that already contains a database:
-   any pre-existing database will always remain untouched on container startup.
-
-The variables are optional,
-except that you must specify at least one of the following:
-
-* :ref:`MYSQL_ALLOW_EMPTY_PASSWORD`: least secure, use only for testing.
-
-* :ref:`MYSQL_ROOT_PASSWORD`: more secure,
-  but setting the password on the command line is not recommended
-  for sensitive production setups.
-
-* :ref:`MYSQL_RANDOM_ROOT_PASSWORD`: most secure,
-  recommended for production.
-
-  .. note:: To further secure your instance,
-     use the :ref:`MYSQL_ONETIME_PASSWORD` variable
-     if you are running version 5.6 or later.
-
-.. _MYSQL_ALLOW_EMPTY_PASSWORD:
-
-.. rubric:: ``MYSQL_ALLOW_EMPTY_PASSWORD`` 
-
-  Specifies whether to allow the container
-  to be started with a blank password for the MySQL root user.
-  Disabled by default.
-  To enable, set ``MYSQL_ALLOW_EMPTY_PASSWORD=yes``.
-
-  .. note:: Allowing empty root password is not recommended for production,
-     because anyone will have full superuser access to the database.
-
-.. _MYSQL_DATABASE:
-
-.. rubric:: ``MYSQL_DATABASE``
-
-  Specifies the name of the database to be created when running the container.
-  To create a user with full access to this database (``GRANT ALL``),
-  set the :ref:`MYSQL_USER` and :ref:`MYSQL_PASSWORD` variables.
-
-.. _MYSQL_ONETIME_PASSWORD:
-
-.. rubric:: ``MYSQL_ONETIME_PASSWORD``
-
-  Specifies whether the password for the MySQL root user
-  should be set as expired.
-  Disabled by default.
-  If enabled using ``MYSQL_ONETIME_PASSWORD=yes``,
-  the MySQL root password must be changed before using it to log in.
-
-.. _MYSQL_PASSWORD:
-
-.. rubric:: ``MYSQL_PASSWORD``
-
-  Specifies the password for the user with full access to the database
-  specified by the :ref:`MYSQL_DATABASE` variable.
-  Setting the :ref:`MYSQL_USER` variable is also required.
-
-.. _MYSQL_RANDOM_ROOT_PASSWORD:
-
-.. rubric:: ``MYSQL_RANDOM_ROOT_PASSWORD``
-
-  Specifies whether a random password for the MySQL root user
-  should be generated.
-  Disabled by default.
-  To enable, set ``MYSQL_RANDOM_ROOT_PASSWORD=yes``.
-
-  The password will be printed to ``stdout`` in the container,
-  and it can be viewed using the ``docker logs`` command.
-
-.. _MYSQL_ROOT_PASSWORD:
-
-.. rubric:: ``MYSQL_ROOT_PASSWORD``
-
-  Specifies the password for the MySQL root user.
-
-  .. note:: Setting the MySQL root password on the command line is insecure.
-     It is recommended to set a random password
-     using the :ref:`MYSQL_RANDOM_ROOT_PASSWORD` variable.
-
-.. _MYSQL_ROOT_PASSWORD_FILE:
-
-.. rubric:: ``MYSQL_ROOT_PASSWORD_FILE``
-
-  Specifies a file that will be read for the root user account.
-  This can be a mounted file when you run your container. This
-  can also be used in the scope of the Docker Secrets (Swarm mode)
-  functionality.
-
-.. _MYSQL_USER:
-
-.. rubric:: ``MYSQL_USER``
-
-  Specifies the name for the user with full access to the database
-  specified by the :ref:`MYSQL_DATABASE` variable.
-  Setting the :ref:`MYSQL_PASSWORD` variable is also required.
-
-.. _INIT_TOKUDB:
-
-.. rubric:: ``INIT_TOKUDB``
-
-  Specifies whether to allow the container to be started with
-  enabled TokuDB engine. Disabled by default. To enable, set
-  ``INIT_TOKUDB=yes``.
-
-.. note:: 
-
-   Starting with :ref:`8.0.28-19`, the TokuDB storage engine is no longer supported. We have removed the storage engine from the installation packages and disabled the storage engine in our binary builds. For more information, see :ref:`tokudb_intro`.
-
-.. _INIT_ROCKSDB:
-
-.. rubric:: ``INIT_ROCKSDB``
-
-  Specifies whether to allow the container to be started with
-  enabled RocksDB engine. Disabled by default. To enable, set
-  ``INIT_ROCKSDB=yes``.
-
-Storing Data
-============
-
-There are two ways to store data used by applications
-that run in Docker containers:
-
-* Let Docker manage the storage of your data
-  by writing the database files to disk on the host system
-  using its own internal volume management.
-
-* Create a data directory on the host system
-  (outside the container on high performance storage)
-  and mount it to a directory visible from inside the container.
-  This places the database files in a known location on the host system,
-  and makes it easy for tools and applications on the host system
-  to access the files.
-  The user should make sure that the directory exists,
-  and that permissions and other security mechanisms on the host system
-  are set up correctly.
-
-For example, if you create a data directory on a suitable volume
-on your host system named ``/local/datadir``,
-you run the container with the following command::
-
- [root@docker-host] $ docker run -d \
-   --name ps \
-   -e MYSQL_ROOT_PASSWORD=root \
-   -v /local/datadir:/var/lib/mysql \
-   percona/percona-server:8.0
-
-The ``-v /local/datadir:/var/lib/mysql`` option
-mounts the ``/local/datadir`` directory on the host
-to ``/var/lib/mysql`` in the container,
-which is the default data directory used by *Percona Server for MySQL*.
-
-.. note:: If the data directory contains subdirectories, files, or data, do not add :ref:`MYSQL_ROOT_PASSWORD` to the ``docker run`` command.
-
-.. note:: If you have SELinux enabled,
-   assign the relevant policy type to the new data directory,
-   so that the container will be allowed to access it::
-
-    [root@docker-host] $ chcon -Rt svirt_sandbox_file_t /local/datadir
-
-Port Forwarding
-===============
-
-Docker allows mapping ports on the container to ports on the host system
-using the ``-p`` option.
-If you run the container with this option,
-you can connect to the database by connecting your client
-to a port on the host machine.
-This can greatly simplify consolidating many instances to a single host.
-
-To map the standard MySQL port 3306 to port 6603 on the host::
-
-  [root@docker-host] $ docker run -d \
-   --name ps \
-   -e MYSQL_ROOT_PASSWORD=root \
-   -p 6603:3306 \
-   percona/percona-server:8.0
-
-Passing Options to *Percona Server for MySQL*
-===================================
-
-You can pass options to *Percona Server for MySQL* when running the container
-by appending them to the ``docker run`` command.
-For example, to start run *Percona Server for MySQL* with UTF-8
-as the default setting for character set
-and collation for all databases::
-
-  [root@docker-host] $ docker run -d \
-   --name ps \
-   -e MYSQL_ROOT_PASSWORD=root \
-   percona/percona-server:8.0 \
-   --character-set-server=utf8 \
-   --collation-server=utf8_general_ci
-
-.. seealso::
-
-    `Docker Hub MySQL <https://hub.docker.com/_/mysql>`__
diff --git a/doc/source/installation/post-installation.rst b/doc/source/installation/post-installation.rst
deleted file mode 100644
index 5f5d443f4027..000000000000
--- a/doc/source/installation/post-installation.rst
+++ /dev/null
@@ -1,230 +0,0 @@
-.. _post-installation:
-
-===============================================================================
-Post-Installation
-===============================================================================
-
-After you have installed |Percona Server|, you may need to do the following:
-
-.. tabularcolumns:: |p{5cm}|p{5cm}|
-
-.. list-table::
-   :header-rows: 1
-
-   * - Task
-     - Description
-   * - Initialize the data directory
-     - The source distribution or generic binary distribution installation does not automatically initialize the data directory
-   * - Update the ``root`` password
-     - The CentOS/RedHat installations set up a temporary ``root`` password. 
-   * - Start the server
-     - Common method to start the server and check the status
-   * - Configure the server to start on startup
-     - Use ``systemd`` to start the server automatically
-   * - Testing the server
-     - Verify the server returns information
-   * - Enable time zone recognition
-     - Populate the time zone tables
-
-Initializing the Data Directory
--------------------------------
-
-If you install the server using either the source distribution or generic binary distribution files, the data directory is not initialized, and you must run the initialization process after installation. 
-
-Run `mysqld` with the `--initialize <https://dev.mysql.com/doc/refman/8.0/en/server-options.html#option_mysqld_initialize>`_ option or the `initialize-insecure <https://dev.mysql.com/doc/refman/8.0/en/server-options.html#option_mysqld_initialize-insecure>`_ option.
-
-Executing `mysqld` with either option does the following:
-
-* Verifies the existence of the data directory
-* Initializes the system tablespace and related structures
-* Creates system tables including grant tables, time zone tables, and server-side help tables
-* Creates ``root@localhost``
-
-You should run the following steps with the ``mysql`` login. 
-
-1. Navigate to the MySQL directory. The example uses the default location.
-
-.. code-block:: bash
-
-    $ cd /usr/local/mysql
-
-2. Create a directory for the MySQL files. The `secure_file_priv <https://dev.mysql.com/doc/refman/8.0/en/server-system-variables.html#sysvar_secure_file_priv>`_ uses the directory path as a value.
-
-.. code-block:: bash
-
-    $ mkdir mydata
-
-The ``mysql`` user account should have the ``drwxr-x---`` permissions.
-Four sections define the permissions; file or directory, User, Group, and Others. 
-
-The first character designates if the permissions are for a file or directory. The first character is ``d`` for a directory. 
-
-The rest of the sections are specified in three-character sets. 
-
-.. tabularcolumns:: |p{5cm}|p{5cm}|p{5cm}|p{5cm}|
-
-.. list-table::
-   :header-rows: 1
-
-   * - Permission 
-     - User 
-     - Group 
-     - Other 
-   * - Read
-     - Yes
-     - Yes
-     - No 
-   * - Write
-     - Yes
-     - No
-     - No
-   * - Execute
-     - Yes
-     - Yes
-     - No
-
-
-3. Run the command to initialize the data directory. 
-
-.. code-block:: bash
-
-    $ bin/mysqld --initialize
-    
-
-Secure the Installation
------------------------
-
-The `mysql_secure_installation
-<https://dev.mysql.com/doc/refman/8.0/en/mysql-secure-installation.html>`_
-script improves the security of the installation.
-
-Running the script does the following:
-
-* Changes the ``root`` password
-* Disallows remote login for ``root`` accounts
-* Removes anonymous users
-* Removes the ``test`` database
-* Reloads the privilege tables
-
-The following statement runs the script:
-
-.. code-block:: bash
-
-    $ mysql_secure_installation
-
-Testing the Server
----------------------------------------------
-
-After a generic binary installation, the server starts. The following command checks the server status:
-
-.. code-block:: bash
-
-    $ sudo service mysql status
-    
-Access the server with the following command:
-
-.. code-block:: bash
-
-    $ mysql -u root -p
-    
-Configuring the Server to Start at Startup
-------------------------------------------------------
-
-You can manage the server with systemd. If you have installed the server from a generic binary distribution on an operating system that uses systemd, you can manually configure systemd support. 
-
-The following commands start, check the status, and stop the server:
-
-.. code-block:: bash
-
-   $ systemctl start mysql
-   $ systemctl status mysql
-   $ systemctl stop mysql
-
-Enabling the server to start at startup, run the following:
-
-.. code-block:: bash
-
-   systemctl enable mysql
-
-Testing the Server
-------------------
-
-After you have initialized the data directory, and the server is started, you can run tests on the server. 
-
-This section assumes you have used the default installation settings. If you have modified the installation, navigate to the installation location. You can also add the location by `Setting the Environment Variables <https://dev.mysql.com/doc/refman/8.0/en/setting-environment-variables.html>`_.
-
-You can use the `mysqladmin <https://dev.mysql.com/doc/refman/8.0/en/mysqladmin.html>`_ client to access the server. 
-
-If you have issues connecting to the server, you should use the ``root`` user and the root account password.
-
-.. code-block:: bash
-
-    $ sudo mysqladmin -u root -p version
-    Enter password: 
-
-    mysql Ver 8.0.19-10 for debian-linux-gnu on x86_64 (Percona Server (GPL), Release '10', Revision 'f446c04')
-    ...
-    Server version      8.0.19-10
-    Protocol version    10
-    Connection          Localhost via UNIX socket
-    UNIX socket         /var/run/mysqld/mysqld.sock
-    Uptime:             4 hours 58 min 10 section
-
-    Threads:    2 Questions:    16 Slow queries: 0 Opens: 139 Flush tables: 3
-    Open tables: 59  Queries per second avg: 0.0000 
-
-Use `mysqlshow <https://dev.mysql.com/doc/refman/8.0/en/mysqlshow.html>`_ to display database and table information.
-
-.. code-block:: bash
-
-    $ sudo mysqlshow -u root -p 
-    Enter password:
-
-    +---------------------+
-    |      Databases      |
-    +=====================+
-    | information_schema  |
-    +---------------------+
-    | mysql               |
-    +---------------------+
-    | performance_schema  |
-    +---------------------+
-    | sys                 |
-    +---------------------+
-
-
-Populating the Time Zone Tables
---------------------------------
-
-The time zone system tables are the following:
-
-* ``time_zone``
-* ``time_zone_leap_second``
-* ``time_zone_name``
-* ``time_zone_transition``
-* ``time_zone_transition_type``
-
-If you install the server using either the source distribution or the
-generic binary distribution files, the installation creates the time zone
-tables, but the tables are not populated.
-
-The `mysql_tzinfo_to_sql
-<https://dev.mysql.com/doc/refman/8.0/en/mysql-tzinfo-to-sql.html>`_ program
-populates the tables from the ``zoneinfo`` directory data available in Linux.
-
-A common method to populate the tables is to add the zoneinfo directory path
-to ``mysql_tzinfo_to_sql`` and then send the output into
-the `mysql system schema <https://dev.mysql.com/doc/refman/8.0/en/system-schema.html>`__.
-
-The example assumes you are running the command with the ``root`` account.
-The account must have the privileges for modifying the ``mysql``
-system schema.
-
-.. code-block:: bash
-
-    $ mysql_tzinfo_to_sql /usr/share/zoneinfo | mysql -u root -p -D mysql
-
-
-
-
-
diff --git a/doc/source/installation/yum_repo.rst b/doc/source/installation/yum_repo.rst
deleted file mode 100644
index 66f4eaf91856..000000000000
--- a/doc/source/installation/yum_repo.rst
+++ /dev/null
@@ -1,267 +0,0 @@
-.. _yum_repo:
-
-====================================================================
- Installing |Percona Server| on Red Hat Enterprise Linux and CentOS
-====================================================================
-
-.. package name: percona-server-server-8.0.13-3.1.el7.x86_64.rpm
-
-Ready-to-use packages are available from the |Percona Server| software
-repositories and the `download page
-<http://www.percona.com/downloads/Percona-Server-8.0/>`_. The
-|Percona| :program:`yum` repository supports popular *RPM*-based
-operating systems. The easiest way to install the *Percona Yum* repository is to install an *RPM*
-that configures :program:`yum` and installs the `Percona GPG key
-<https://www.percona.com/downloads/RPM-GPG-KEY-percona>`_.
-
-Specific information on the supported platforms, products, and versions are described in `Percona Software and Platform Lifecycle <https://www.percona.com/services/policies/percona-software-platform-lifecycle#mysql>`_.
-
-|Percona Server| is certified for Red Hat Enterprise Linux 8. This certification is based on common and secure best practices, and successful interoperability with the operating system. Percona Server is listed in the `Red Hat Ecosystem Catalog <https://catalog.redhat.com/software/applications/detail/5869161>`_. 
-
-
-.. note:: 
-
-    The RPM packages for Red Hat Enterprise Linux 7 (and compatible derivatives)  do not support TLSv1.3, as it requires OpenSSL 1.1.1, which is currently not available on this platform. 
-  
-
-What's in each RPM package?
-===========================
-
-Each of the |Percona Server| RPM packages have a particular purpose.
-
-.. list-table::
-   :widths: 25 75
-   :header-rows: 1
-
-   * - Package
-     - Contains
-   * - percona-server-server
-     - Server itself (the ``mysqld`` binary)
-   * - percona-server-debuginfo
-     - Debug symbols for the server
-   * - percona-server-client
-     - Command line client
-   * - percona-server-devel
-     - Header files needed to compile software using the client library.
-   * - percona-server-shared
-     - Client shared library.
-   * - percona-server-shared-compat
-     - Shared libraries for software compiled against old versions of
-       the client library. The following libraries are included in
-       this package: ``libmysqlclient.so.12``,
-       ``libmysqlclient.so.14``, ``libmysqlclient.so.15``,
-       ``libmysqlclient.so.16``, and ``libmysqlclient.so.18``.
-   * - percona-server-test
-     - Includes the test suite for |Percona Server|.
-
-Installing |Percona Server| from Percona ``yum`` repository
-===========================================================
-
-You can install Percona yum repository by running the following commands as a ``root`` user or with sudo.
-
-1. Install the Percona repository
-
-   .. code-block:: bash
-
-      $ sudo yum install https://repo.percona.com/yum/percona-release-latest.noarch.rpm
-
-   You should see an output that the files are being downloaded, like the following:
-
-   .. code-block:: bash
-
-      percona-release-latest.noarch-rpm               36 kB/s | 19 kb 00:00
-      =====================================================================
-        Package         Architecture      Version    Repository    Size
-      =====================================================================
-      Installing:
-         percona release    noarch         1.0-25     @commandline  19k
-      ...
-
-#. Enable the repository:
-
-   .. code-block:: bash
-
-      $ sudo percona-release setup ps80
-      On RedHat 8 systems it is needed to disable dnf mysql module to install Percona-Server
-      Do you want to disable it? [y/N] y
-      ...
-
-#. Install the packages
-
-   .. code-block:: bash
-
-      $ sudo yum install percona-server-server
-
-.. note::
-
-   |Percona Server| 8.0 also provides the :ref:`TokuDB storage engine
-   <tokudb_intro>` and :ref:`MyRocks <myrocks_intro>` storage engines which can
-   be installed as plugins. 
-
-   Starting with :ref:`8.0.28-19`, the TokuDB storage engine is no longer supported. We have removed the storage engine from the installation packages and disabled the storage engine in our binary builds. For more information, see :ref:`tokudb_intro`.
-
-   For more information on how to install and enable the |TokuDB| storage review the :ref:`tokudb_installation` document. 
-   For information on how to install and enable |MyRocks| review the
-   section :ref:`myrocks_install`.
-
-Percona `yum` Testing repository
---------------------------------------------------------------------------------
-
-Percona offers pre-release builds from our testing repository. To
-subscribe to the testing repository, you enable the testing
-repository in :file:`/etc/yum.repos.d/percona-release.repo`. To do so,
-set both ``percona-testing-$basearch`` and ``percona-testing-noarch``
-to ``enabled = 1`` (Note that there are three sections in this file:
-release, testing and experimental - in this case it is the second
-section that requires updating). 
-
-.. note:: 
-   
-   You must install the Percona repository first if the installation has not been done already.
-
-
-.. _standalone_rpm:
-
-Installing |Percona Server| using downloaded rpm packages
-================================================================================
-
-1. Download the packages of the desired series for your architecture from the
-   `download page <http://www.percona.com/downloads/Percona-Server-8.0/>`_. The
-   easiest way is to download bundle which contains all the packages. Following
-   example will download |Percona Server| 8.0.21-12 release packages for *RHEL* 8. 
-
-   .. code-block:: bash
-
-      $ wget https://www.percona.com/downloads/Percona-Server-8.0/Percona-Server-8.0.21-12/binary/redhat/8/x86_64/Percona-Server-8.0.21-12-r7ddfdfe-el8-x86_64-bundle.tar
-
-2. Unpack the bundle to get the packages: :bash:`tar xvf Percona-Server-8.0.21-12-r7ddfdfe-el8-x86_64-bundle.tar`
-
-3. To view a list of packages, run the following command:
-
-   .. code-block:: bash
-
-      $ ls *.rpm
-
-      percona-mysql-router-8.0.21-12.2.el8.x86_64.rpm
-      percona-mysql-router-debuginfo-8.0.21-12.2.el8.x86_64.rpm
-      percona-server-client-8.0.21-12.2.el8.x86_64.rpm
-      percona-server-client-debuginfo-8.0.21-12.2.el8.x86_64.rpm
-      percona-server-debuginfo-8.0.21-12.2.el8.x86_64.rpm
-      percona-server-debugsource-8.0.21-12.2.el8.x86_64.rpm
-      percona-server-devel-8.0.21-12.2.el8.x86_64.rpm
-      percona-server-rocksdb-8.0.21-12.2.el8.x86_64.rpm
-      percona-server-rocksdb-debuginfo-8.0.21-12.2.el8.x86_64.rpm
-      percona-server-server-8.0.21-12.2.el8.x86_64.rpm
-      percona-server-server-debuginfo-8.0.21-12.2.el8.x86_64.rpm
-      percona- server-shared-8.0.21-12.2.el8.x86_64.rpm
-      percona-server-shared-compat-8.0.21-12.2.el8.x86_64.rpm
-      percona-server-shared-debuginfo-8.0.21-12.2.el8.x86_64.rpm
-      percona-server-test-8.0.21-12.2.el8.x86_64.rpm
-      percona-server-test-debuginfo-8.0.21-12.2.el8.x86_64.rpm
-      percona-server-tokudb-8.0.21-12.2.el8.x86_64.rpm
-
-4. Install ``jemalloc`` with the following command, if needed:
-
-   .. code-block:: bash
-
-       wget https://repo.percona.com/yum/release/8/RPMS/x86_64/jemalloc-3.6.0-1.el8.x86_64.rpm
-
-5.  For a *RHEL* distribution and derivatives package installation, |Percona Server| requires the mysql module to be disabled before installing the packages: 
-
-    .. code-block:: bash
-
-        sudo yum module disable mysql 
-
-6. Install all the packages (for debugging, testing, etc.) with the following command:
-
-   .. code-block:: bash
-
-      $ sudo rpm -ivh *.rpm
-
-.. note::
-
-   When installing packages manually, you must make sure to
-   resolve all dependencies and install any missing packages yourself.
-
-Running |Percona Server|
-========================
-
-|Percona Server| stores the data files in :file:`/var/lib/mysql/` by
-default. The configuration file used to manage |Percona
-Server| is the :file:`/etc/my.cnf`.
-
-The following commands start, provide the server status, stop the server, and restart the server.
-
-.. note::
-
-   The *RHEL* distributions and derivatives come with `systemd
-   <http://freedesktop.org/wiki/Software/systemd/>`_ as the default
-   system and service manager so you can invoke all of the commands
-   with ``sytemctl`` instead of ``service``. Currently, both options are
-   supported.
-
-* |Percona Server| is not started automatically on the *RHEL* distributions and derivatives after installation. Start the server with the following command:
-
-   .. code-block:: bash
-
-      $ sudo service mysql start
-
-* Review the service status with the following command:
-
-   .. code-block:: bash
-
-      $ sudo service mysql status
-
-* Stop the service with the following command:
-
-   .. code-block:: bash
-
-      $ sudo service mysql stop
-
-* Restart the service with the following command:
-
-   .. code-block:: bash
-
-      $ sudo service mysql restart
-
-
-
-SELinux and security considerations
-===============================================
-
-For information on working with SELinux, see :ref:`selinux`.
-
-The *RHEL* 8 distributions and derivatives have added `system-wide cryptographic policies component <https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/security_hardening/using-the-system-wide-cryptographic-policies_security-hardening>`__. This component allows the configuration of cryptographic subsystems. 
-
-Uninstalling |Percona Server|
-=============================
-
-To completely uninstall |Percona Server|, remove all the installed packages and data files.
-
-1.  Stop the |Percona Server| service:
-
-    .. code-block:: bash
-
-        $ sudo service mysql stop
-        
-#. Remove the packages:
-
-   .. code-block:: bash
-
-      $ sudo yum remove percona-server*
-
-#. Remove the data and configuration files:
-
-.. warning::
-
-    This step removes all the packages and deletes all the data files (databases,
-    tables, logs, etc.). Take a backup before doing this in case you need the data.
-
-
-   .. code-block:: bash
-
-      $ rm -rf /var/lib/mysql
-      $ rm -f /etc/my.cnf
-
-
-
diff --git a/doc/source/management/audit_log_plugin.rst b/doc/source/management/audit_log_plugin.rst
deleted file mode 100644
index 29429772b917..000000000000
--- a/doc/source/management/audit_log_plugin.rst
+++ /dev/null
@@ -1,1043 +0,0 @@
-.. _audit_log_plugin:
-
-================================================================================
- Audit Log Plugin
-================================================================================
-
-Percona Audit Log Plugin provides monitoring and logging of connection and query
-activity that were performed on specific server. Information about the activity
-is stored in a log file. This
-implementation is alternative to the `MySQL Enterprise Audit Log Plugin
-<https://dev.mysql.com/doc/refman/8.0/en/audit-log.html>`_
-
-Audit logging documents the database usage. You can use the log for troubleshooting. 
-
-* **Audit** - Audit event indicates that audit logging started or finished. ``NAME`` field will be ``Audit`` when logging started and ``NoAudit`` when logging finished. Audit record also includes server version and command-line arguments.
-
-Example of the Audit event: :: 
-
- <AUDIT_RECORD
-  "NAME"="Audit"
-  "RECORD"="1_2014-04-29T09:29:40"
-  "TIMESTAMP"="2014-04-29T09:29:40 UTC"
-  "MYSQL_VERSION"="5.6.17-65.0-655.trusty"
-  "STARTUP_OPTIONS"="--basedir=/usr --datadir=/var/lib/mysql --plugin-dir=/usr/lib/mysql/plugin --user=mysql --log-error=/var/log/mysql/error.log --pid-file=/var/run/mysqld/mysqld.pid --socket=/var/run/mysqld/mysqld.sock --port=3306"
-  "OS_VERSION"="x86_64-debian-linux-gnu",
-  />
-
-* **Connect**/**Disconnect** - Connect record event will have ``NAME`` field ``Connect`` when user logged in or login failed, or ``Quit`` when connection is closed. Additional fields for this event are ``CONNECTION_ID``, ``STATUS``, ``USER``, ``PRIV_USER``, ``OS_LOGIN``, ``PROXY_USER``, ``HOST``, and ``IP``. ``STATUS`` will be  ``0`` for successful logins and non-zero for failed logins.
-
-Example of the Disconnect event: :: 
-
- <AUDIT_RECORD
-  "NAME"="Quit"
-  "RECORD"="24_2014-04-29T09:29:40"
-  "TIMESTAMP"="2014-04-29T10:20:13 UTC"
-  "CONNECTION_ID"="49"
-  "STATUS"="0"
-  "USER"=""
-  "PRIV_USER"=""
-  "OS_LOGIN"=""
-  "PROXY_USER"=""
-  "HOST"=""
-  "IP"=""
-  "DB"=""
-  />
-
-* **Query** - Additional fields for this event are: ``COMMAND_CLASS`` (values come from the ``com_status_vars`` array in the :file:`sql/mysqld.cc`` file in a MySQL source distribution. Examples are ``select``, ``alter_table``, ``create_table``, etc.), ``CONNECTION_ID``, ``STATUS`` (indicates error when non-zero), ``SQLTEXT`` (text of SQL-statement), ``USER``, ``HOST``, ``OS_USER``, ``IP``. Possible values for the ``NAME`` name field for this event are ``Query``, ``Prepare``, ``Execute``, ``Change user``, etc..
-
-.. note::
-    The ``statement/sql/%``  populates the audit log command_class field. For example, the ``SELECT name FROM performance_schema.setup_instruments WHERE name LIKE "statement/sql/%"`` query.
-    
-    The %statement/com%`` entry populates the audit log command_class field as lowercase text. For example, the ``SELECT name FROM performance_schema.setup_instruments WHERE name LIKE '%statement/com%'`` query. If you run a 'ping' command, then the command_class field is 'ping', and for 'Init DB', the command_class field is 'init db'.
-
-Example of the Query event: :: 
-
- <AUDIT_RECORD
-  "NAME"="Query"
-  "RECORD"="23_2014-04-29T09:29:40"
-  "TIMESTAMP"="2014-04-29T10:20:10 UTC"
-  "COMMAND_CLASS"="select"
-  "CONNECTION_ID"="49"
-  "STATUS"="0"
-  "SQLTEXT"="SELECT * from mysql.user"
-  "USER"="root[root] @ localhost []"
-  "HOST"="localhost"
-  "OS_USER"=""
-  "IP"=""
-  />
-
-Installation
-============
-
-The audit Log plugin is installed, but, by default, is not enabled when you install *Percona Server for MySQL*. To check if the plugin is enabled run the following commands:
-
-.. sourcecode:: mysql
-
-    mysql> SELECT * FROM information_schema.PLUGINS WHERE PLUGIN_NAME LIKE '%audit%';
-    Empty set (0.00 sec)
-
-    mysql> SHOW variables LIKE 'audit%';
-    Empty set (0.01 sec)
-
-    mysql> SHOW variables LIKE 'plugin%';
-    +---------------+------------------------+
-    | Variable_name | Value                  |
-    +---------------+------------------------+
-    | plugin_dir    | /usr/lib/mysql/plugin/ |
-    +---------------+------------------------+
-    1 row in set (0.00 sec)
-
-.. note::
-
-    The location of the MySQL plugin directory depends on the operating system and may be different on your system. 
-
-The following command enables the plugin: 
-
-.. code-block:: mysql
-
-   mysql> INSTALL PLUGIN audit_log SONAME 'audit_log.so';
-
-Run the following command to verify if the plugin was installed correctly:
-
-.. sourcecode:: mysql
-
-    mysql> SELECT * FROM information_schema.PLUGINS WHERE PLUGIN_NAME LIKE '%audit%'\G
-    *************************** 1. row ***************************
-              PLUGIN_NAME: audit_log
-            PLUGIN_VERSION: 0.2
-            PLUGIN_STATUS: ACTIVE
-              PLUGIN_TYPE: AUDIT
-      PLUGIN_TYPE_VERSION: 4.1
-            PLUGIN_LIBRARY: audit_log.so
-    PLUGIN_LIBRARY_VERSION: 1.7
-            PLUGIN_AUTHOR: Percona LLC and/or its affiliates.
-        PLUGIN_DESCRIPTION: Audit log
-            PLUGIN_LICENSE: GPL
-              LOAD_OPTION: ON
-    1 row in set (0.00 sec)
-
-You can review the audit log variables with the following command:
-
-.. sourcecode:: mysql
-
-    mysql> SHOW variables LIKE 'audit%';
-    +-----------------------------+---------------+
-    | Variable_name               | Value         |
-    +-----------------------------+---------------+
-    | audit_log_buffer_size       | 1048576       |
-    | audit_log_exclude_accounts  |               |
-    | audit_log_exclude_commands  |               |
-    | audit_log_exclude_databases |               |
-    | audit_log_file              | audit.log     |
-    | audit_log_flush             | OFF           |
-    | audit_log_format            | OLD           |
-    | audit_log_handler           | FILE          |
-    | audit_log_include_accounts  |               |
-    | audit_log_include_commands  |               |
-    | audit_log_include_databases |               |
-    | audit_log_policy            | ALL           |
-    | audit_log_rotate_on_size    | 0             |
-    | audit_log_rotations         | 0             |
-    | audit_log_strategy          | ASYNCHRONOUS  |
-    | audit_log_syslog_facility   | LOG_USER      |
-    | audit_log_syslog_ident      | percona-audit |
-    | audit_log_syslog_priority   | LOG_INFO      |
-    +-----------------------------+---------------+
-    18 rows in set (0.00 sec)
-
-
-The audit Log plugin generates a log of following events:
-
-* **Audit** - Audit event indicates that audit logging started or finished. ``NAME`` field will be ``Audit`` when logging started and ``NoAudit`` when logging finished. Audit record also includes server version and command-line arguments.
-
-   An example of an Audit event: 
-
-   .. sourcecode:: xml
-
-      <AUDIT_RECORD
-         NAME="Audit"
-         RECORD="1_2021-06-30T11:56:53"
-         TIMESTAMP="2021-06-30T11:56:53 UTC"
-         MYSQL_VERSION="5.7.34-37"
-         STARTUP_OPTIONS="--daemonize --pid-file=/var/run/mysqld/mysqld.pid"
-         OS_VERSION="x86_64-debian-linux-gnu"
-      />
-
-* **Connect**/**Disconnect** - Connect record event will have ``NAME`` field ``Connect`` when user logged in or login failed, or ``Quit`` when connection is closed. 
-   The additional fields for this event are the following:
-
-   * ``CONNECTION_ID``
-
-   * ``STATUS``
-
-   * ``USER``
-
-   * ``PRIV_USER``
-
-   * ``OS_LOGIN``
-
-   * ``PROXY_USER``
-
-   * ``HOST``
-
-   * ``IP``
-
-   The value for ``STATUS`` is ``0`` for successful logins and non-zero for failed logins.
-
-   An example of a Disconnect event: 
-
-   .. sourcecode:: xml
-
-      <AUDIT_RECORD
-         NAME="Quit"
-         RECORD="5_2021-06-29T19:33:03"
-         TIMESTAMP="2021-06-29T19:34:38Z"
-         CONNECTION_ID="14"
-         STATUS="0"
-         USER="root"
-         PRIV_USER="root"
-         OS_LOGIN=""
-         PROXY_USER=""
-         HOST="localhost"
-         IP=""
-         DB=""
-      />
-
-* **Query** - Additional fields for this event are: ``COMMAND_CLASS`` (values come from the ``com_status_vars`` array in the :file:`sql/mysqld.cc`` file in a MySQL source distribution. 
-
-   Examples are ``select``, ``alter_table``, ``create_table``, etc.), ``CONNECTION_ID``, ``STATUS`` (indicates an error when the vaule is non-zero), ``SQLTEXT`` (text of SQL-statement), ``USER``, ``HOST``, ``OS_USER``, ``IP``. 
-   
-   The possible values for the ``NAME`` name field for this event are ``Query``, ``Prepare``, ``Execute``, ``Change user``, etc.
-
-   An example of the Query event: 
-
-   .. sourcecode:: xml
-
-      <AUDIT_RECORD
-         NAME="Query"
-         RECORD="4_2021-06-29T19:33:03"
-         TIMESTAMP="2021-06-29T19:33:34Z"
-         COMMAND_CLASS="show_variables"
-         CONNECTION_ID="14"
-         STATUS="0"
-         SQLTEXT="show variables like 'audit%'"
-         USER="root[root] @ localhost []"
-         HOST="localhost"
-         OS_USER=""
-         IP=""
-         DB=""
-      />
-
-Log Format
-==========
-
-The plugin supports the following log formats: ``OLD``, ``NEW``, ``JSON``, and ``CSV``. The ``OLD``format and the``NEW`` format are based on XML. The ``OLD`` format defines each log record with XML attributes. The ``NEW`` format defines each log record with XML tags. The information logged is the same for all four formats. The :ref:`audit_log_format` variable controls the log format choice.
-
-An example of the ``OLD`` format: 
-
-.. sourcecode:: xml
-
-  <AUDIT_RECORD
-    NAME="Query"
-    RECORD="3_2021-06-30T11:56:53"
-    TIMESTAMP="2021-06-30T11:57:14 UTC"
-    COMMAND_CLASS="select"
-    CONNECTION_ID="3"
-    STATUS="0"
-    SQLTEXT="select * from information_schema.PLUGINS where PLUGIN_NAME like '%audit%'"
-    USER="root[root] @ localhost []"
-    HOST="localhost"
-    OS_USER=""
-    IP=""
-    DB=""
-  />
-
-An example of the ``NEW`` format: 
-
-.. sourcecode:: xml
-
-  <AUDIT_RECORD>
-    <NAME>Query</NAME>
-    <RECORD>16684_2021-06-30T16:07:41</RECORD>
-    <TIMESTAMP>2021-06-30T16:08:06 UTC</TIMESTAMP>
-    <COMMAND_CLASS>select</COMMAND_CLASS>
-    <CONNECTION_ID>2</CONNECTION_ID>
-    <STATUS>0</STATUS>
-    <SQLTEXT>select id, holder from one</SQLTEXT>
-    <USER>root[root] @ localhost []</USER>
-    <HOST>localhost</HOST>
-    <OS_USER></OS_USER>
-    <IP></IP>
-    <DB></DB>
-
-An example of the ``JSON`` format: 
-
-.. sourcecode:: json
-
-  {"audit_record":{"name":"Query","record":"13149_2021-06-30T15:03:11","timestamp":"2021-06-30T15:07:58 UTC","command_class":"show_databases","connection_id":"2","status":0,"sqltext":"show databases","user":"root[root] @ localhost []","host":"localhost","os_user":"","ip":"","db":""}}
-
-An example of the ``CSV`` format: 
-
-.. sourcecode:: text
-
-  "Query","22567_2021-06-30T16:10:09","2021-06-30T16:19:00 UTC","select","2",0,"select count(*) from one","root[root] @ localhost []","localhost","","",""
-
-.. _streaming_to_syslog:
-
-Streaming the audit log to syslog
-=================================
-
-To stream the audit log to syslog you'll need to set :ref:`audit_log_handler` variable to ``SYSLOG``. To control the syslog file handler, the following variables can be used: :ref:`audit_log_syslog_ident`, :ref:`audit_log_syslog_facility`, and :ref:`audit_log_syslog_priority` These variables have the same meaning as appropriate parameters described in the `syslog(3) manual <http://linux.die.net/man/3/syslog>`_.
-
-.. note::
-
-   The actions for the variables: :ref:`audit_log_strategy`, :ref:`audit_log_buffer_size`, :ref:`audit_log_rotate_on_size`, :ref:`audit_log_rotations` are captured only with ``FILE`` handler. 
-
-.. _filtering_by_user:
-
-Filtering by user
-=================
-
-The filtering by user feature adds two new global variables:
-:ref:`audit_log_include_accounts` and
-:ref:`audit_log_exclude_accounts` to specify which user accounts should be
-included or excluded from audit logging.
-
-.. warning::
-
-   Only one of these variables can contain a list of users to be either
-   included or excluded, while the other needs to be ``NULL``. If one of the
-   variables is set to be not ``NULL`` (contains a list of users), the attempt
-   to set another one will fail. An empty string means an empty list.
-
-.. note::
-
-   Changes of :ref:`audit_log_include_accounts` and
-   :ref:`audit_log_exclude_accounts` do not apply to existing server
-   connections.
-
-Example
--------
-
-The following example adds users who will be monitored:
-
-.. code-block:: mysql
-
-   mysql> SET GLOBAL audit_log_include_accounts = 'user1@localhost,root@localhost';
-   Query OK, 0 rows affected (0.00 sec)
-
-If you try to add users to both the include list and the exclude list, the server returns the following error:
-
-.. code-block:: mysql
-
-   mysql> SET GLOBAL audit_log_exclude_accounts = 'user1@localhost,root@localhost';
-   ERROR 1231 (42000): Variable 'audit_log_exclude_accounts' can't be set to the value of 'user1@localhost,root@localhost'
-
-To switch from filtering by included user list to the excluded user list or back,
-first set the currently active filtering variable to ``NULL``:
-
-.. code-block:: mysql
-
-   mysql> SET GLOBAL audit_log_include_accounts = NULL;
-   Query OK, 0 rows affected (0.00 sec)
-
-   mysql> SET GLOBAL audit_log_exclude_accounts = 'user1@localhost,root@localhost';
-   Query OK, 0 rows affected (0.00 sec)
-
-   mysql> SET GLOBAL audit_log_exclude_accounts = "'user'@'host'";
-   Query OK, 0 rows affected (0.00 sec)
-
-   mysql> SET GLOBAL audit_log_exclude_accounts = '''user''@''host''';
-   Query OK, 0 rows affected (0.00 sec)
-
-   mysql> SET GLOBAL audit_log_exclude_accounts = '\'user\'@\'host\'';
-   Query OK, 0 rows affected (0.00 sec)
-
-To see which user accounts have been added to the exclude list, run the following command:
-
-.. code-block:: mysql
-
-   mysql> SELECT @@audit_log_exclude_accounts;
-   +------------------------------+
-   | @@audit_log_exclude_accounts |
-   +------------------------------+
-   | 'user'@'host'                |
-   +------------------------------+
-   1 row in set (0.00 sec)
-
-Account names from :ref:`mysql.user` table are logged in the
-audit log. For example when you create a user:
-
-.. code-block:: mysql
-
-   mysql> CREATE USER 'user1'@'%' IDENTIFIED BY '111';
-   Query OK, 0 rows affected (0.00 sec)
-
-When ``user1`` connects from ``localhost``, the user is listed:
-
-.. code-block:: none
-
-   <AUDIT_RECORD
-    NAME="Connect"
-    RECORD="2_2021-06-30T11:56:53"
-    TIMESTAMP="2021-06-30T11:56:53 UTC"
-    CONNECTION_ID="6"
-    STATUS="0"
-    USER="user1" ;; this is a 'user' part of account in 8.0
-    PRIV_USER="user1"
-    OS_LOGIN=""
-    PROXY_USER=""
-    HOST="localhost" ;; this is a 'host' part of account in 8.0
-    IP=""
-    DB=""
-  />
-
-To exclude ``user1`` from logging in *Percona Server for MySQL* 8.0, set:
-
-.. code-block:: mysql
-
-   SET GLOBAL audit_log_exclude_accounts = 'user1@%';
-
-The value can be ``NULL`` or comma separated list of accounts in form
-``user@host`` or ``'user'@'host'`` (if user or host contains comma).
-
-.. _filtering_by_sql_command_type:
-
-Filtering by SQL command type
-=============================
-
-The filtering by SQL command type adds two new global variables:
-:ref:`audit_log_include_commands` and
-:ref:`audit_log_exclude_commands` to specify which command types should be
-
-included or excluded from audit logging.
-
-.. warning::
-
-   Only one of these variables can contain a list of command types to be
-   either included or excluded, while the other needs to be ``NULL``. If one of
-   the variables is set to be not ``NULL`` (contains a list of command types),
-   the attempt to set another one will fail. An empty string is defined as an empty list.
-
-.. note::
-
-   If both the :ref:`audit_log_exclude_commands` variable and the 
-   :ref:`audit_log_include_commands` variable are ``NULL``, all commands are logged.
-
-Example
--------
-
-The available command types can be listed by running:
-
-.. code-block:: mysql
-
-   mysql> SELECT name FROM performance_schema.setup_instruments WHERE name LIKE "statement/sql/%" ORDER BY name;
-   +------------------------------------------+
-   | name                                     |
-   +------------------------------------------+
-   | statement/sql/alter_db                   |
-   | statement/sql/alter_db_upgrade           |
-   | statement/sql/alter_event                |
-   | statement/sql/alter_function             |
-   | statement/sql/alter_procedure            |
-   | statement/sql/alter_server               |
-   | statement/sql/alter_table                |
-   | statement/sql/alter_tablespace           |
-   | statement/sql/alter_user                 |
-   | statement/sql/analyze                    |
-   | statement/sql/assign_to_keycache         |
-   | statement/sql/begin                      |
-   | statement/sql/binlog                     |
-   | statement/sql/call_procedure             |
-   | statement/sql/change_db                  |
-   | statement/sql/change_master              |
-   ...
-   | statement/sql/xa_rollback                |
-   | statement/sql/xa_start                   |
-   +------------------------------------------+
-   145 rows in set (0.00 sec)
-
-You can add commands to the ``include`` filter by running:
-
-.. code-block:: mysql
-
-   mysql> SET GLOBAL audit_log_include_commands= 'set_option,create_db';
-
-Create a database with the following command:
-
-.. code-block:: mysql
-
-  mysql> CREATE DATABASE sample;
-
-The action is captured in the audit log:
-
-.. code-block:: xml
-
-  <AUDIT_RECORD>
-    <NAME>Query</NAME>
-    <RECORD>24320_2021-06-30T17:44:46</RECORD>
-    <TIMESTAMP>2021-06-30T17:45:16 UTC</TIMESTAMP>
-    <COMMAND_CLASS>create_db</COMMAND_CLASS>
-    <CONNECTION_ID>2</CONNECTION_ID>
-    <STATUS>0</STATUS>
-    <SQLTEXT>CREATE DATABASE sample</SQLTEXT>
-    <USER>root[root] @ localhost []</USER>
-    <HOST>localhost</HOST>
-    <OS_USER></OS_USER>
-    <IP></IP>
-    <DB></DB>
-  </AUDIT_RECORD>
-
-To switch the command type filtering type from included type list to the excluded list
-or back, first reset the currently-active list to ``NULL``:
-
-.. code-block:: mysql
-
-   mysql> SET GLOBAL audit_log_include_commands = NULL;
-   Query OK, 0 rows affected (0.00 sec)
-
-   mysql> SET GLOBAL audit_log_exclude_commands= 'set_option,create_db';
-   Query OK, 0 rows affected (0.00 sec)
-
-.. note::
-
-  A stored procedure has the ``call_procedure`` command type. All
-  the statements executed within the procedure have the same type
-  ``call_procedure`` as well.
-
-.. _filtering_by_database:
-
-Filtering by database
-=====================
-
-The filtering by an SQL database is implemented by two global variables:
-:ref:`audit_log_include_databases` and
-:ref:`audit_log_exclude_databases` to specify which databases should be
-
-included or excluded from audit logging.
-
-.. warning::
-
-   Only one of these variables can contain a list of databases to be either
-   included or excluded, while the other needs to be ``NULL``. If one of the
-   variables is set to be not ``NULL`` (contains a list of databases), the
-   attempt to set another one will fail. Empty string means an empty list.
-
-
-If query is accessing any of databases listed in
-:ref:`audit_log_include_databases`, the query will be logged.
-If query is accessing only databases listed in
-:ref:`audit_log_exclude_databases`, the query will not be logged.
-``CREATE TABLE`` statements are logged unconditionally.
-
-.. note::
-
-   Changes of :ref:`audit_log_include_databases` and
-   :ref:`audit_log_exclude_databases` do not apply to existing server
-   connections.
-
-Example
--------
-
-To add databases to be monitored you should run:
-
-.. code-block:: mysql
-
-   mysql> SET GLOBAL audit_log_include_databases = 'test,mysql,db1';
-   Query OK, 0 rows affected (0.00 sec)
-
-   mysql> SET GLOBAL audit_log_include_databases= 'db1','db3';
-   Query OK, 0 rows affected (0.00 sec)
-
-If you you try to add databases to both include and exclude lists server will
-show you the following error:
-
-.. code-block:: mysql
-
-   mysql> SET GLOBAL audit_log_exclude_databases = 'test,mysql,db1';
-   ERROR 1231 (42000): Variable 'audit_log_exclude_databases can't be set to the value of 'test,mysql,db1'
-
-To switch from filtering by included database list to the excluded one or back,
-first set the currently active filtering variable to ``NULL``:
-
-.. code-block:: mysql
-
-   mysql> SET GLOBAL audit_log_include_databases = NULL;
-   Query OK, 0 rows affected (0.00 sec)
-
-   mysql> SET GLOBAL audit_log_exclude_databases = 'test,mysql,db1';
-   Query OK, 0 rows affected (0.00 sec)
-
-System Variables
-================
-
-.. _audit_log_strategy:
-
-.. rubric:: ``audit_log_strategy``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - Yes
-   * - Scope
-     - Global
-   * - Dynamic
-     - No
-   * - Data type
-     - String
-   * - Default
-     - ASYNCHRONOUS
-   * - Allowed values
-     - ``ASYNCHRONOUS``, ``PERFORMANCE``, ``SEMISYNCHRONOUS``, ``SYNCHRONOUS``
-
-This variable is used to specify the audit log strategy, possible values are:
-
-* ``ASYNCHRONOUS`` - (default) log using memory buffer, do not drop messages if buffer is full
-* ``PERFORMANCE`` - log using memory buffer, drop messages if buffer is full
-* ``SEMISYNCHRONOUS`` - log directly to file, do not flush and sync every event
-* ``SYNCHRONOUS`` - log directly to file, flush and sync every event
-
-This variable has effect only when :ref:`audit_log_handler` is set to ``FILE``.
-
-.. _audit_log_file:
-
-.. rubric:: ``audit_log_file``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - Yes
-   * - Scope
-     - Global
-   * - Dynamic
-     - No
-   * - Data type
-     - String
-   * - Default
-     - audit.log
-
-This variable is used to specify the filename that's going to store the audit log. It can contain the path relative to the datadir or absolute path.
-
-.. _audit_log_flush:
-
-.. rubric:: ``audit_log_flush``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - Yes
-   * - Scope
-     - Global
-   * - Dynamic
-     - Yes
-   * - Data type
-     - String
-   * - Default
-     - OFF
-
-When this variable is set to ``ON`` log file will be closed and reopened. This can be used for manual log rotation.
-
-.. _audit_log_buffer_size:
-
-.. rubric:: ``audit_log_buffer_size``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - Yes
-   * - Scope
-     - Global
-   * - Dynamic
-     - No
-   * - Data type
-     - Numeric
-   * - Default
-     - 1 Mb
-
-This variable can be used to specify the size of memory buffer used for logging, used when :ref:`audit_log_strategy` variable is set to ``ASYNCHRONOUS`` or ``PERFORMANCE`` values. This variable has effect only when :ref:`audit_log_handler` is set to ``FILE``.
-
-.. _audit_log_exclude_accounts:
-
-.. rubric:: ``audit_log_exclude_accounts``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - Yes
-   * - Scope
-     - Global
-   * - Dynamic
-     - Yes
-   * - Data type
-     - String
-
-This variable is used to specify the list of users for which
-:ref:`filtering_by_user` is applied. The value can be ``NULL`` or comma
-separated list of accounts in form ``user@host`` or ``'user'@'host'`` (if user
-or host contains comma). If this variable is set, then
-:ref:`audit_log_include_accounts` must be unset, and vice versa.
-
-.. _audit_log_exclude_commands:
-
-.. rubric:: ``audit_log_exclude_commands``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - Yes
-   * - Scope
-     - Global
-   * - Dynamic
-     - Yes
-   * - Data type
-     - String
-
-This variable is used to specify the list of commands for which
-:ref:`filtering_by_sql_command_type` is applied. The value can be ``NULL`` or
-comma separated list of commands. If this variable is set, then
-:ref:`audit_log_include_commands` must be unset, and vice versa.
-
-.. _audit_log_exclude_databases:
-
-.. rubric:: ``audit_log_exclude_databases``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - Yes
-   * - Scope
-     - Global
-   * - Dynamic
-     - Yes
-   * - Data type
-     - String
-
-This variable is used to specify the list of commands for which
-:ref:`filtering_by_database` is applied. The value can be ``NULL`` or
-comma separated list of commands. If this variable is set, then
-:ref:`audit_log_include_databases` must be unset, and vice versa.
-
-.. _audit_log_format:
-
-.. rubric:: ``audit_log_format``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - Yes
-   * - Scope
-     - Global
-   * - Dynamic
-     - No
-   * - Data type
-     - String
-   * - Default
-     - OLD
-   * - Allowed values
-     - ``OLD``, ``NEW``, ``CSV``, ``JSON``
-
-This variable is used to specify the audit log format. The audit log plugin
-supports four log formats: ``OLD``, ``NEW``, ``JSON``, and ``CSV``. ``OLD`` and
-``NEW`` formats are based on XML, where the former outputs log record properties
-as XML attributes and the latter as XML tags. Information logged is the same in
-all four formats.
-
-.. _audit_log_include_accounts:
-
-.. rubric:: ``audit_log_include_accounts``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - Yes
-   * - Scope
-     - Global
-   * - Dynamic
-     - Yes
-   * - Data type
-     - String
-
-This variable is used to specify the list of users for which
-:ref:`filtering_by_user` is applied. The value can be ``NULL`` or comma
-separated list of accounts in form ``user@host`` or ``'user'@'host'`` (if user
-or host contains comma). If this variable is set, then
-:ref:`audit_log_exclude_accounts` must be unset, and vice versa.
-
-.. _audit_log_include_commands:
-
-.. rubric:: ``audit_log_include_commands``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - Yes
-   * - Scope
-     - Global
-   * - Dynamic
-     - Yes
-   * - Data type
-     - String
-
-This variable is used to specify the list of commands for which
-:ref:`filtering_by_sql_command_type` is applied. The value can be ``NULL`` or
-comma separated list of commands. If this variable is set, then
-:ref:`audit_log_exclude_commands` must be unset, and vice versa.
-
-.. _audit_log_include_databases:
-
-.. rubric:: ``audit_log_include_databases``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - Yes
-   * - Scope
-     - Global
-   * - Dynamic
-     - Yes
-   * - Data type
-     - String
-
-This variable is used to specify the list of commands for which
-:ref:`filtering_by_database` is applied. The value can be ``NULL`` or
-comma separated list of commands. If this variable is set, then
-:ref:`audit_log_exclude_databases` must be unset, and vice versa.
-
-.. _audit_log_policy:
-
-.. rubric:: ``audit_log_policy``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - Yes
-   * - Scope
-     - Global
-   * - Dynamic
-     - Yes
-   * - Data type
-     - String
-   * - Default
-     - ALL
-   * - Allowed values
-     - ``ALL``, ``LOGINS``, ``QUERIES``, ``NONE``
-
-This variable is used to specify which events should be logged. Possible values
-are:
-
-* ``ALL`` - all events will be logged
-* ``LOGINS`` - only logins will be logged
-* ``QUERIES`` - only queries will be logged
-* ``NONE`` - no events will be logged
-
-.. _audit_log_rotate_on_size:
-
-.. rubric:: ``audit_log_rotate_on_size``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - Yes
-   * - Scope
-     - Global
-   * - Dynamic
-     - No
-   * - Data type
-     - Numeric
-   * - Default
-     - 0 (don't rotate the log file)
-
-This variable is measured in bytes and specifies the maximum size of the audit log file. Upon reaching
-this size, the audit log will be rotated. The rotated log files are present in
-the same directory as the current log file. The sequence number is appended to
-the log file name upon rotation. For this variable to take effect, set the :ref:`audit_log_handler` variable to ``FILE``.
- 
-.. _audit_log_rotations:
-
-.. rubric:: ``audit_log_rotations``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - Yes
-   * - Scope
-     - Global
-   * - Dynamic
-     - No
-   * - Data type
-     - Numeric
-   * - Default
-     - 0 
-
-This variable is used to specify how many log files should be kept when
-:ref:`audit_log_rotate_on_size` variable is set to non-zero value. This
-variable has effect only when :ref:`audit_log_handler` is set to ``FILE``.
-
-.. _audit_log_handler:
-
-.. rubric:: ``audit_log_handler``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - Yes
-   * - Scope
-     - Global
-   * - Dynamic
-     - No
-   * - Data type
-     - String
-   * - Default
-     - FILE
-   * - Allowed values
-     - ``FILE``, ``SYSLOG``
-
-This variable is used to configure where the audit log will be written. If it is
-set to ``FILE``, the log will be written into a file specified by
-:ref:`audit_log_file` variable. If it is set to ``SYSLOG``, the audit log
-will be written to syslog.
-
-.. _audit_log_syslog_ident:
-
-.. rubric:: ``audit_log_syslog_ident``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - Yes
-   * - Scope
-     - Global
-   * - Dynamic
-     - No
-   * - Data type
-     - String
-   * - Default
-     - percona-audit
-
-This variable is used to specify the ``ident`` value for syslog. This variable
-has the same meaning as the appropriate parameter described in the `syslog(3)
-manual <http://linux.die.net/man/3/syslog>`_.
-
-.. _audit_log_syslog_facility:
-
-.. rubric:: ``audit_log_syslog_facility``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - Yes
-   * - Scope
-     - Global
-   * - Dynamic
-     - No
-   * - Data type
-     - String
-   * - Default
-     - LOG_USER
-
-This variable is used to specify the ``facility`` value for syslog. This
-variable has the same meaning as the appropriate parameter described in the
-`syslog(3) manual <http://linux.die.net/man/3/syslog>`_.
-
-.. _audit_log_syslog_priority:
-
-.. rubric:: ``audit_log_syslog_priority``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - Yes
-   * - Scope
-     - Global
-   * - Dynamic
-     - No
-   * - Data type
-     - String
-   * - Default
-     - LOG_INFO
-
-This variable is used to specify the ``priority`` value for syslog. This
-variable has the same meaning as the appropriate parameter described in the
-`syslog(3) manual <http://linux.die.net/man/3/syslog>`_.
-
-Status Variables
-================
-
-.. _Audit_log_buffer_size_overflow:
-
-.. rubric:: ``Audit_log_buffer_size_overflow``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Scope
-     - Global
-   * - Data type
-     - Numeric
-
-The number of times an audit log entry was either
-dropped or written directly to the file due to its size being bigger
-than :ref:`audit_log_buffer_size` variable.
-
-Version Specific Information
-============================
-
-  * :ref:`8.0.12-1`: The feature was ported from *Percona Server for MySQL* 5.7.
-  * :ref:`8.0.15-6`: The :ref:`Audit_log_buffer_size_overflow` variable was implemented.
diff --git a/doc/source/management/backup_locks.rst b/doc/source/management/backup_locks.rst
deleted file mode 100644
index abeea1a34b23..000000000000
--- a/doc/source/management/backup_locks.rst
+++ /dev/null
@@ -1,203 +0,0 @@
-.. _backup_locks:
-
-================================================================================
-Backup Locks
-================================================================================
-
-*Percona Server for MySQL* offers the ``LOCK TABLES FOR BACKUP`` statement as a
-lightweight alternative to ``FLUSH TABLES WITH READ LOCK`` for both physical and
-logical backups.
-
-.. note::
-
-        As of *Percona Server for MySQL* 8.0.13-4, ``LOCK TABLES FOR BACKUP`` requires the
-        ``BACKUP_ADMIN`` privilege.
-
-LOCK TABLES FOR BACKUP
-================================================================================
-
-``LOCK TABLES FOR BACKUP`` uses a new MDL lock type to block updates to
-non-transactional tables and DDL statements for all tables. If there is an
-active ``LOCK TABLES FOR BACKUP`` lock then all DDL statements and all updates
-to MyISAM, CSV, MEMORY, ARCHIVE, *TokuDB*, and *MyRocks* tables will be blocked
-in the ``Waiting for backup lock`` status, visible in ``PERFORMANCE_SCHEMA`` or
-``PROCESSLIST``.
-
-``LOCK TABLES FOR BACKUP`` has no effect on ``SELECT`` queries for all mentioned
-storage engines. Against *InnoDB*, *MyRocks*, Blackhole and Federated tables,
-the ``LOCK TABLES FOR BACKUP`` is not applicable to the ``INSERT``, ``REPLACE``,
-``UPDATE``, ``DELETE`` statements: Blackhole tables obviously have no relevance
-to backups, and Federated tables are ignored by both logical and physical backup
-tools.
-
-Unlike ``FLUSH TABLES WITH READ LOCK``, ``LOCK TABLES FOR BACKUP`` does not
-flush tables, i.e. storage engines are not forced to close tables and tables are
-not expelled from the table cache. As a result, ``LOCK TABLES FOR BACKUP`` only
-waits for conflicting statements to complete (i.e. DDL and updates to
-non-transactional tables). It never waits for SELECTs, or UPDATEs to *InnoDB* or
-*MyRocks* tables to complete, for example.
-
-If an "unsafe" statement is executed in the same connection that is holding a
-``LOCK TABLES FOR BACKUP`` lock, it fails with the following error: ::
-
- ERROR 1880 (HY000): Can't execute the query because you have a conflicting backup lock
-
- UNLOCK TABLES releases the lock acquired by LOCK TABLES FOR BACKUP.
-
-The intended use case for |Percona XtraBackup| is: :: 
-
-  LOCK TABLES FOR BACKUP
-  ... copy .frm, MyISAM, CSV, etc. ...
-  UNLOCK TABLES
-  ... get binlog coordinates ...
-  ... wait for redo log copying to finish ...
-
-Privileges
-================================================================================
-
-The ``LOCK TABLES FOR BACKUP`` requires the ``BACKUP_ADMIN``
-privilege. 
-
-Interaction with other global locks
-================================================================================
-
-The ``LOCK TABLES FOR BACKUP`` has no effect if the current connection already
-owns a ``FLUSH TABLES WITH READ LOCK`` lock, as it is a more restrictive
-lock. If ``FLUSH TABLES WITH READ LOCK`` is executed in a connection that has
-acquired ``LOCK TABLES FOR BACKUP``, ``FLUSH TABLES WITH READ LOCK`` fails with
-an error.
-
-If the server is operating in the read-only mode (i.e. :ref:`read_only` set
-to ``1``), statements that are unsafe for backups will be either blocked or fail
-with an error, depending on whether they are executed in the same connection
-that owns ``LOCK TABLES FOR BACKUP`` lock, or other connections.
-
-MyISAM index and data buffering
-================================================================================
-
-*MyISAM* key buffering is normally write-through, i.e. by the time each update
-to a *MyISAM* table is completed, all index updates are written to disk. The
-only exception is delayed key writing feature which is disabled by default.
-
-When the global system variable `delay_key_write` is set to ``ALL``,
-key buffers for all *MyISAM* tables are not flushed between updates, so a
-physical backup of those tables may result in broken *MyISAM* indexes. To
-prevent this, ``LOCK TABLES FOR BACKUP`` will fail with an error if
-`delay_key_write` is set to ``ALL``. An attempt to set `delay_key_write` to ``ALL`` when there's an active backup lock will
-also fail with an error.
-
-Another option to involve delayed key writing is to create *MyISAM* tables with
-the DELAY_KEY_WRITE option and set the `delay_key_write` variable to
-``ON`` (which is the default). In this case, ``LOCK TABLES FOR BACKUP`` will not
-be able to prevent stale index files from appearing in the backup. Users are
-encouraged to set `delay_key_writes` to ``OFF`` in the configuration
-file, :file:`my.cnf`, or repair *MyISAM* indexes after restoring from a physical
-backup created with backup locks.
-
-*MyISAM* may also cache data for bulk inserts, e.g. when executing multi-row
-INSERTs or ``LOAD DATA`` statements. Those caches, however, are flushed between
-statements, so have no effect on physical backups as long as all statements
-updating *MyISAM* tables are blocked.
-
-The mysqldump Command
-================================================================================
-
-``mysqldump`` has also been extended with a new option,
-:ref:`lock-for-backup` (disabled by default). When used together with the
-`--single-transaction` option, the option makes ``mysqldump`` issue
-``LOCK TABLES FOR BACKUP`` before starting the dump operation to prevent unsafe
-statements that would normally result in an inconsistent backup.
-
-When used without the `--single-transaction` option,
-:ref:`lock-for-backup` is automatically converted to `lock-all-tables`.
-
-The option :ref:`lock-for-backup` is mutually exclusive with `lock-all-tables`, i.e. specifying both on the command line will lead to
-an error.
-
-If the backup locks feature is not supported by the target server, but
-:ref:`lock-for-backup` is specified on the command line, ``mysqldump`` aborts
-with an error.
-
-Version Specific Information
-================================================================================
-
-  * :ref:`8.0.12-1`: The feature was ported from *Percona Server for MySQL* 5.7.
-
-System Variables
-================================================================================
-
-.. _have_backup_locks:
-
-.. rubric:: ``have_backup_locks``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - Yes
-   * - Config file
-     - No
-   * - Scope
-     - Global
-   * - Dynamic
-     - No
-   * - Data type
-     - Boolean
-   * - Default
-     - YES
-
-This is a server variable implemented to help other utilities decide what
-locking strategy can be implemented for a server. When available, the backup
-locks feature is supported by the server and the variable value is always
-``YES``.
-
-Status Variables
-================================================================================
-
-.. _Com_lock_tables_for_backup:
-
-.. rubric:: ``Com_lock_tables_for_backup``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Scope
-     - Global/Session
-   * - Data type
-     - Numeric
-
-This status variable indicates the number of times the corresponding statements
-have been executed.
-
-Client Command Line Parameter
-================================================================================
-
-.. _lock-for-backup:
-
-.. rubric:: ``lock-for-backup``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - Yes
-   * - Scope
-     - Global
-   * - Dynamic
-     - No
-   * - Data type
-     - String
-   * - Default
-     - Off
-
-When used together with the `--single-transaction` option, the option
-makes ``mysqldump`` issue ``LOCK TABLES FOR BACKUP`` before starting the dump
-operation to prevent unsafe statements that would normally result in an
-inconsistent backup.
-
diff --git a/doc/source/management/changed_page_tracking.rst b/doc/source/management/changed_page_tracking.rst
deleted file mode 100644
index b7e2f23c2e6b..000000000000
--- a/doc/source/management/changed_page_tracking.rst
+++ /dev/null
@@ -1,162 +0,0 @@
-.. _changed_page_tracking:
-
-=============================
-XtraDB changed page tracking
-=============================
-
-.. Important:: 
-
-        Starting with Percona Server for MySQL 8.0.27, the page tracking feature is deprecated and may be removed in future versions.
-
-        We recommend using the MySQL page tracking feature. For more information, see `MySQL InnoDB Clone and page tracking <https://dev.mysql.com/blog-archive/innodb-clone-and-page-tracking>`_ .
-
-*XtraDB* now tracks the pages that have changes written to them according to the redo log. This information is written out in special changed page bitmap files. This information can be used to speed up incremental backups using `Percona XtraBackup <http://www.percona.com/doc/percona-xtrabackup/>`_ by removing the need to scan whole data files to find the changed pages. Changed page tracking is done by a new *XtraDB* worker thread that reads and parses log records between checkpoints. The tracking is controlled by a new read-only server variable :ref:`innodb_track_changed_pages`.
-
-Bitmap filename format used for changed page tracking is ``ib_modified_log_<seq>_<startlsn>.xdb``. The first number is the sequence number of the bitmap log file and the *startlsn* number is the starting LSN number of data tracked in that file. Example of the bitmap log files should look like this: :: 
-
- ib_modified_log_1_0.xdb
- ib_modified_log_2_1603391.xdb
-
-Sequence number can be used to easily check if all the required bitmap files are present. Start LSN number will be used in *XtraBackup* and ``INFORMATION_SCHEMA`` queries to determine which files have to be opened and read for the required LSN interval data. The bitmap file is rotated on each server restart and whenever the current file size reaches the predefined maximum. This maximum is controlled by a new :ref:`innodb_max_bitmap_file_size` variable.
-
-Old bitmap files may be safely removed after a corresponding incremental backup is taken. For that there are server :ref:`changed_page_tracking_statements`. Removing the bitmap files from the filesystem directly is safe too, as long as care is taken not to delete data for not-yet-backuped LSN range.
-
-This feature will be used for implementing faster incremental backups that use this information to avoid full data scans in *Percona XtraBackup*.
-
-.. _changed_page_tracking_statements:
-
-User statements for handling the XtraDB changed page bitmaps
-============================================================
-
-New statements have been introduced for handling the changed page bitmap tracking. All of these statements require ``SUPER`` privilege.
-
- * ``FLUSH CHANGED_PAGE_BITMAPS`` - this statement can be used for synchronous bitmap write for immediate catch-up with the log checkpoint. This is used by innobackupex to make sure that XtraBackup indeed has all the required data it needs.
- * ``RESET CHANGED_PAGE_BITMAPS`` - this statement will delete all the bitmap log files and restart the bitmap log file sequence.
- * ``PURGE CHANGED_PAGE_BITMAPS BEFORE <lsn>`` - this statement will delete all the change page bitmap files up to the specified log sequence number.
-
-Additional information in SHOW ENGINE INNODB STATUS
-===================================================
-When log tracking is enabled, the following additional fields are displayed in the LOG section of the ``SHOW ENGINE INNODB STATUS`` output:
-
- * "Log tracked up to:" displays the LSN up to which all the changes have been parsed and stored as a bitmap on disk by the log tracking thread
- * "Max tracked LSN age:" displays the maximum limit on how far behind the log tracking thread may be.
-
-.. note:: 
-
-        Implemented in Percona Server for MySQL 8.0.13-4, a new InnoDB monitor,
-        log_writer_on_tracker_waits, records log writer waits due to changed
-        page tracking lag. This log writer works in parallel with other
-        log_writer_on_[*]_ waits monitors.
-
-INFORMATION_SCHEMA Tables
-=========================
-
-This table contains a list of modified pages from the bitmap file data. As these files are generated by the log tracking thread parsing the log whenever the checkpoint is made, it is not real-time data.
-
-.. _INNODB_CHANGED_PAGES:
-
-.. rubric:: ``INFORMATION_SCHEMA.INNODB_CHANGED_PAGES``
-
-.. list-table::
-      :header-rows: 1
-
-      * - Column Name
-        - Description
-      * - 'INT(11) space_id'
-        - 'space id of modified page'
-      * - 'INT(11) page_id'
-        - 'id of modified page'
-      * - 'BIGINT(21) start_lsn'
-        - 'start of the interval'
-      * - 'BIGINT(21) end_lsn'
-        - 'end of the interval '
-
-The ``start_lsn`` and the ``end_lsn`` columns denote between which two checkpoints this page was changed at least once. They are also equal to checkpoint LSNs.
-
-Number of records in this table can be limited by using the variable :ref:`innodb_max_changed_pages`.
-
-Version Specific Information
-============================
-
-  * `8.0.12-1`: The feature was ported from *Percona Server for MySQL* 5.7.
-
-System Variables
-================
-
-.. _innodb_max_changed_pages:
-
-.. rubric:: ``innodb_max_changed_pages``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - Yes
-   * - Config file
-     - Yes
-   * - Scope
-     - Global
-   * - Dynamic
-     - Yes
-   * - Data type
-     - Numeric
-   * - Default
-     - 1000000
-   * - Range
-     - 1 - 0 (unlimited)
-
-This variable is used to limit the result row count for the queries from :ref:`INNODB_CHANGED_PAGES` table.
-
-.. _innodb_track_changed_pages:
-
-.. rubric:: ``innodb_track_changed_pages``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - Yes
-   * - Config file
-     - Yes
-   * - Scope
-     - Global
-   * - Dynamic
-     - No
-   * - Data type
-     - Boolean
-   * - Default
-     - 0 - False
-   * - Range
-     - 0-1
-
-This variable is used to enable/disable :ref:`changed_page_tracking` feature.
-
-.. _innodb_max_bitmap_file_size:
-
-.. rubric:: ``innodb_max_bitmap_file_size``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - Yes
-   * - Config file
-     - Yes
-   * - Scope
-     - Global
-   * - Dynamic
-     - Yes
-   * - Data type
-     - Numeric 
-   * - Default
-     - 104857600 (100 MB)
-   * - Range
-     - 4096 (4KB) - 18446744073709551615 (16EB)
-
-This variable is used to control maximum bitmap size after which the file will be rotated.
diff --git a/doc/source/management/enforce_engine.rst b/doc/source/management/enforce_engine.rst
deleted file mode 100644
index 56d3b82f9160..000000000000
--- a/doc/source/management/enforce_engine.rst
+++ /dev/null
@@ -1,67 +0,0 @@
-.. _enforce_engine:
-
-========================
-Enforcing Storage Engine
-========================
-
-*Percona Server for MySQL* has implemented variable which can be used for enforcing the
-use of a specific storage engine.
-
-When this variable is specified and a user tries to create a table using an
-explicit storage engine that is not the specified enforced engine, the user
-will get either an error if the ``NO_ENGINE_SUBSTITUTION`` SQL mode is enabled
-or a warning if ``NO_ENGINE_SUBSTITUTION`` is disabled and the table
-will be created anyway using the enforced engine (this is consistent with the
-default *MySQL* way of creating the default storage engine if other engines
-are not available unless ``NO_ENGINE_SUBSTITUTION`` is set).
-
-In case user tries to enable :ref:`enforce_storage_engine` with engine
-that isn't available, system will not start.
-
-.. note::
- 
- If you're using :ref:`enforce_storage_engine`, you must either disable
- it before doing ``mysql_upgrade`` or perform ``mysql_upgrade`` with server
- started with :option:`--skip-grants-tables`.
-
-Version Specific Information
-============================
-
-* :ref:`8.0.13-4`: The feature was ported from *Percona Server for MySQL* 5.7.
-
-System Variables
-================
-
-.. _enforce_storage_engine:
-
-.. rubric:: ``enforce_storage_engine``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - Yes
-   * - Config file
-     - Yes
-   * - Scope
-     - Global
-   * - Dynamic
-     - No
-   * - Data type
-     - String
-   * - Default
-     - NULL
-
-.. note:: 
-
-  This variable is not case sensitive.
-
-Example
-=======
-
-Adding following option to :term:`my.cnf` will start the server with InnoDB as
-enforced storage engine. ::  
-
- enforce_storage_engine=InnoDB
diff --git a/doc/source/management/extended_show_grants.rst b/doc/source/management/extended_show_grants.rst
deleted file mode 100644
index 1925c75146e3..000000000000
--- a/doc/source/management/extended_show_grants.rst
+++ /dev/null
@@ -1,80 +0,0 @@
-.. _extended_show_grants:
-
-================================================================================
-Extended ``SHOW GRANTS``
-================================================================================
-
-In Oracle *MySQL* ``SHOW GRANTS`` displays only the privileges granted
-explicitly to the named account. Other privileges might be available
-to the account, but they are not displayed. For example, if an
-anonymous account exists, the named account might be able to use its
-privileges, but ``SHOW GRANTS`` will not display them. |Percona
-Server| offers the ``SHOW EFFECTIVE GRANTS`` command to display
-all the effectively available privileges to the account, including
-those granted to a different account.
-
-Example
-================================================================================
-If we create the following users:
-
-.. code-block:: mysql
-
-   mysql> CREATE USER grantee@localhost IDENTIFIED BY 'grantee1';
-   Query OK, 0 rows affected (0.50 sec)
-
-   mysql> CREATE USER grantee IDENTIFIED BY 'grantee2';
-   Query OK, 0 rows affected (0.09 sec)
-
-   mysql> CREATE DATABASE db2;
-   Query OK, 1 row affected (0.20 sec)
-
-   mysql> GRANT ALL PRIVILEGES ON db2.* TO grantee WITH GRANT OPTION;
-   Query OK, 0 rows affected (0.12 sec)
-
-
-* ``SHOW EFFECTIVE GRANTS`` output before the change: 
-
-.. code-block:: mysql
-
-   mysql> SHOW EFFECTIVE GRANTS;
-   +----------------------------------------------------------------------------------------------------------------+
-   | Grants for grantee@localhost                                                                                   |
-   +----------------------------------------------------------------------------------------------------------------+
-   | GRANT USAGE ON *.* TO 'grantee'@'localhost' IDENTIFIED BY PASSWORD '*9823FF338D44DAF02422CF24DD1F879FB4F6B232' |
-   +----------------------------------------------------------------------------------------------------------------+
-   1 row in set (0.04 sec)
-   
-Although the grant for the ``db2`` database isn't shown, ``grantee`` user has enough privileges to create the table in that database:
-
-.. code-block:: bash
-
-   user@trusty:~$ mysql -ugrantee -pgrantee1 -h localhost
-
-.. code-block:: mysql
-
-   mysql> CREATE TABLE db2.t1(a int);
-   Query OK, 0 rows affected (1.21 sec)
-
-* The output of ``SHOW EFFECTIVE GRANTS`` after the change shows all
-  the privileges for the ``grantee`` user:
-
-.. code-block:: mysql
-
-   mysql> SHOW EFFECTIVE GRANTS;
-   +----------------------------------------------------------------------------------------------------------------+
-   | Grants for grantee@localhost                                                                                   |
-   +----------------------------------------------------------------------------------------------------------------+
-   | GRANT USAGE ON *.* TO 'grantee'@'localhost' IDENTIFIED BY PASSWORD '*9823FF338D44DAF02422CF24DD1F879FB4F6B232' |
-   | GRANT ALL PRIVILEGES ON `db2`.* TO 'grantee'@'%' WITH GRANT OPTION                                             |
-   +----------------------------------------------------------------------------------------------------------------+
-   2 rows in set (0.00 sec)
-  
-Version-Specific Information
-================================================================================
-
-  * :ref:`8.0.12-1`: The feature was ported from *Percona Server for MySQL* 5.7.
-
-Other reading
-================================================================================
-
-* :mysqlbug:`53645` - ``SHOW GRANTS`` not displaying all the applicable grants
diff --git a/doc/source/management/innodb_expanded_fast_index_creation.rst b/doc/source/management/innodb_expanded_fast_index_creation.rst
deleted file mode 100644
index 75544a531962..000000000000
--- a/doc/source/management/innodb_expanded_fast_index_creation.rst
+++ /dev/null
@@ -1,110 +0,0 @@
-.. _expanded_innodb_fast_index_creation:
-
-================================================================================
-Expanded Fast Index Creation
-================================================================================
-
-:Availability: This feature is **Experimental** qualtiy.
-
-Percona has implemented several changes related to *MySQL*'s fast index creation
-feature. Fast index creation was implemented in *MySQL* as a way to speed up the
-process of adding or dropping indexes on tables with many rows.
-
-This feature implements a session variable that enables extended fast index
-creation. Besides optimizing DDL directly,
-:ref:`expand_fast_index_creation` may also optimize index access for
-subsequent DML statements because using it results in much less fragmented
-indexes.
-
-The **mysqldump** Command
-==========================================
-
-A new option, ``--innodb-optimize-keys``, was implemented in **mysqldump**. It
-changes the way *InnoDB* tables are dumped, so that secondary and foreign keys
-are created after loading the data, thus taking advantage of fast index
-creation. More specifically:
-
-* ``KEY``, ``UNIQUE KEY``, and ``CONSTRAINT`` clauses are omitted from ``CREATE
-  TABLE`` statements corresponding to *InnoDB* tables.
-* An additional ``ALTER TABLE`` is issued after dumping the data, in order to
-  create the previously omitted keys.
-
-``ALTER TABLE``
-================================================================================
-
-When ``ALTER TABLE`` requires a table copy, secondary keys are now dropped and
-recreated later, after copying the data. The following restrictions apply:
-
-* Only non-unique keys can be involved in this optimization.
-* If the table contains foreign keys, or a foreign key is being added as a part
-  of the current ``ALTER TABLE`` statement, the optimization is disabled for all
-  keys.
-
-``OPTIMIZE TABLE``
-================================================================================
-
-Internally, ``OPTIMIZE TABLE`` is mapped to ``ALTER TABLE ... ENGINE=innodb``
-for *InnoDB* tables. As a consequence, it now also benefits from fast index
-creation, with the same restrictions as for ``ALTER TABLE``.
-
-
-Caveats
-================================================================================
-
-*InnoDB* fast index creation uses temporary files in tmpdir for all indexes
-being created. So make sure you have enough tmpdir space when using
-:ref:`expand_fast_index_creation`. It is a session variable, so you can
-temporarily switch it off if you are short on tmpdir space and/or don’t want
-this optimization to be used for a specific table.
-
-There’s also a number of cases when this optimization is not applicable:
-
-* ``UNIQUE`` indexes in ``ALTER TABLE`` are ignored to enforce uniqueness where
-  necessary when copying the data to a temporary table;
-* ``ALTER TABLE`` and ``OPTIMIZE TABLE`` always process tables containing
-  foreign keys as if :ref:`expand_fast_index_creation` is OFF to avoid
-  dropping keys that are part of a FOREIGN KEY constraint;
-* :command:`mysqldump --innodb-optimize-keys` ignores foreign keys because
-  *InnoDB* requires a full table rebuild on foreign key changes. So adding them
-  back with a separate ``ALTER TABLE`` after restoring the data from a dump
-  would actually make the restore slower;
-* :command:`mysqldump --innodb-optimize-keys` ignores indexes on
-  ``AUTO_INCREMENT`` columns, because they must be indexed, so it is impossible
-  to temporarily drop the corresponding index;
-* :command:`mysqldump --innodb-optimize-keys` ignores the first UNIQUE index on
-  non-nullable columns when the table has no ``PRIMARY KEY`` defined, because in
-  this case *InnoDB* picks such an index as the clustered one.
-
-System Variables
-================================================================================
-
-.. _expand_fast_index_creation:
-
-.. rubric:: ``expand_fast_index_creation``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - Yes
-   * - Config file
-     - No
-   * - Scope
-     - Local/Global
-   * - Dynamic
-     - Yes
-   * - Data type
-     - Boolean
-   * - Default
-     - ON/OFF
-
-.. seealso::
-
-   Improved InnoDB fast index creation
-      http://www.mysqlperformanceblog.com/2011/11/06/improved-innodb-fast-index-creation/
-   Thinking about running OPTIMIZE on your InnoDB Table? Stop!
-      http://www.mysqlperformanceblog.com/2010/12/09/thinking-about-running-optimize-on-your-innodb-table-stop/
-
-.. include:: ../.res/replace.program.txt
diff --git a/doc/source/management/kill_idle_trx.rst b/doc/source/management/kill_idle_trx.rst
deleted file mode 100644
index d5dbc00b5ad1..000000000000
--- a/doc/source/management/kill_idle_trx.rst
+++ /dev/null
@@ -1,43 +0,0 @@
-.. _kill_idle_trx:
-
-======================
-Kill Idle Transactions
-======================
-
-This feature limits the age of idle transactions, for all transactional storage
-engines. If a transaction is idle for more seconds than the threshold
-specified, it will be killed. This prevents users from blocking *InnoDB* purge
-by mistake.
-
-Version Specific Information
-============================
-
-  * `8.0.12-1`: The feature was ported from *Percona Server for MySQL* 5.7.
-
-System Variables
-================
-
-.. _kill_idle_transaction:
-
-.. rubric:: ``kill_idle_transaction``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Config file
-     - Yes
-   * - Scope
-     - Global
-   * - Dynamic
-     - Yes
-   * - Data type
-     - Integer
-   * - Default
-     - 0 (disabled)
-   * - Units
-     - Seconds
-   
-If non-zero, any idle transaction will be killed after being idle for this many seconds.
-
diff --git a/doc/source/management/pam_plugin.rst b/doc/source/management/pam_plugin.rst
deleted file mode 100644
index f3779c43de86..000000000000
--- a/doc/source/management/pam_plugin.rst
+++ /dev/null
@@ -1,11 +0,0 @@
-
-
-===========================
- PAM Authentication Plugin
-===========================
-
-This page has been moved or been replaced. The new page is located here:
-
-:ref:`pam_plugin`
-
-Please update any bookmarks that point to the old page.
diff --git a/doc/source/management/start_transaction_with_consistent_snapshot.rst b/doc/source/management/start_transaction_with_consistent_snapshot.rst
deleted file mode 100644
index 6ae06252986e..000000000000
--- a/doc/source/management/start_transaction_with_consistent_snapshot.rst
+++ /dev/null
@@ -1,93 +0,0 @@
-.. _start_transaction_with_consistent_snapshot:
-
-============================================
- Start transaction with consistent snapshot
-============================================
-
-*Percona Server for MySQL* has ported *MariaDB* `enhancement <https://mariadb.com/kb/en/enhancements-for-start-transaction-with-consistent/>`_ for ``START TRANSACTION WITH CONSISTENT SNAPSHOTS`` feature to *MySQL* 5.6 group commit implementation. This enhancement makes binary log positions consistent with *InnoDB* transaction snapshots.
-
-This feature is quite useful to obtain logical backups with correct positions without running a ``FLUSH TABLES WITH READ LOCK``. Binary log position can be obtained by two newly implemented status variables: :ref:`Binlog_snapshot_file` and :ref:`Binlog_snapshot_position`. After starting a transaction using the ``START TRANSACTION WITH CONSISTENT SNAPSHOT``, these two variables will provide you with the binlog position corresponding to the state of the database of the consistent snapshot so taken, irrespectively of which other transactions have been committed since the snapshot was taken.
-
-.. _snapshot_cloning:
-
-Snapshot Cloning
-================
-
-The *Percona Server for MySQL* implementation extends the ``START TRANSACTION WITH CONSISTENT SNAPSHOT`` syntax with the optional ``FROM SESSION`` clause:
-
-.. code-block:: mysql
-
-  START TRANSACTION WITH CONSISTENT SNAPSHOT FROM SESSION <session_id>;
-
-When specified, all participating storage engines and binary log instead of creating a new snapshot of data (or binary log coordinates), create a copy of the snapshot which has been created by an active transaction in the specified session. ``session_id`` is the session identifier reported in the ``Id`` column of ``SHOW PROCESSLIST``.
-
-Currently snapshot cloning is only supported by *XtraDB* and the binary log. As with the regular ``START TRANSACTION WITH CONSISTENT SNAPSHOT``, snapshot clones can only be created with the ``REPEATABLE READ`` isolation level.
-
-For *XtraDB*, a transaction with a cloned snapshot will only see data visible or changed by the donor transaction. That is, the cloned transaction will see no changes committed by transactions that started after the donor transaction, not even changes made by itself. Note that in case of chained cloning the donor transaction is the first one in the chain. For example, if transaction A is cloned into transaction B, which is in turn cloned into transaction C, the latter will have read view from transaction A (i.e. the donor transaction). Therefore, it will see changes made by transaction A, but not by transaction B.
-
-mysqldump
-=========
-
-``mysqldump`` has been updated to use new status variables automatically when they are supported by the server and both :ref:`--single-transaction` and :ref:`--master-data` are specified on the command line. Along with the ``mysqldump`` improvements introduced in :ref:`backup_locks` there is now a way to generate ``mysqldump`` backups that are guaranteed to be consistent without using ``FLUSH TABLES WITH READ LOCK`` even if :ref:`--master-data` is requested.
-
-System Variables
-================
-
-.. _have_snapshot_cloning:
-
-.. rubric:: ``have_snapshot_cloning``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - Yes
-   * - Config file
-     - No
-   * - Scope
-     - Global
-   * - Dynamic
-     - No
-   * - Data type
-     - Boolean
-
-This server variable is implemented to help other utilities detect if the server supports the ``FROM SESSION`` extension. When available, the snapshot cloning feature and the syntax extension to ``START TRANSACTION WITH CONSISTENT SNAPSHOT`` are supported by the server, and the variable value is always ``YES``.
-
-Status Variables
-================
-
-.. _Binlog_snapshot_file:
-
-.. rubric:: ``Binlog_snapshot_file``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Scope
-     - Global
-   * - Data type
-     - String
-
-.. _Binlog_snapshot_position:
-
-.. rubric:: ``Binlog_snapshot_position``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Scope
-     - Global
-   * - Data type
-     - Numeric
-
-These status variables are only available when the binary log is enabled globally.
-
-Other Reading
-=============
-* `MariaDB Enhancements for START TRANSACTION WITH CONSISTENT SNAPSHOT <https://mariadb.com/kb/en/enhancements-for-start-transaction-with-consistent/>`_
diff --git a/doc/source/management/udf_percona_toolkit.rst b/doc/source/management/udf_percona_toolkit.rst
deleted file mode 100644
index 0640a043f862..000000000000
--- a/doc/source/management/udf_percona_toolkit.rst
+++ /dev/null
@@ -1,49 +0,0 @@
-.. _udf_percona_toolkit:
-
-========================
- *Percona Toolkit* UDFs
-========================
-
-Three *Percona Toolkit* UDFs that provide faster checksums are provided:
-
-  * ``libfnv1a_udf``
-
-  * ``libfnv_udf``
-
-  * ``libmurmur_udf``
-
-Version Specific Information
-============================
-
-  * `8.0.12-1`: The feature was ported from *Percona Server for MySQL* 5.7.
-
-Other Information
-=================
-
-  * Author / Origin:
-    Baron Schwartz
-
-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: ::
-
-  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'"
-
-Executing each of these commands will install its respective UDF into the server.
-
-Troubleshooting
-================
-
-If you get the error: :: 
-
-  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)
-
-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``.
-
-Other Reading
-=============
-
-  * *Percona Toolkit* `documentation <http://www.percona.com/doc/percona-toolkit/>`_
diff --git a/doc/source/management/utility_user.rst b/doc/source/management/utility_user.rst
deleted file mode 100644
index efdc735161c3..000000000000
--- a/doc/source/management/utility_user.rst
+++ /dev/null
@@ -1,217 +0,0 @@
-.. _psaas_utility_user:
-
-==============
- Utility user
-==============
-
-*Percona Server for MySQL* has implemented ability to have a *MySQL* user who has system access to do administrative tasks but limited access to user schema. This feature is especially useful to those operating *MySQL* As A Service. 
-
-This user has a mixed and special scope of abilities and protection:
-
-  * Utility user will not appear in the mysql.user table and can not be modified by any other user, including root.
-
-  * Utility user will not appear in :ref:`USER_STATISTICS`, :ref:`CLIENT_STATISTICS` or :ref:`THREAD_STATISTICS` tables or in any `performance_schema tables <https://dev.mysql.com/doc/dev/mysql-server/latest/group__performance__schema__tables.html>`__.
-
-  * Utility user's queries may appear in the general and slow logs.
-
-  * Utility user doesn't have the ability create, modify, delete or see any schemas or data not specified (except for information_schema).
-
-  * Utility user may modify all visible, non read-only system variables (see `expanded_option_modifiers` functionality).
-
-  * Utility user may see, create, modify and delete other system users only if given access to the mysql schema.
-
-  * Regular users may be granted proxy rights to the utility user but any attempt to impersonate the utility user will fail. The utility user may not be granted proxy rights on any regular user. For example running: GRANT PROXY ON utility_user TO regular_user; will not fail, but any actual attempt to impersonate as the utility user will fail. Running: `GRANT PROXY ON regular_user TO utility_user;` will fail when utility_user is an exact match or is more specific than than the utility user specified.
-
-When the server starts, it will note in the log output that the utility user exists and the schemas that it has access to.
-
-In order to have the ability for a special type of MySQL user, which will have a very limited and special amount of control over the system and can not be see or modified by any other user including the root user, three new options have been added.
-
-Option :ref:`utility_user` specifies the user which the system will create and recognize as the utility user. The host in the utility user specification follows conventions described in the `MySQL manual <http://dev.mysql.com/doc/refman/5.7/en/connection-access.html>`_, i.e. it allows wildcards and IP masks. Anonymous user names are not permitted to be used for the utility user name.
-
-This user must not be an exact match to any other user that exists in the mysql.user table. If the server detects that the user specified with this option exactly matches any user within the mysql.user table on start up, the server will report an error and shut down gracefully. If host name wildcards are used and a more specific user specification is identified on start up, the server will report a warning and continue. 
-
- Example: :ref:`utility_user` =frank@% and frank@localhost exists within the mysql.user table.
-
-If a client attempts to create a MySQL user that matches this user specification exactly or if host name wildcards are used for the utility user and the user being created has the same name and a more specific host, the creation attempt will fail with an error.
-
- Example: :ref:`utility_user` =frank@% and CREATE USER 'frank@localhost';
-
-As a result of these requirements, it is strongly recommended that a very unique user name and reasonably specific host be used and that any script or tools test that they are running within the correct user by executing 'SELECT CURRENT_USER()' and comparing the result against the known utility user.
-
-Option :ref:`utility_user_password` specifies the password for the utility user and MUST be specified or the server will shut down gracefully with an error.
-
- Example: :ref:`utility_user_password` =`Passw0rD`
-
-Option :ref:`utility_user_schema_access` specifies the name(s) of the schema(s) that the utility user will have access to read write and modify. If a particular schema named here does not exist on start up it will be ignored. If a schema by the name of any of those listed in this option is created after the server is started, the utility user will have full access to it.
-
- Example: :ref:`utility_user_schema_access` =schema1,schema2,schema3
-
-Option :ref:`utility_user_privileges` allows a comma-separated list of extra access privileges to grant to the utility user.
-
- Example: :ref:`utility-user-privileges` ="CREATE,DROP,LOCK TABLES"
-
-Option :ref:`utility_user_dynamic_privileges` allows a comma-separated list of extra access dynamic privileges to grant to the utility user.
-
- Example: :ref:`utility-user-dynamic-privileges` ="SYSTEM_USER,AUDIT_ADMIN"
-
-Version Specific Information
-============================
-
-  * :ref:`8.0.17-8`: The feature was ported from *Percona Server for MySQL* 5.7.
-
-System Variables
-================
-
-.. _utility_user:
-
-.. rubric:: ``utility_user``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - Yes
-   * - Config file
-     - utility_user=<user@host>
-   * - Scope
-     - Global
-   * - Dynamic
-     - No
-   * - Data type
-     - String
-   * - Default
-     - NULL
-
-Specifies a MySQL user that will be added to the internal list of users and recognized as the utility user.
-
-.. _utility_user_password:
-
-.. rubric:: ``utility_user_password``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - Yes
-   * - Config file
-     - utility_user_password=<password>
-   * - Scope
-     - Global
-   * - Dynamic
-     - No
-   * - Data type
-     - String
-   * - Default
-     - NULL
-
-Specifies the password required for the utility user.
-
-.. _utility_user_schema_access:
-
-.. rubric:: ``utility_user_schema_access``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - Yes
-   * - Config file
-     - utility_user_schema_access=<schema>,<schema>,<schema>
-   * - Scope
-     - Global
-   * - Dynamic
-     - No
-   * - Data type
-     - String
-   * - Default
-     - NULL
-
-Specifies the schemas that the utility user has access to in a comma delimited list.
-
-.. _utility_user_privileges:
-
-.. rubric:: ``utility_user_privileges``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - Yes
-   * - Config file
-     - utility_user_privileges=<privilege1>,<privilege2>,<privilege3>
-   * - Scope
-     - Global
-   * - Dynamic
-     - No
-   * - Data type
-     - String
-   * - Default
-     - NULL
-
-This variable can be used to specify a comma-separated list of extra access privileges to grant to the utility user. Supported values for the privileges list are: ``SELECT, INSERT, UPDATE, DELETE, CREATE, DROP, RELOAD, SHUTDOWN, PROCESS, FILE, GRANT, REFERENCES, INDEX, ALTER, SHOW DATABASES, SUPER, CREATE TEMPORARY TABLES, LOCK TABLES, EXECUTE, REPLICATION SLAVE, REPLICATION CLIENT, CREATE VIEW, SHOW VIEW, CREATE ROUTINE, ALTER ROUTINE, CREATE USER, EVENT, TRIGGER, CREATE TABLESPACE``
-
-.. _utility_user_dynamic_privileges:
-
-.. rubric:: ``utility_user_dynamic_privileges``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - Yes
-   * - Config file
-     - utility_user_dynamic_privileges=<privilege1>,<privilege2>,<privilege3>
-   * - Scope
-     - Global
-   * - Dynamic
-     - No
-   * - Data type
-     - String
-   * - Default
-     - NULL
-
-This variable was implemented in :ref:`8.0.20-11`.
-
-This variable allows a comma-separated list of extra access dynamic privileges to grant to the utility user. The supported values for the dynamic privileges are:
-
-* APPLICATION_PASSWORD_ADMIN
-* AUDIT_ADMIN
-* BACKUP_ADMIN
-* BINLOG_ADMIN
-* BINLOG_ENCRYPTION_ADMIN
-* CLONE_ADMIN
-* CONNECTION_ADMIN
-* ENCRYPTION_KEY_ADMIN
-* FIREWALL_ADMIN
-* FIREWALL_USER
-* GROUP_REPLICATION_ADMIN
-* INNODB_REDO_LOG_ARCHIVE
-* NDB_STORED_USER
-* PERSIST_RO_VARIABLES_ADMIN
-* REPLICATION_APPLIER
-* REPLICATION_SLAVE_ADMIN
-* RESOURCE_GROUP_ADMIN
-* RESOURCE_GROUP_USER
-* ROLE_ADMIN 
-* SESSION_VARIABLES_ADMIN
-* SET_USER_ID
-* SHOW_ROUTINE
-* SYSTEM_USER
-* SYSTEM_VARIABLES_ADMIN
-* TABLE_ENCRYPTION_ADMIN
-* VERSION_TOKEN_ADMIN
-* XA_RECOVER_ADMIN
-
-Other dynamic privileges may be defined by plugins.
-
-
diff --git a/doc/source/myrocks/added-features.rst b/doc/source/myrocks/added-features.rst
deleted file mode 100644
index 4c3a6668c661..000000000000
--- a/doc/source/myrocks/added-features.rst
+++ /dev/null
@@ -1,21 +0,0 @@
-.. _added-features:
-
-================================================================================
-Updated Supported Features
-================================================================================
-
-The following is a list of the latest supported features:
-
-* **Percona Server for MySQL** 8.0.27-18 adds support for ``SELECT FOR UPDATE SKIP LOCKED/NOWAIT``. The transaction isolation level must be ``READ COMMITTED``.
-  
-* **Percona Server for MySQL** 8.0.27-18 adds the ability to cancel ongoing manual compactions. The cancel methods are the following:
-
-  * Using either Control+C (from a session) or KILL (from another session) for client sessions running manual compactions by ``SET GLOBAL rocksdb_compact_cf (variable)``.
-  * Using a global variable ``rocksdb_cancel_manual_compactions`` to cancel all ongoing manual compactions.
-    
-* **Percona Server for MySQL** 8.0.23-14 adds supported for `Generated Columns <https://dev.mysql.com/doc/refman/8.0/en/create-table-generated-columns.html>`_ and index are supported. Generated columns are not supported in versions earlier than 8.0.23-14.
-
-* **Percona Server for MySQL** 8.0.23-14 adds support for `explicit DEFAULT value expressions <https://dev.mysql.com/doc/refman/8.0/en/data-type-defaults.html>`__. From version 8.0.13-3 to version 8.0.22-13, MyRocks did not support these expressions.
-
-
-
diff --git a/doc/source/myrocks/column-family.rst b/doc/source/myrocks/column-family.rst
deleted file mode 100644
index c9938417d985..000000000000
--- a/doc/source/myrocks/column-family.rst
+++ /dev/null
@@ -1,92 +0,0 @@
-.. _ps.myrocks.column-family:
-
-================================================================================
-|myrocks| Column Families
-================================================================================
-
-|MyRocks| stores all data in a single server instance as a collection of
-key-value pairs within the `log structured merge tree` data structure. This is a
-flat data structure that requires that keys be unique throughout the whole data
-structure. |MyRocks| incorporates table IDs and index IDs into the keys.
-
-Each key-value pair belongs to a column family. It is a data structure similar
-in concept to tablespaces. Each column family has distinct attributes, such as
-block size, compression, sort order, and MemTable. Utilizing these attributes,
-|MyRocks| effectively uses column families to store indexes.
-
-On system initialization, |MyRocks| creates two column families.  The
-``__system__`` column family is reserved by |MyRocks|; no user created tables or
-indexes belong to this column family.  The ``default`` column family is the
-location for the indexes created by the user when you a column family is not
-explicitly specified.
-
-To be able to apply a custom block size, compression, or sort order you need to
-create an index in its own column family using the ``COMMENT`` clause.
-
-The following example demonstrates how to place the ``PRIMARY KEY`` into the
-`cf1` column family and the index ``kb`` --- into the `cf2` column family.
-
-.. code-block:: mysql
-
-   CREATE TABLE t1 (a INT, b INT,
-   PRIMARY KEY(a) COMMENT 'cfname=cf1',
-   KEY kb(b) COMMENT 'cf_name=cf2')
-   ENGINE=ROCKSDB;
-
-The column family name is specified as the value of the |cfname| attribute at
-the beginning of the |sql.comment| clause. The name is case sensitive and may not
-contain leading or trailing whitespace characters.
-
-The |sql.comment| clause may contain other information following the semicolon
-character (;) after the column family name: 'cfname=foo; special column
-family'. If the column family cannot be created, |MyRocks| uses the default
-column family.
-
-.. important::
-
-   The |cfname| attribute must be all lowercase. Place the equals sign (=) in
-   front of the column family name without any whitespace on both sides of it.
-
-   .. code-block:: mysql
-
-      COMMENT 'cfname=Foo; Creating the Foo family name'
-
-.. seealso::
-
-   Using |sql.comment| to Specify Column Family Names with Multiple Table Partitions
-      https://github.com/facebook/mysql-5.6/wiki/Column-Families-on-Partitioned-Tables.
-
-.. rubric:: Controlling the number of column families to reduce memory consumption
-   
-Each column family has its own MemTable. It is an in-memory data structure where
-data are written to before they are flushed to SST files. The queries also use
-MemTables first. To reduce the overall memory consumption, the number of active
-column families should stay low.
-
-.. Application: PS-8.0 not PS-5.7
-
-With the option |opt.no-create-column-family| set to `true`, the |sql.comment|
-clause will not treat |cfname| as a special token; it will not be possible to
-create column families using the |sql.comment| clause.
-
-.. _ps.myrocks.column-family.option:
-
-Column Family Options
-================================================================================
-
-On startup, the server applies the |opt.default-cf-options| option to all
-existing column families. You may use the |opt.override-cf-options| option to
-override the value of any attribute of a chosen column family.
-
-Note that the options |opt.dcfo| and |opt.ocfo| are read-only at runtime.
-
-At runtime, use the the |opt.update-cf-options| option to update some column
-family attributes.
-
-.. important:: 
-
-   Changes made to a column families using the |opt.update-cf-options| option
-   only persist until the server is restarted.
-
-.. include:: ../.res/replace.opt.txt
-.. include:: ../.res/replace.concept.txt
diff --git a/doc/source/myrocks/data_loading.rst b/doc/source/myrocks/data_loading.rst
deleted file mode 100644
index 097bd7010cce..000000000000
--- a/doc/source/myrocks/data_loading.rst
+++ /dev/null
@@ -1,148 +0,0 @@
-.. _data-loading:
-
-============
-Data Loading
-============
-
-By default, MyRocks configurations are optimized for short transactions,
-and not for data loading. MyRocks has a couple of special session variables
-to speed up data loading dramatically.
-
-Sorted bulk loading
-===================
-
-If your data is guaranteed to be loaded in primary key order, then this method
-is recommended. This method works by dropping any secondary keys first, loading
-data into your table in primary key order, and then restoring the secondary
-keys via Fast Secondary Index Creation.
-
-Creating Secondary Indexes
---------------------------
-
-When loading data into empty tables, it is highly recommended to drop all
-secondary indexes first, then loading data, and adding all secondary indexes
-after finishing loading data. MyRocks has a feature called ``Fast Secondary
-Index Creation``. Fast Secondary Index Creation is automatically used when
-executing ``CREATE INDEX`` or ``ALTER TABLE ... ADD INDEX``. With Fast
-Secondary Index Creation, the secondary index entries are directly written
-to bottommost RocksDB levels and bypassing compaction. This significantly
-reduces total write volume and CPU time for decompressing and compressing
-data on higher levels.
-
-.. _myrocks_data_loading:
-
-Loading Data
-------------
-
-As described above, loading data is highly recommended for tables with primary
-key only (no secondary keys), with all secondary indexes added after loading
-data.
-
-When loading data into MyRocks tables, there are two recommended session
-variables:
-
-.. code-block:: mysql
-
-  SET session sql_log_bin=0;
-  SET session rocksdb_bulk_load=1;
-
-When converting from large MyISAM/InnoDB tables, either by using the ``ALTER``
-or ``INSERT INTO SELECT`` statements it's recommended that you
-create MyRocks tables as below (in case the table is sufficiently big it will
-cause the server to consume all the memory and then be terminated by the OOM
-killer):
-
-.. code-block:: mysql
-
-  SET session sql_log_bin=0;
-  SET session rocksdb_bulk_load=1;
-  ALTER TABLE large_myisam_table ENGINE=RocksDB;
-  SET session rocksdb_bulk_load=0;
-
-Using sql_log_bin=0 avoids writing to binary logs.
-
-With :ref:`rocksdb_bulk_load` set to ``1``, MyRocks enters special mode to
-write all inserts into bottommost RocksDB levels, and skips writing data into
-MemTable and the following compactions. This is very efficient way to load
-data.
-
-The :ref:`rocksdb_bulk_load` mode operates with a few conditions:
-
-* None of the data being bulk loaded can overlap with existing data in the
-  table. The easiest way to ensure this is to always bulk load into an empty
-  table, but the mode will allow loading some data into the table, doing other
-  operations, and then returning and bulk loading addition data if there is no
-  overlap between what is being loaded and what already exists.
-
-* The data may not be visible until bulk load mode is ended (i.e. the
-  :ref:`rocksdb_bulk_load` is set to zero again). The method that is used
-  is building up SST files which will later be added as-is to the database.
-  Until a particular SST has been added the data will not be visible to the
-  rest of the system, thus issuing a ``SELECT`` on the table currently being
-  bulk loaded will only show older data and will likely not show the most
-  recently added rows. Ending the bulk load mode will cause the most recent SST
-  file to be added. When bulk loading multiple tables, starting a new table
-  will trigger the code to add the most recent SST file to the system -- as a
-  result, it is inadvisable to interleave ``INSERT`` statements to two or more
-  tables during bulk load mode.
-
-By default, the :ref:`rocksdb_bulk_load` mode expects all data be inserted
-in primary key order (or reversed order). If the data is in the reverse order
-(i.e. the data is descending on a normally ordered primary key or is ascending
-on a reverse ordered primary key), the rows are cached in chunks to switch the
-order to match the expected order.
-
-Inserting one or more rows out of order will result in an error and may result
-in some of the data being inserted in the table and some not. To resolve the
-problem, one can either fix the data order of the insert, truncate the table,
-and restart.
-
-Unsorted bulk loading
-=====================
-
-If your data is not ordered in primary key order, then this method is
-recommended. With this method, secondary keys do not need to be dropped and
-restored. However, writing to the primary key no longer goes directly to SST
-files, and are written to temporary files for sorted first, so there is extra
-cost to this method.
-
-To allow for loading unsorted data:
-
-.. code-block:: mysql
-
-  SET session sql_log_bin=0;
-  SET session rocksdb_bulk_load_allow_unsorted=1;
-  SET session rocksdb_bulk_load=1;
-  ...
-  SET session rocksdb_bulk_load=0;
-  SET session rocksdb_bulk_load_allow_unsorted=0;
-
-Note that :ref:`rocksdb_bulk_load_allow_unsorted` can only be changed when
-:ref:`rocksdb_bulk_load` is disabled (set to ``0``). In this case, all
-input data will go through an intermediate step that writes the rows to
-temporary SST files, sorts them rows in the primary key order, and then writes
-to final SST files in the correct order.
-
-Other Approaches
-================
-
-If :ref:`rocksdb_commit_in_the_middle` is enabled, MyRocks implicitly
-commits every :ref:`rocksdb_bulk_load_size` records (default is ``1,000``)
-in the middle of your transaction. If your data loading fails in the middle of
-the statement (``LOAD DATA`` or bulk ``INSERT``), rows are not entirely rolled
-back, but some of rows are stored in the table. To restart data loading, you'll
-need to truncate the table and loading data again.
-
-.. warning::
-
-  If you are loading large data without enabling :ref:`rocksdb_bulk_load`
-  or :ref:`rocksdb_commit_in_the_middle`, please make sure transaction
-  size is small enough. All modifications of the ongoing transactions are kept
-  in memory.
-
-Other Reading
-=============
-* `Data Loading <https://github.com/facebook/mysql-5.6/wiki/Data-Loading>`_ -
-  this document has been used as a source for writing this documentation
-* `ALTER TABLE ... ENGINE=ROCKSDB uses too much memory
-  <https://github.com/facebook/mysql-5.6/issues/692>`_
diff --git a/doc/source/myrocks/differences.rst b/doc/source/myrocks/differences.rst
deleted file mode 100644
index e54a668330e9..000000000000
--- a/doc/source/myrocks/differences.rst
+++ /dev/null
@@ -1,35 +0,0 @@
-.. _myrocks_differences:
-
-========================================================
-Differences between Percona MyRocks and Facebook MyRocks
-========================================================
-
-The original MyRocks was developed by Facebook
-and works with their implementation of MySQL.
-*Percona MyRocks* is a branch of MyRocks for |Percona Server|
-and includes the following differences from the original implementation:
-
-* The behavior of the ``START TRANSACTION WITH CONSISTENT SNAPSHOT`` statement
-  depends on the `transaction isolation level
-  <https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html>`_.
-
-  +------------------+------------------------------------------------------+
-  | Storage Engine   |      Transaction isolation level                     |
-  |                  +--------------------+---------------------------------+
-  |                  | ``READ COMMITTED`` | ``REPEATABLE READ``             |
-  +------------------+--------------------+---------------------------------+
-  | InnoDB           | Success            | Success                         |
-  +------------------+--------------------+---------------------------------+
-  | Facebook MyRocks | Fail               | Success                         |
-  |                  |                    | (MyRocks engine only; read-only,|
-  |                  |                    | as all MyRocks engine snapshots)|
-  +------------------+--------------------+---------------------------------+
-  | Percona MyRocks  | Fail with any DML  | Success                         |
-  |                  | which would violate| (read-only snapshots independent|
-  |                  | the read-only      | of the engines in use)          |
-  |                  | snapshot constraint|                                 |
-  +------------------+--------------------+---------------------------------+
-
-* Percona MyRocks includes the ``lz4`` and ``zstd``
-  statically linked libraries.
-
diff --git a/doc/source/myrocks/gap_locks_detection.rst b/doc/source/myrocks/gap_locks_detection.rst
deleted file mode 100644
index 37186279f808..000000000000
--- a/doc/source/myrocks/gap_locks_detection.rst
+++ /dev/null
@@ -1,20 +0,0 @@
-.. _gap_locks_detection:
-
-===================
-Gap locks detection
-===================
-
-The `Gap locks
-<https://dev.mysql.com/doc/refman/8.0/en/innodb-locking.html#innodb-gap-locks>`_
-detection is based on a Facebook *MySQL* patch.
-
-If a transactional storage engine does not support gap locks (for example
-MyRocks) and a gap lock is being attempted while the transaction isolation
-level is either ``REPEATABLE READ`` or ``SERIALIZABLE``, the following SQL
-error will be returned to the client and no actual gap lock will be taken
-on the effected rows.
-
-.. code-block:: mysql
-
-  ERROR HY000: Using Gap Lock without full unique key in multi-table or multi-statement transactions is not allowed. You need to either rewrite queries to use all unique key columns in WHERE equal conditions, or rewrite to single-table, single-statement transaction.
-
diff --git a/doc/source/myrocks/index.rst b/doc/source/myrocks/index.rst
deleted file mode 100644
index 8570aede0e2f..000000000000
--- a/doc/source/myrocks/index.rst
+++ /dev/null
@@ -1,33 +0,0 @@
-.. _myrocks_intro:
-
-============================
-Percona MyRocks Introduction
-============================
-
-`MyRocks <http://myrocks.io>`_ is a storage engine
-for `MySQL <https://www.mysql.com>`_ based on `RocksDB <http://rocksdb.org/>`_,
-an embeddable, persistent key-value store.
-*Percona MyRocks* is an implementation
-for `Percona Server for MySQL <https://www.percona.com/software/percona-server>`_.
-
-The RocksDB store is based on the log-structured merge-tree (or LSM
-tree). It is optimized for fast storage and combines outstanding
-space and write efficiency with acceptable read performance. As a
-result, MyRocks has the following advantages compared to other storage
-engines, if your workload uses fast storage, such as SSD:
-
-* Requires less storage space
-* Provides more storage endurance
-* Ensures better IO capacity
-
-.. toctree::
-   :maxdepth: 1
-
-   install
-   limitations
-   differences
-   column-family
-   variables
-   information-schema-tables
-   performance-schema-tables
-
diff --git a/doc/source/myrocks/information-schema-tables.rst b/doc/source/myrocks/information-schema-tables.rst
deleted file mode 100644
index 2a0af4741f82..000000000000
--- a/doc/source/myrocks/information-schema-tables.rst
+++ /dev/null
@@ -1,377 +0,0 @@
-.. _ps.myrocks.information-schema-table:
-
-================================================================================
-|myrocks| |information-schema| Tables
-================================================================================
-
-When you install the |myrocks| plugin for |MySQL|, the
-|information-schema| is extended to include the following tables:
-
-.. contents::
-   :local:
-   :depth: 1
-
-.. _ps.myrocks.information-schema-table.rocksdb-global-info:
-
-ROCKSDB_GLOBAL_INFO
-================================================================================
-
-.. rubric:: Columns
-
-.. list-table::
-   :header-rows: 1
-
-   * - Column Name
-     - Type
-   * - TYPE
-     - varchar(513)
-   * - NAME
-     - varchar(513)
-   * - VALUE
-     - varchar(513)
-
-.. _ps.myrocks.information-schema-table.rocksdb-cfstats:
-
-ROCKSDB_CFSTATS
-================================================================================
-
-.. rubric:: Columns
-
-.. list-table::
-   :header-rows: 1
-
-   * - Column Name
-     - Type
-   * - CF_NAME
-     - varchar(193)
-   * - STAT_TYPE
-     - varchar(193)
-   * - VALUE
-     - bigint(8) 
-
-.. _ps.myrocks.information-schema-table.rocksdb-trx:
-
-ROCKSDB_TRX
-================================================================================
-
-This table stores mappings of |rocksdb| transaction identifiers to |MySQL|
-client identifiers to enable associating a |rocksdb| transaction with a |MySQL|
-client operation.
-
-.. rubric:: Columns
-
-.. list-table::
-   :header-rows: 1
-
-   * - Column Name
-     - Type
-   * - TRANSACTION_ID
-     - bigint(8)  
-   * - STATE
-     - varchar(193)
-   * - NAME
-     - varchar(193)
-   * - WRITE_COUNT
-     - bigint(8)   
-   * - LOCK_COUNT
-     - bigint(8)   
-   * - TIMEOUT_SEC
-     - int(4)      
-   * - WAITING_KEY
-     - varchar(513)
-   * - WAITING_COLUMN_FAMILY_ID
-     - int(4)      
-   * - IS_REPLICATION
-     - int(4)      
-   * - SKIP_TRX_API
-     - int(4)      
-   * - READ_ONLY
-     - int(4)      
-   * - HAS_DEADLOCK_DETECTION
-     - int(4)      
-   * - NUM_ONGOING_BULKLOAD
-     - int(4)      
-   * - THREAD_ID
-     - int(8)      
-   * - QUERY
-     - varchar(193)
-   
-.. _ps.myrocks.information-schema-table.rocksdb-cf-options:
-
-ROCKSDB_CF_OPTIONS
-================================================================================
-
-.. rubric:: Columns
-
-.. list-table::
-   :header-rows: 1
-
-   * - Column Name
-     - Type
-   * - CF_NAME
-     - varchar(193)
-   * - OPTION_TYPE
-     - varchar(193)
-   * - VALUE
-     - varchar(193)
-
-.. _ps.myrocks.information-schema-table.rocksdb-active-compaction-stats:
-
-ROCKSDB_ACTIVE_COMPACTION_STATS
-================================================================================
-
-.. rubric:: Columns
-
-.. list-table::
-   :header-rows: 1
-
-   * - Column Name
-     - Type
-   * - THREAD_ID
-     - bigint
-   * - CF_NAME
-     - varchar(513)
-   * - INPUT_FILES
-     - varchar(513)
-   * - OUTPUT_FILES
-     - varchar(513)
-   * - COMPACTION_REASON
-     - varchar(513)
-
-.. _ps.myrocks.information-schema-table.rocksdb-compaction-history:
-
-ROCKSDB_COMPACTION_HISTORY
-================================================================================
-
-.. rubric:: Columns
-
-.. list-table:: 
-   :header-rows: 1
-
-   * - Column Name
-     - Type
-   * - THREAD_ID
-     - bigint
-   * - CF_NAME
-     - varchar(513)
-   * - INPUT_LEVEL
-     - integer
-   * - OUTPUT_LEVEL
-     - integer
-   * - INPUT_FILES
-     - varchar(513)
-   * - OUTPUT_FILES
-     - varchar(513)
-   * - COMPACTION_REASON
-     - varchar(513)
-   * - START_TIMESTAMP
-     - bigint
-   * - END_TIMESTAMP
-     - bigint
-
-.. _ps.myrocks.information-schema-table.rocksdb-compaction-stats:
-
-ROCKSDB_COMPACTION_STATS
-================================================================================
-
-.. rubric:: Columns
-
-.. list-table::
-   :header-rows: 1
-
-   * - Column Name
-     - Type
-   * - CF_NAME
-     - varchar(193)
-   * - LEVEL
-     - varchar(513)
-   * - TYPE
-     - varchar(513)
-   * - VALUE
-     - double         
-
-
-.. _ps.myrocks.information-schema-table.rocksdb-dbstats:
-
-ROCKSDB_DBSTATS
-================================================================================
-
-.. rubric:: Columns
-
-.. list-table::
-   :header-rows: 1
-
-   * - Column Name
-     - Type
-   * - STAT_TYPE
-     - varchar(193)
-   * - VALUE
-     - bigint(8)
-
-.. _ps.myrocks.information-schema-table.rocksdb-ddl:
-
-ROCKSDB_DDL
-================================================================================
-
-.. rubric:: Columns
-
-.. list-table::
-   :header-rows: 1
-
-   * - Column Name
-     - Type
-   * - TABLE_SCHEMA
-     - varchar(193)       
-   * - TABLE_NAME
-     - varchar(193)       
-   * - PARTITION_NAME
-     - varchar(193)       
-   * - INDEX_NAME
-     - varchar(193)       
-   * - COLUMN_FAMILY
-     - int(4)             
-   * - INDEX_NUMBER
-     - int(4)             
-   * - INDEX_TYPE
-     - smallint(2)        
-   * - KV_FORMAT_VERSION
-     - smallint(2)        
-   * - TTL_DURATION
-     - bigint(8)          
-   * - INDEX_FLAGS
-     - bigint(8)          
-   * - CF
-     - varchar(193)       
-   * - AUTO_INCREMENT
-     - bigint(8) unsigned
-
-.. _ps.myrocks.information-schema-table.rocksdb-index-file-map:
-
-ROCKSDB_INDEX_FILE_MAP
-================================================================================
-
-.. rubric:: Columns
-
-.. list-table::
-   :header-rows: 1
-
-   * - Column Name
-     - Type
-   * - COLUMN_FAMILY
-     - int(4)
-   * - INDEX_NUMBER
-     - int(4)
-   * - SST_NAME
-     - varchar(193)
-   * - NUM_ROWS
-     - bigint(8)
-   * - DATA_SIZE
-     - bigint(8)
-   * - ENTRY_DELETES
-     - bigint(8)
-   * - ENTRY_SINGLEDELETES
-     - bigint(8)
-   * - ENTRY_MERGES
-     - bigint(8)
-   * - ENTRY_OTHERS
-     - bigint(8)
-   * - DISTINCT_KEYS_PREFIX
-     - varchar(400)
-   
-.. _ps.myrocks.information-schema-table.rocksdb-locks:
-
-ROCKSDB_LOCKS
-================================================================================
-
-This table contains the set of locks granted to |myrocks| transactions.
-
-.. rubric:: Columns
-
-.. list-table::
-   :header-rows: 1
-
-   * - Column Name
-     - Type
-   * - COLUMN_FAMILY_ID
-     - int(4)
-   * - TRANSACTION_ID
-     - int(4)
-   * - KEY
-     - varchar(513)
-   * - MODE
-     - varchar(32)
-
-.. _ps.myrocks.information-schema-table.rocksdb-perf-context:
-
-ROCKSDB_PERF_CONTEXT
-================================================================================
-
-.. rubric:: Columns
-
-.. list-table::
-   :header-rows: 1
-
-   * - Column Name
-     - Type
-   * - TABLE_SCHEMA
-     - varchar(193)
-   * - TABLE_NAME
-     - varchar(193)
-   * - PARTITION_NAME
-     - varchar(193)
-   * - STAT_TYPE
-     - varchar(193)
-   * - VALUE
-     - bigint(8) 
-   
-.. _ps.myrocks.information-schema-table.rocksdb-perf-context-global:
-
-ROCKSDB_PERF_CONTEXT_GLOBAL
-================================================================================
-
-.. rubric:: Columns
-
-.. list-table::
-   :header-rows: 1
-
-   * - Column Name
-     - Type
-   * - STAT_TYPE
-     - varchar(193)
-   * - VALUE
-     - bigint(8)
-
-.. _ps.myrocks.information-schema-table.rocksdb-deadlock:
-
-ROCKSDB_DEADLOCK
-================================================================================
-
-This table records information about deadlocks.
-
-.. rubric:: Columns
-
-.. list-table::
-   :header-rows: 1
-
-   * - Column Name
-     - Type
-   * - DEADLOCK_ID
-     - bigint(8)
-   * - TRANSACTION_ID
-     - bigint(8)
-   * - CF_NAME
-     - varchar(193)
-   * - WAITING_KEY
-     - varchar(513)
-   * - LOCK_TYPE
-     - varchar(193)
-   * - INDEX_NAME
-     - varchar(193)
-   * - TABLE_NAME
-     - varchar(193)
-   * - ROLLED_BACK
-     - bigint(8) 
-
-.. |myrocks| replace:: MyRocks
-.. |rocksdb| replace:: RocksDB
-.. |information-schema| replace:: Information Schema
diff --git a/doc/source/myrocks/install.rst b/doc/source/myrocks/install.rst
deleted file mode 100644
index 64f3ba53cbb8..000000000000
--- a/doc/source/myrocks/install.rst
+++ /dev/null
@@ -1,191 +0,0 @@
-.. _myrocks_install:
-
-==================================
-Percona MyRocks Installation Guide
-==================================
-
-Percona MyRocks is distributed as a separate package that can be enabled as a
-plugin for |Percona Server| 8.0 and later versions.
-
-.. note::
-
-   File formats across different MyRocks variants may not be compatible.
-   |Percona Server| supports only *Percona MyRocks*.  Migrating from one variant
-   to another requires a logical data dump and reload.
-
-.. contents::
-   :local:
-
-.. _myrocks-install:
-
-Installing Percona MyRocks
-==========================
-
-It is recommended to install Percona software from official repositories:
-
-1. Configure Percona repositories as described in
-   `Percona Software Repositories Documentation
-   <https://www.percona.com/doc/percona-repo-config/index.html>`_.
-
-#. Install Percona MyRocks using the corresponding package manager:
-
-   * For Debian or Ubuntu::
-
-      $ sudo apt install percona-server-rocksdb
-      
-     .. note::
-     
-       Review the :ref:`zenfs` document for the :ref:`zenfs-installation` and the :ref:`zenfs-configure` information.
-     
-      
-   * For RHEL or CentOS::
-
-      $ sudo yum install percona-server-rocksdb
-      
-After installation, you should see the following output::
-
-* This release of |Percona Server| is distributed with RocksDB storage engine.
-* Run the following script to enable the RocksDB storage engine in Percona Server:
-
-  .. code-block:: bash
-
-     $ ps-admin --enable-rocksdb -u <mysql_admin_user> -p[mysql_admin_pass] [-S <socket>] [-h <host> -P <port>]
-
-Run the ``ps-admin`` script as system root user or with :program:`sudo`
-and provide the MySQL root user credentials
-to properly enable the RocksDB (MyRocks) storage engine:
-
-.. code-block:: bash
-
-   $ sudo ps-admin --enable-rocksdb -u root -pPassw0rd
-
-   Checking if RocksDB plugin is available for installation ...
-   INFO: ha_rocksdb.so library for RocksDB found at /usr/lib64/mysql/plugin/ha_rocksdb.so.
-
-   Checking RocksDB engine plugin status...
-   INFO: RocksDB engine plugin is not installed.
-
-   Installing RocksDB engine...
-   INFO: Successfully installed RocksDB engine plugin.
-
-.. note::
-
-   When you use the ``ps-admin`` script to enable Percona MyRocks, it
-   performs the following:
-
-   * Disables Transparent huge pages
-   * Installs and enables the RocksDB plugin
-
-If the script returns no errors,
-Percona MyRocks should be successfully enabled on the server.
-You can verify it as follows:
-
-.. code-block:: mysql
-
-   mysql> SHOW ENGINES;
-   +---------+---------+----------------------------------------------------------------------------+--------------+------+------------+
-   | Engine  | Support | Comment                                                                    | Transactions | XA   | Savepoints |
-   +---------+---------+----------------------------------------------------------------------------+--------------+------+------------+
-   | ROCKSDB | YES     | RocksDB storage engine                                                     | YES          | YES  | YES        |
-   ...
-   | InnoDB  | DEFAULT | Percona-XtraDB, Supports transactions, row-level locking, and foreign keys | YES          | YES  | YES        |
-   +---------+---------+----------------------------------------------------------------------------+--------------+------+------------+
-   10 rows in set (0.00 sec)
-
-Note that the RocksDB engine is not set to be default,
-new tables will still be created using the InnoDB (XtraDB) storage engine.
-To make RocksDB storage engine default,
-set ``default-storage-engine=rocksdb`` in the ``[mysqld]`` section
-of :file:`my.cnf` and restart |Percona Server|.
-
-Alternatively, you can add ``ENGINE=RocksDB``
-after the ``CREATE TABLE`` statement
-for every table that you create.
-
-.. rubric:: Installing MyRocks Plugins
-
-You can install MyRocks manually with a series of `INSTALL PLUGIN <https://dev.mysql.com/doc/refman/5.7/en/install-plugin.html>`_ statements. You must have the ``INSERT`` privilege for the ``mysql.plugin`` system table.
-
-The following statements install MyRocks:
-
-.. code-block:: mysql
-
-    INSTALL PLUGIN ROCKSDB SONAME 'ha_rocksdb.so';
-    INSTALL PLUGIN ROCKSDB_CFSTATS SONAME 'ha_rocksdb.so';
-    INSTALL PLUGIN ROCKSDB_DBSTATS SONAME 'ha_rocksdb.so';
-    INSTALL PLUGIN ROCKSDB_PERF_CONTEXT SONAME 'ha_rocksdb.so';
-    INSTALL PLUGIN ROCKSDB_PERF_CONTEXT_GLOBAL SONAME 'ha_rocksdb.so';
-    INSTALL PLUGIN ROCKSDB_CF_OPTIONS SONAME 'ha_rocksdb.so';
-    INSTALL PLUGIN ROCKSDB_GLOBAL_INFO SONAME 'ha_rocksdb.so';
-    INSTALL PLUGIN ROCKSDB_COMPACTION_HISTORY SONAME 'ha_rocksdb.so';
-    INSTALL PLUGIN ROCKSDB_COMPACTION_STATS SONAME 'ha_rocksdb.so';
-    INSTALL PLUGIN ROCKSDB_ACTIVE_COMPACTION_STATS SONAME 'ha_rocksdb.so';
-    INSTALL PLUGIN ROCKSDB_DDL SONAME 'ha_rocksdb.so';
-    INSTALL PLUGIN ROCKSDB_INDEX_FILE_MAP SONAME 'ha_rocksdb.so';
-    INSTALL PLUGIN ROCKSDB_LOCKS SONAME 'ha_rocksdb.so';
-    INSTALL PLUGIN ROCKSDB_TRX SONAME 'ha_rocksdb.so';
-    INSTALL PLUGIN ROCKSDB_DEADLOCK SONAME 'ha_rocksdb.so';
-
-Removing Percona MyRocks
-========================
-
-It will not be possible to access tables created using the RocksDB engine
-with another storage engine after you remove Percona MyRocks.
-If you need this data, alter the tables to another storage engine.
-For example, to alter the ``City`` table to InnoDB, run the following:
-
-.. code-block:: mysql
-
-   mysql> ALTER TABLE City ENGINE=InnoDB;
-
-To disable and uninstall the RocksDB engine plugins,
-use the ``ps-admin`` script as follows:
-
-.. code-block:: bash
-
-   $ sudo ps-admin --disable-rocksdb -u root -pPassw0rd
-
-   Checking RocksDB engine plugin status...
-   INFO: RocksDB engine plugin is installed.
-
-   Uninstalling RocksDB engine plugin...
-   INFO: Successfully uninstalled RocksDB engine plugin.
-
-After the engine plugins have been uninstalled,
-remove the Percona MyRocks package:
-
-* For Debian or Ubuntu::
-
-  $ sudo apt remove percona-server-rocksdb-8.0
-
-* For RHEL or CentOS::
-
-  $ sudo yum remove percona-server-rocksdb-80.x86_64
-
-Finally, remove all the :ref:`myrocks_server_variables`
-from the configuration file (:file:`my.cnf`)
-and restart |Percona Server|.
-
-.. rubric:: Uninstall MyRocks Plugins
-
-You can `uninstall the plugins <https://dev.mysql.com/doc/refman/5.7/en/uninstall-plugin.html>`_ for MyRocks. You must have the ``DELETE`` privilege for the ``mysql.plugin`` system table.
-
-The following statements remove the MyRocks plugins:
-
-.. code-block:: mysql
-
-    UNINSTALL PLUGIN ROCKSDB;
-    UNINSTALL PLUGIN ROCKSDB_CFSTATS;
-    UNINSTALL PLUGIN ROCKSDB_DBSTATS;
-    UNINSTALL PLUGIN ROCKSDB_PERF_CONTEXT;
-    UNINSTALL PLUGIN ROCKSDB_PERF_CONTEXT_GLOBAL;
-    UNINSTALL PLUGIN ROCKSDB_CF_OPTIONS;
-    UNINSTALL PLUGIN ROCKSDB_GLOBAL_INFO;
-    UNINSTALL PLUGIN ROCKSDB_COMPACTION_HISTORY;
-    UNINSTALL PLUGIN ROCKSDB_COMPACTION_STATS;
-    UNINSTALL PLUGIN ROCKSDB_ACTIVE_COMPACTION_STATS;
-    UNINSTALL PLUGIN ROCKSDB_DDL;
-    UNINSTALL PLUGIN ROCKSDB_INDEX_FILE_MAP;
-    UNINSTALL PLUGIN ROCKSDB_LOCKS;
-    UNINSTALL PLUGIN ROCKSDB_TRX;
-    UNINSTALL PLUGIN ROCKSDB_DEADLOCK;
diff --git a/doc/source/myrocks/limitations.rst b/doc/source/myrocks/limitations.rst
deleted file mode 100644
index 783a53016029..000000000000
--- a/doc/source/myrocks/limitations.rst
+++ /dev/null
@@ -1,118 +0,0 @@
-.. _myrocks_limitations:
-
-===================
-MyRocks Limitations
-===================
-
-The MyRocks storage engine lacks the following features compared to InnoDB:
-
-* `Online DDL <https://dev.mysql.com/doc/refman/8.0/en/innodb-online-ddl.html>`_ is not supported due to the lack of atomic DDL support.
-    - There is no ``ALTER TABLE ... ALGORITHM=INSTANT`` functionality
-    - A partition management operation only supports the ``COPY`` algorithms, which rebuilds the partition table and moves the data based on the new ``PARTITION ... VALUE`` definition. In the case of ``DROP PARTITION``, the data not moved to another partition is deleted.
-* `ALTER TABLE .. EXCHANGE PARTITION <https://dev.mysql.com/doc/refman/8.0/en/partitioning-management-exchange.html>`_.
-* `SAVEPOINT <https://dev.mysql.com/doc/refman/8.0/en/savepoint.html>`_
-* `Transportable tablespace <https://dev.mysql.com/doc/refman/8.0/en/innodb-table-import.html>`_
-* `Foreign keys <https://dev.mysql.com/doc/refman/8.0/en/create-table-foreign-keys.html>`_
-* `Spatial indexes <https://dev.mysql.com/doc/refman/8.0/en/using-spatial-indexes.html>`_
-* `Fulltext indexes <https://dev.mysql.com/doc/refman/8.0/en/innodb-fulltext-index.html>`_
-* `Gap locks <https://dev.mysql.com/doc/refman/8.0/en/innodb-locking.html#innodb-gap-locks>`_
-* `Group Replication <https://dev.mysql.com/doc/refman/8.0/en/group-replication.html>`_
-* `Partial Update of LOB in InnoDB <https://mysqlserverteam.com/mysql-8-0-optimizing-small-partial-update-of-lob-in-innodb/>`_
-    
-
-
-You should also consider the following:
-
-* :file:`*_bin` (e.g. ``latin1_bin``) or binary collation should be used
-  on ``CHAR`` and ``VARCHAR`` indexed columns.
-  By default, MyRocks prevents creating indexes with non-binary collations
-  (including ``latin1``).
-  You can optionally use it by setting
-  :ref:`rocksdb_strict_collation_exceptions` to ``t1``
-  (table names with regex format),
-  but non-binary covering indexes other than ``latin1``
-  (excluding ``german1``) still require a primary key lookup
-  to return the ``CHAR`` or ``VARCHAR`` column.
-
-* Either ``ORDER BY DESC`` or ``ORDER BY ASC`` is slow.
-  This is because of "Prefix Key Encoding" feature in RocksDB.
-  See http://www.slideshare.net/matsunobu/myrocks-deep-dive/58 for details.
-  By default, ascending scan is faster and descending scan is slower.
-  If the "reverse column family" is configured,
-  then descending scan will be faster and ascending scan will be slower.
-  Note that InnoDB also imposes a cost
-  when the index is scanned in the opposite order.
-  
-  
-* When converting from large MyISAM/InnoDB tables, either by using the
-  ``ALTER`` or ``INSERT INTO SELECT`` statements it's recommended that you
-  check the :ref:`Data loading <myrocks_data_loading>` documentation and
-  create MyRocks tables as below (in case the table is sufficiently big it will
-  cause the server to consume all the memory and then be terminated by the OOM
-  killer):
-
-
-  .. code-block:: mysql
-
-    SET session sql_log_bin=0;
-    SET session rocksdb_bulk_load=1;
-    ALTER TABLE large_myisam_table ENGINE=RocksDB;
-    SET session rocksdb_bulk_load=0;
-
-   .. warning::
-
-    If you are loading large data without enabling :ref:`rocksdb_bulk_load`
-    or :ref:`rocksdb_commit_in_the_middle`, please make sure transaction
-    size is small enough. All modifications of the ongoing transactions are
-    kept in memory.
-
-* With partitioned tables that use the *TokuDB* or *MyRocks* storage engine,
-  the upgrade only works with native partitioning.
-
-  .. seealso::
-
-     *MySQL* Documentation: Preparing Your Installation for Upgrade
-        https://dev.mysql.com/doc/refman/8.0/en/upgrade-prerequisites.html
-
-.. include:: ../.res/replace.concept.txt
-
-* **Percona Server for MySQL** 8.0 and Unicode 9.0.0 standards have defined a change in the
-  handling of binary collations. These collations are handled as NO PAD,
-  trailing spaces are included in key comparisons. A binary collation comparison
-  may result in two unique rows inserted and does not generate a`DUP_ENTRY`
-  error. MyRocks key encoding and comparison does not account for this
-  character set attribute.
-
-
-Not Supported on MyRocks
-============================================
-
-MyRocks does not support the following:
-
-* Operating as either a source or a replica
-  in any replication topology that is not exclusively row-based.
-  Statement-based and mixed-format binary logging is not supported.
-  For more information, see `Replication Formats
-  <https://dev.mysql.com/doc/refman/8.0/en/replication-formats.html>`_.
-
-* Using `multi-valued indexes <https://dev.mysql.com/doc/refman/8.0/en/create-index.html#create-index-multi-valued>`__. Implemented in **Percona Server for MySQL** 8.0.17, InnoDB supports this feature.
-
-* Using `spatial data types <https://dev.mysql.com/doc/refman/8.0/en/spatial-type-overview.html>`__ .
-
-* Using the `Clone Plugin <https://dev.mysql.com/doc/refman/8.0/en/clone-plugin.html>`__ and the Clone Plugin API.  As of **Percona Server for MySQL** 8.0.17, InnoDB supports either these features.
-
-* Using encryption in tables. At this time, during an ``ALTER TABLE`` operation, MyRocks mistakenly detects all InnoDB tables as encrypted. Therefore, any attempt to ``ALTER`` an InnoDB table to MyRocks fails.
-
-  As a workaround, we recommend a manual move of the table. The following  steps are the same as the ``ALTER TABLE ... ENGINE=...`` process:
-
-  1. Use ``SHOW CREATE TABLE ...`` to return the InnoDB table definition.
-
-  #. With the table definition as the source, perform a ``CREATE TABLE ... ENGINE=RocksDB``.
-
-  #. In the new table, use ``INSERT INTO <new table> SELECT * FROM <old table>``.
-
-    .. note::
-
-        With MyRocks and with large tables, it is recommended to set the session variable ``rocksdb_bulk_load=1`` during the load to prevent running out of memory. This recommendation is because of the MyRocks large transaction limitation. For more information, see `MyRocks Data Loading <https://www.percona.com/doc/percona-server/8.0/myrocks/data_loading.html>`__
-    
-
diff --git a/doc/source/myrocks/performance-schema-tables.rst b/doc/source/myrocks/performance-schema-tables.rst
deleted file mode 100644
index 5f1250157ee8..000000000000
--- a/doc/source/myrocks/performance-schema-tables.rst
+++ /dev/null
@@ -1,28 +0,0 @@
-.. _performance_schema_tables:
-
--------------------------------------------------------------------------------
-Performance Schema MyRocks changes
--------------------------------------------------------------------------------
-
-.. _log_status:
-
-RocksDB WAL file information can be seen in the
-`performance_schema.log_status <https://dev.mysql.com/doc/refman/8.0/en/performance-schema-log-status-table.html>`__
-table in the ``STORAGE ENGINE`` column.
-
-This feature has been implemented in :ref:`8.0.15-6`.
-
-Example
--------------------------------------------------------------------------------
-
-.. code-block:: mysql
-
-    mysql> select * from performance_schema.log_status\G
-
-    *************************** 1. row ***************************
-
-    SERVER_UUID: f593b4f8-6fde-11e9-ad90-080027c2be11
-        LOCAL: {"gtid_executed": "", "binary_log_file": "binlog.000004", "binary_log_position": 1698222}
-    REPLICATION: {"channels": []}
-    STORAGE_ENGINES: {"InnoDB": {"LSN": 36810235, "LSN_checkpoint": 36810235}, "RocksDB": {"wal_files": [{"path_name": "/000026.log", "log_number": 26, "size_file_bytes": 371869}]}}
-    1 row in set (0.00 sec)
diff --git a/doc/source/myrocks/status_variables.rst b/doc/source/myrocks/status_variables.rst
deleted file mode 100644
index 50e626e860de..000000000000
--- a/doc/source/myrocks/status_variables.rst
+++ /dev/null
@@ -1,919 +0,0 @@
-.. _myrocks_status_variables:
-
-========================
-MyRocks Status Variables
-========================
-
-MyRocks status variables provide details
-about the inner workings of the storage engine
-and they can be useful in tuning the storage engine
-to a particular environment.
-
-You can view these variables and their values by running:
-
-.. code-block:: mysql
-
-  mysql> SHOW STATUS LIKE 'rocksdb%';
-
-The following global status variables are available:
-
-.. tabularcolumns:: |p{9cm}|p{6cm}|
-
-.. list-table::
-   :header-rows: 1
-
-   * - Name
-     - Var Type
-   * - :ref:`rocksdb_rows_deleted`
-     - Numeric
-   * - :ref:`rocksdb_rows_inserted`
-     - Numeric
-   * - :ref:`rocksdb_rows_read`
-     - Numeric
-   * - :ref:`rocksdb_rows_unfiltered_no_snapshot`
-     - Numeric
-   * - :ref:`rocksdb_rows_updated`
-     - Numeric
-   * - :ref:`rocksdb_rows_expired`
-     - Numeric
-   * - :ref:`rocksdb_system_rows_deleted`
-     - Numeric
-   * - :ref:`rocksdb_system_rows_inserted`
-     - Numeric
-   * - :ref:`rocksdb_system_rows_read`
-     - Numeric
-   * - :ref:`rocksdb_system_rows_updated`
-     - Numeric
-   * - :ref:`rocksdb_memtable_total`
-     - Numeric
-   * - :ref:`rocksdb_memtable_unflushed`
-     - Numeric
-   * - :ref:`rocksdb_queries_point`
-     - Numeric
-   * - :ref:`rocksdb_queries_range`
-     - Numeric
-   * - :ref:`rocksdb_covered_secondary_key_lookups`
-     - Numeric
-   * - :ref:`rocksdb_additional_compactions_trigger`
-     - Numeric
-   * - :ref:`rocksdb_block_cache_add`
-     - Numeric
-   * - :ref:`rocksdb_block_cache_add_failures`
-     - Numeric
-   * - :ref:`rocksdb_block_cache_bytes_read`
-     - Numeric
-   * - :ref:`rocksdb_block_cache_bytes_write`
-     - Numeric
-   * - :ref:`rocksdb_block_cache_data_add`
-     - Numeric
-   * - :ref:`rocksdb_block_cache_data_bytes_insert`
-     - Numeric
-   * - :ref:`rocksdb_block_cache_data_hit`
-     - Numeric
-   * - :ref:`rocksdb_block_cache_data_miss`
-     - Numeric
-   * - :ref:`rocksdb_block_cache_filter_add`
-     - Numeric
-   * - :ref:`rocksdb_block_cache_filter_bytes_evict`
-     - Numeric
-   * - :ref:`rocksdb_block_cache_filter_bytes_insert`
-     - Numeric
-   * - :ref:`rocksdb_block_cache_filter_hit`
-     - Numeric
-   * - :ref:`rocksdb_block_cache_filter_miss`
-     - Numeric
-   * - :ref:`rocksdb_block_cache_hit`
-     - Numeric
-   * - :ref:`rocksdb_block_cache_index_add`
-     - Numeric
-   * - :ref:`rocksdb_block_cache_index_bytes_evict`
-     - Numeric
-   * - :ref:`rocksdb_block_cache_index_bytes_insert`
-     - Numeric
-   * - :ref:`rocksdb_block_cache_index_hit`
-     - Numeric
-   * - :ref:`rocksdb_block_cache_index_miss`
-     - Numeric
-   * - :ref:`rocksdb_block_cache_miss`
-     - Numeric
-   * - :ref:`rocksdb_block_cache_compressed_hit`
-     - Numeric
-   * - :ref:`rocksdb_block_cache_compressed_miss`
-     - Numeric
-   * - :ref:`rocksdb_bloom_filter_prefix_checked`
-     - Numeric
-   * - :ref:`rocksdb_bloom_filter_prefix_useful`
-     - Numeric
-   * - :ref:`rocksdb_bloom_filter_useful`
-     - Numeric
-   * - :ref:`rocksdb_bytes_read`
-     - Numeric
-   * - :ref:`rocksdb_bytes_written`
-     - Numeric
-   * - :ref:`rocksdb_compact_read_bytes`
-     - Numeric
-   * - :ref:`rocksdb_compact_write_bytes`
-     - Numeric
-   * - :ref:`rocksdb_compaction_key_drop_new`
-     - Numeric
-   * - :ref:`rocksdb_compaction_key_drop_obsolete`
-     - Numeric
-   * - :ref:`rocksdb_compaction_key_drop_user`
-     - Numeric
-   * - :ref:`rocksdb_flush_write_bytes`
-     - Numeric
-   * - :ref:`rocksdb_get_hit_l0`
-     - Numeric
-   * - :ref:`rocksdb_get_hit_l1`
-     - Numeric
-   * - :ref:`rocksdb_get_hit_l2_and_up`
-     - Numeric
-   * - :ref:`rocksdb_get_updates_since_calls`
-     - Numeric
-   * - :ref:`rocksdb_iter_bytes_read`
-     - Numeric
-   * - :ref:`rocksdb_memtable_hit`
-     - Numeric
-   * - :ref:`rocksdb_memtable_miss`
-     - Numeric
-   * - :ref:`rocksdb_no_file_closes`
-     - Numeric
-   * - :ref:`rocksdb_no_file_errors`
-     - Numeric
-   * - :ref:`rocksdb_no_file_opens`
-     - Numeric
-   * - :ref:`rocksdb_num_iterators`
-     - Numeric
-   * - :ref:`rocksdb_number_block_not_compressed`
-     - Numeric
-   * - :ref:`rocksdb_number_db_next`
-     - Numeric
-   * - :ref:`rocksdb_number_db_next_found`
-     - Numeric
-   * - :ref:`rocksdb_number_db_prev`
-     - Numeric
-   * - :ref:`rocksdb_number_db_prev_found`
-     - Numeric
-   * - :ref:`rocksdb_number_db_seek`
-     - Numeric
-   * - :ref:`rocksdb_number_db_seek_found`
-     - Numeric
-   * - :ref:`rocksdb_number_deletes_filtered`
-     - Numeric
-   * - :ref:`rocksdb_number_keys_read`
-     - Numeric
-   * - :ref:`rocksdb_number_keys_updated`
-     - Numeric
-   * - :ref:`rocksdb_number_keys_written`
-     - Numeric
-   * - :ref:`rocksdb_number_merge_failures`
-     - Numeric
-   * - :ref:`rocksdb_number_multiget_bytes_read`
-     - Numeric
-   * - :ref:`rocksdb_number_multiget_get`
-     - Numeric
-   * - :ref:`rocksdb_number_multiget_keys_read`
-     - Numeric
-   * - :ref:`rocksdb_number_reseeks_iteration`
-     - Numeric
-   * - :ref:`rocksdb_number_sst_entry_delete`
-     - Numeric
-   * - :ref:`rocksdb_number_sst_entry_merge`
-     - Numeric
-   * - :ref:`rocksdb_number_sst_entry_other`
-     - Numeric
-   * - :ref:`rocksdb_number_sst_entry_put`
-     - Numeric
-   * - :ref:`rocksdb_number_sst_entry_singledelete`
-     - Numeric
-   * - :ref:`rocksdb_number_stat_computes`
-     - Numeric
-   * - :ref:`rocksdb_number_superversion_acquires`
-     - Numeric
-   * - :ref:`rocksdb_number_superversion_cleanups`
-     - Numeric
-   * - :ref:`rocksdb_number_superversion_releases`
-     - Numeric
-   * - :ref:`rocksdb_rate_limit_delay_millis`
-     - Numeric
-   * - :ref:`rocksdb_row_lock_deadlocks`
-     - Numeric
-   * - :ref:`rocksdb_row_lock_wait_timeouts`
-     - Numeric
-   * - :ref:`rocksdb_snapshot_conflict_errors`
-     - Numeric
-   * - :ref:`rocksdb_stall_l0_file_count_limit_slowdowns`
-     - Numeric
-   * - :ref:`rocksdb_stall_locked_l0_file_count_limit_slowdowns`
-     - Numeric
-   * - :ref:`rocksdb_stall_l0_file_count_limit_stops`
-     - Numeric
-   * - :ref:`rocksdb_stall_locked_l0_file_count_limit_stops`
-     - Numeric
-   * - :ref:`rocksdb_stall_pending_compaction_limit_stops`
-     - Numeric
-   * - :ref:`rocksdb_stall_pending_compaction_limit_slowdowns`
-     - Numeric
-   * - :ref:`rocksdb_stall_memtable_limit_stops`
-     - Numeric
-   * - :ref:`rocksdb_stall_memtable_limit_slowdowns`
-     - Numeric
-   * - :ref:`rocksdb_stall_total_stops`
-     - Numeric
-   * - :ref:`rocksdb_stall_total_slowdowns`
-     - Numeric
-   * - :ref:`rocksdb_stall_micros`
-     - Numeric
-   * - :ref:`rocksdb_wal_bytes`
-     - Numeric
-   * - :ref:`rocksdb_wal_group_syncs`
-     - Numeric
-   * - :ref:`rocksdb_wal_synced`
-     - Numeric
-   * - :ref:`rocksdb_write_other`
-     - Numeric
-   * - :ref:`rocksdb_write_self`
-     - Numeric
-   * - :ref:`rocksdb_write_timedout`
-     - Numeric
-   * - :ref:`rocksdb_write_wal`
-     - Numeric
-
-.. _rocksdb_rows_deleted:
-
-.. rubric:: ``rocksdb_rows_deleted``
-
-This variable shows the number of rows that were deleted from MyRocks tables.
-
-.. _rocksdb_rows_inserted:
-
-.. rubric:: ``rocksdb_rows_inserted``
-
-This variable shows the number of rows that were inserted into MyRocks tables.
-
-.. _rocksdb_rows_read:
-
-.. rubric:: ``rocksdb_rows_read``
-
-This variable shows the number of rows that were read from MyRocks tables.
-
-.. _rocksdb_rows_unfiltered_no_snapshot:
-
-.. rubric:: ``rocksdb_rows_unfiltered_no_snapshot``
-
-This variable shows how many reads need TTL and have no snapshot timestamp.
-
-.. _rocksdb_rows_updated:
-
-.. rubric:: ``rocksdb_rows_updated``
-
-This variable shows the number of rows that were updated in MyRocks tables.
-
-.. _rocksdb_rows_expired:
-
-.. rubric:: ``rocksdb_rows_expired``
-
-This variable shows the number of expired rows in MyRocks tables.
-
-.. _rocksdb_system_rows_deleted:
-
-.. rubric:: ``rocksdb_system_rows_deleted``
-
-This variable shows the number of rows that were deleted
-from MyRocks system tables.
-
-.. _rocksdb_system_rows_inserted:
-
-.. rubric:: ``rocksdb_system_rows_inserted``
-
-This variable shows the number of rows that were inserted
-into MyRocks system tables.
-
-.. _rocksdb_system_rows_read:
-
-.. rubric:: ``ocksdb_system_rows_read``
-
-This variable shows the number of rows that were read
-from MyRocks system tables.
-
-.. _rocksdb_system_rows_updated:
-
-.. rubric:: ``rocksdb_system_rows_updated``
-
-This variable shows the number of rows that were updated
-in MyRocks system tables.
-
-.. _rocksdb_memtable_total:
-
-.. rubric:: ``rocksdb_memtable_total``
-
-This variable shows the memory usage, in bytes, of all memtables.
-
-.. _rocksdb_memtable_unflushed:
-
-.. rubric:: ``rocksdb_memtable_unflushed``
-
-This variable shows the memory usage, in bytes, of all unflushed memtables.
-
-.. _rocksdb_queries_point:
-
-.. rubric:: ``rocksdb_queries_point``
-
-This variable shows the number of single row queries.
-
-.. _rocksdb_queries_range:
-
-.. rubric:: ``rocksdb_queries_range``
-
-This variable shows the number of multi/range row queries.
-
-.. _rocksdb_covered_secondary_key_lookups:
-
-.. rubric:: ``rocksdb_covered_secondary_key_lookups``
-
-This variable shows the number of lookups via secondary index that were able to
-return all fields requested directly from the secondary index when the
-secondary index contained a field that is only a prefix of the
-``varchar`` column.
-
-.. _rocksdb_additional_compactions_trigger:
-
-.. rubric:: ``rocksdb_additional_compactions_trigger``
-
-This variable shows the number of triggered additional compactions.
-MyRocks triggers an additional compaction if (number of deletions / number of entries) > (rocksdb_compaction_sequential_deletes / rocksdb_compaction_sequential_deletes_window)
-in the SST file.
-
-.. _rocksdb_block_cache_add:
-
-.. rubric:: ``rocksdb_block_cache_add``
-
-This variable shows the number of blocks added to block cache.
-
-.. _rocksdb_block_cache_add_failures:
-
-.. rubric:: ``rocksdb_block_cache_add_failures``
-
-This variable shows the number of failures when adding blocks to block cache.
-
-.. _rocksdb_block_cache_bytes_read:
-
-.. rubric:: ``rocksdb_block_cache_bytes_read``
-
-This variable shows the number of bytes read from cache.
-
-.. _rocksdb_block_cache_bytes_write:
-
-.. rubric:: ``rocksdb_block_cache_bytes_write``
-
-This variable shows the number of bytes written into cache.
-
-.. _rocksdb_block_cache_data_add:
-
-.. rubric:: ``rocksdb_block_cache_data_add``
-
-This variable shows the number of data blocks added to block cache.
-
-.. _rocksdb_block_cache_data_bytes_insert:
-
-.. rubric:: ``rocksdb_block_cache_data_bytes_insert``
-
-This variable shows the number of bytes of data blocks inserted into cache.
-
-.. _rocksdb_block_cache_data_hit:
-
-.. rubric:: ``rocksdb_block_cache_data_hit``
-
-This variable shows the number of cache hits when accessing the
-data block from the block cache.
-
-.. _rocksdb_block_cache_data_miss:
-
-.. rubric:: ``rocksdb_block_cache_data_miss``
-
-This variable shows the number of cache misses when accessing the
-data block from the block cache.
-
-.. _rocksdb_block_cache_filter_add:
-
-.. rubric:: ``rocksdb_block_cache_filter_add``
-
-This variable shows the number of filter blocks added to block cache.
-
-.. _rocksdb_block_cache_filter_bytes_evict:
-
-.. rubric:: ``rocksdb_block_cache_filter_bytes_evict``
-
-This variable shows the number of bytes of bloom filter blocks
-removed from cache.
-
-.. _rocksdb_block_cache_filter_bytes_insert:
-
-.. rubric:: ``rocksdb_block_cache_filter_bytes_insert``
-
-This variable shows the number of bytes of bloom filter blocks
-inserted into cache.
-
-.. _rocksdb_block_cache_filter_hit:
-
-.. rubric:: ``rocksdb_block_cache_filter_hit``
-
-This variable shows the number of times cache hit when accessing filter block
-from block cache.
-
-.. _rocksdb_block_cache_filter_miss:
-
-.. rubric:: ``rocksdb_block_cache_filter_miss``
-
-This variable shows the number of times cache miss when accessing filter
-block from block cache.
-
-.. _rocksdb_block_cache_hit:
-
-.. rubric:: ``rocksdb_block_cache_hit``
-
-This variable shows the total number of block cache hits.
-
-.. _rocksdb_block_cache_index_add:
-
-.. rubric:: ``rocksdb_block_cache_index_add``
-
-This variable shows the number of index blocks added to block cache.
-
-.. _rocksdb_block_cache_index_bytes_evict:
-
-.. rubric:: ``rocksdb_block_cache_index_bytes_evict``
-
-This variable shows the number of bytes of index block erased from cache.
-
-.. _rocksdb_block_cache_index_bytes_insert:
-
-.. rubric:: ``rocksdb_block_cache_index_bytes_insert``
-
-This variable shows the number of bytes of index blocks inserted into cache.
-
-.. _rocksdb_block_cache_index_hit:
-
-.. rubric:: ``rocksdb_block_cache_index_hit``
-
-This variable shows the total number of block cache index hits.
-
-.. _rocksdb_block_cache_index_miss:
-
-.. rubric:: ``rocksdb_block_cache_index_miss``
-
-This variable shows the number of times cache hit when accessing index
-block from block cache.
-
-.. _rocksdb_block_cache_miss:
-
-.. rubric:: ``rocksdb_block_cache_miss``
-
-This variable shows the total number of block cache misses.
-
-.. _rocksdb_block_cache_compressed_hit:
-
-.. rubric:: ``rocksdb_block_cache_compressed_hit``
-
-This variable shows the number of hits in the compressed block cache.
-
-.. _rocksdb_block_cache_compressed_miss:
-
-.. rubric:: ``rocksdb_block_cache_compressed_miss``
-
-This variable shows the number of misses in the compressed block cache.
-
-.. _rocksdb_bloom_filter_prefix_checked:
-
-.. rubric:: ``rocksdb_bloom_filter_prefix_checked``
-
-This variable shows the number of times bloom was checked before
-creating iterator on a file.
-
-.. _rocksdb_bloom_filter_prefix_useful:
-
-.. rubric:: ``rocksdb_bloom_filter_prefix_useful``
-
-This variable shows the number of times the check was useful in avoiding
-iterator creation (and thus likely IOPs).
-
-.. _rocksdb_bloom_filter_useful:
-
-.. rubric:: ``rocksdb_bloom_filter_useful``
-
-This variable shows the number of times bloom filter has avoided file reads.
-
-.. _rocksdb_bytes_read:
-
-.. rubric:: ``rocksdb_bytes_read``
-
-This variable shows the total number of uncompressed bytes read. It could be
-either from memtables, cache, or table files.
-
-.. _rocksdb_bytes_written:
-
-.. rubric:: ``rocksdb_bytes_written``
-
-This variable shows the total number of uncompressed bytes written.
-
-.. _rocksdb_compact_read_bytes:
-
-.. rubric:: ``rocksdb_compact_read_bytes``
-
-This variable shows the number of bytes read during compaction
-
-.. _rocksdb_compact_write_bytes:
-
-.. rubric:: ``rocksdb_compact_write_bytes``
-
-This variable shows the number of bytes written during compaction.
-
-.. _rocksdb_compaction_key_drop_new:
-
-.. rubric:: ``rocksdb_compaction_key_drop_new``
-
-This variable shows the number of key drops during compaction because
-it was overwritten with a newer value.
-
-.. _rocksdb_compaction_key_drop_obsolete:
-
-.. rubric:: ``rocksdb_compaction_key_drop_obsolete``
-
-This variable shows the number of key drops during compaction because
-it was obsolete.
-
-.. _rocksdb_compaction_key_drop_user:
-
-.. rubric:: ``rocksdb_compaction_key_drop_user``
-
-This variable shows the number of key drops during compaction because
-user compaction function has dropped the key.
-
-.. _rocksdb_flush_write_bytes:
-
-.. rubric:: ``rocksdb_flush_write_bytes``
-
-This variable shows the number of bytes written during flush.
-
-.. _rocksdb_get_hit_l0:
-
-.. rubric:: ``rocksdb_get_hit_l0``
-
-This variable shows the number of ``Get()`` queries served by L0.
-
-.. _rocksdb_get_hit_l1:
-
-.. rubric:: ``rocksdb_get_hit_l1``
-
-This variable shows the number of ``Get()`` queries served by L1.
-
-.. _rocksdb_get_hit_l2_and_up:
-
-.. rubric:: ``rocksdb_get_hit_l2_and_up``
-
-This variable shows the number of ``Get()`` queries served by L2 and up.
-
-.. _rocksdb_get_updates_since_calls:
-
-.. rubric:: ``rocksdb_get_updates_since_calls``
-
-This variable shows the number of calls to ``GetUpdatesSince`` function.
-Useful to keep track of transaction log iterator refreshes
-
-.. _rocksdb_iter_bytes_read:
-
-.. rubric:: ``rocksdb_iter_bytes_read``
-
-This variable shows the number of uncompressed bytes read from an iterator.
-It includes size of key and value.
-
-.. _rocksdb_memtable_hit:
-
-.. rubric:: ``rocksdb_memtable_hit``
-
-This variable shows the number of memtable hits.
-
-.. _rocksdb_memtable_miss:
-
-.. rubric:: ``rocksdb_memtable_miss``
-
-This variable shows the number of memtable misses.
-
-.. _rocksdb_no_file_closes:
-
-.. rubric:: ``rocksdb_no_file_closes``
-
-This variable shows the number of time file were closed.
-
-.. _rocksdb_no_file_errors:
-
-.. rubric:: ``rocksdb_no_file_errors``
-
-This variable shows number of errors trying to read in data from an sst file.
-
-.. _rocksdb_no_file_opens:
-
-.. rubric:: ``rocksdb_no_file_opens``
-
-This variable shows the number of time file were opened.
-
-.. _rocksdb_num_iterators:
-
-.. rubric:: ``rocksdb_num_iterators``
-
-This variable shows the number of currently open iterators.
-
-.. _rocksdb_number_block_not_compressed:
-
-.. rubric:: ``rocksdb_number_block_not_compressed``
-
-This variable shows the number of uncompressed blocks.
-
-.. _rocksdb_number_db_next:
-
-.. rubric:: ``rocksdb_number_db_next``
-
-This variable shows the number of calls to ``next``.
-
-.. _rocksdb_number_db_next_found:
-
-.. rubric:: ``rocksdb_number_db_next_found``
-
-This variable shows the number of calls to ``next`` that returned data.
-
-.. _rocksdb_number_db_prev:
-
-.. rubric:: ``rocksdb_number_db_prev``
-
-This variable shows the number of calls to ``prev``.
-
-.. _rocksdb_number_db_prev_found:
-
-.. rubric:: ``rocksdb_number_db_prev_found``
-
-This variable shows the number of calls to ``prev`` that returned data.
-
-.. _rocksdb_number_db_seek:
-
-.. rubric:: ``rocksdb_number_db_seek``
-
-This variable shows the number of calls to ``seek``.
-
-.. _rocksdb_number_db_seek_found:
-
-.. rubric:: ``rocksdb_number_db_seek_found``
-
-This variable shows the number of calls to ``seek`` that returned data.
-
-.. _rocksdb_number_deletes_filtered:
-
-.. rubric:: ``rocksdb_number_deletes_filtered``
-
-This variable shows the number of deleted records that were not required to be
-written to storage because key did not exist.
-
-.. _rocksdb_number_keys_read:
-
-.. rubric:: ``rocksdb_number_keys_read``
-
-This variable shows the number of keys read.
-
-.. _rocksdb_number_keys_updated:
-
-.. rubric:: ``rocksdb_number_keys_updated``
-
-This variable shows the number of keys updated, if inplace update is enabled.
-
-.. _rocksdb_number_keys_written:
-
-.. rubric:: ``rocksdb_number_keys_written``
-
-This variable shows the number of keys written to the database.
-
-.. _rocksdb_number_merge_failures:
-
-.. rubric:: ``rocksdb_number_merge_failures``
-
-This variable shows the number of failures performing merge operator actions
-in RocksDB.
-
-.. _rocksdb_number_multiget_bytes_read:
-
-.. rubric:: ``rocksdb_number_multiget_bytes_read``
-
-This variable shows the number of bytes read during RocksDB
-``MultiGet()`` calls.
-
-.. _rocksdb_number_multiget_get:
-
-.. rubric:: ``rocksdb_number_multiget_get``
-
-This variable shows the number ``MultiGet()`` requests to RocksDB.
-
-.. _rocksdb_number_multiget_keys_read:
-
-.. rubric:: ``rocksdb_number_multiget_keys_read``
-
-This variable shows the keys read via ``MultiGet()``.
-
-.. _rocksdb_number_reseeks_iteration:
-
-.. rubric:: ``rocksdb_number_reseeks_iteration``
-
-This variable shows the number of times reseek happened inside an iteration to
-skip over large number of keys with same userkey.
-
-.. _rocksdb_number_sst_entry_delete:
-
-.. rubric:: ``rocksdb_number_sst_entry_delete``
-
-This variable shows the total number of delete markers written by MyRocks.
-
-.. _rocksdb_number_sst_entry_merge:
-
-.. rubric:: ``rocksdb_number_sst_entry_merge``
-
-This variable shows the total number of merge keys written by MyRocks.
-
-.. _rocksdb_number_sst_entry_other:
-
-.. rubric:: ``rocksdb_number_sst_entry_other``
-
-This variable shows the total number of non-delete, non-merge, non-put keys
-written by MyRocks.
-
-.. _rocksdb_number_sst_entry_put:
-
-.. rubric:: ``rocksdb_number_sst_entry_put``
-
-This variable shows the total number of put keys written by MyRocks.
-
-.. _rocksdb_number_sst_entry_singledelete:
-
-.. rubric:: ``rocksdb_number_sst_entry_singledelete``
-
-This variable shows the total number of single delete keys written by MyRocks.
-
-.. _rocksdb_number_stat_computes:
-
-.. rubric:: ``rocksdb_number_stat_computes``
-
-This variable isn't used anymore and will be removed in future releases.
-
-.. _rocksdb_number_superversion_acquires:
-
-.. rubric:: ``rocksdb_number_superversion_acquires``
-
-This variable shows the number of times the superversion structure has been
-acquired in RocksDB, this is used for tracking all of the files for the
-database.
-
-.. _rocksdb_number_superversion_cleanups:
-
-.. rubric:: ``rocksdb_number_superversion_cleanups``
-
-.. _rocksdb_number_superversion_releases:
-
-.. rubric:: ``rocksdb_number_superversion_releases``
-
-.. _rocksdb_rate_limit_delay_millis:
-
-.. rubric:: ``rocksdb_rate_limit_delay_millis``
-
-This variable was removed in *Percona Server for MySQL* :ref:`5.7.23-23`.
-
-.. _rocksdb_row_lock_deadlocks:
-
-.. rubric:: ``rocksdb_row_lock_deadlocks``
-
-This variable shows the total number of deadlocks that have been detected since the instance was started.
-
-.. _rocksdb_row_lock_wait_timeouts:
-
-.. rubric:: ``rocksdb_row_lock_wait_timeouts``
-
-This variable shows the total number of row lock wait timeouts that have been detected since the instance was started.
-
-.. _rocksdb_snapshot_conflict_errors:
-
-.. rubric:: ``rocksdb_snapshot_conflict_errors``
-
-This variable shows the number of snapshot conflict errors occurring during
-write transactions that forces the transaction to rollback.
-
-.. _rocksdb_stall_l0_file_count_limit_slowdowns:
-
-.. rubric:: ``rocksdb_stall_l0_file_count_limit_slowdowns``
-
-This variable shows the slowdowns in write due to L0 being close to full.
-
-.. _rocksdb_stall_locked_l0_file_count_limit_slowdowns:
-
-.. rubric:: ``rocksdb_stall_locked_l0_file_count_limit_slowdowns``
-
-This variable shows the slowdowns in write due to L0 being close to full and
-compaction for L0 is already in progress.
-
-.. _rocksdb_stall_l0_file_count_limit_stops:
-
-.. rubric:: ``rocksdb_stall_l0_file_count_limit_stops``
-
-This variable shows the stalls in write due to L0 being full.
-
-.. _rocksdb_stall_locked_l0_file_count_limit_stops:
-
-.. rubric:: ``rocksdb_stall_locked_l0_file_count_limit_stops``
-
-This variable shows the stalls in write due to L0 being full and compaction
-for L0 is already in progress.
-
-.. _rocksdb_stall_pending_compaction_limit_stops:
-
-.. rubric:: ``rocksdb_stall_pending_compaction_limit_stops``
-
-This variable shows the stalls in write due to hitting limits set for max
-number of pending compaction bytes.
-
-.. _rocksdb_stall_pending_compaction_limit_slowdowns:
-
-.. rubric:: ``rocksdb_stall_pending_compaction_limit_slowdowns``
-
-This variable shows the slowdowns in write due to getting close to limits set
-for max number of pending compaction bytes.
-
-.. _rocksdb_stall_memtable_limit_stops:
-
-.. rubric:: ``rocksdb_stall_memtable_limit_stops``
-
-This variable shows the stalls in write due to hitting max number of
-``memTables`` allowed.
-
-.. _rocksdb_stall_memtable_limit_slowdowns:
-
-.. rubric:: ``rocksdb_stall_memtable_limit_slowdowns``
-
-This variable shows the slowdowns in writes due to getting close to
-max number of memtables allowed.
-
-.. _rocksdb_stall_total_stops:
-
-.. rubric:: ``rocksdb_stall_total_stops``
-
-This variable shows the total number of write stalls.
-
-.. _rocksdb_stall_total_slowdowns:
-
-.. rubric:: ``rocksdb_stall_total_slowdowns``
-
-This variable shows the total number of write slowdowns.
-
-.. _rocksdb_stall_micros:
-
-.. rubric:: ``rocksdb_stall_micros``
-
-This variable shows how long (in microseconds) the writer had to wait for
-compaction or flush to finish.
-
-.. _rocksdb_wal_bytes:
-
-.. rubric:: ``rocksdb_wal_bytes``
-
-This variables shows the number of bytes written to WAL.
-
-.. _rocksdb_wal_group_syncs:
-
-.. rubric:: ``rocksdb_wal_group_syncs``
-
-This variable shows the number of group commit WAL file syncs
-that have occurred.
-
-.. _rocksdb_wal_synced:
-
-.. rubric:: ``rocksdb_wal_synced``
-
-This variable shows the number of times WAL sync was done.
-
-.. _rocksdb_write_other:
-
-.. rubric:: ``rocksdb_write_other``
-
-This variable shows the number of writes processed by another thread.
-
-.. _rocksdb_write_self:
-
-.. rubric:: ``rocksdb_write_self``
-
-This variable shows the number of writes that were processed
-by a requesting thread.
-
-.. _rocksdb_write_timedout:
-
-.. rubric:: ``rocksdb_write_timedout``
-
-This variable shows the number of writes ending up with timed-out.
-
-.. _rocksdb_write_wal:
-
-.. rubric:: ``rocksdb_write_wal``
-
-This variable shows the number of Write calls that request WAL.
diff --git a/doc/source/myrocks/variables.rst b/doc/source/myrocks/variables.rst
deleted file mode 100644
index 2d8b3a8b8188..000000000000
--- a/doc/source/myrocks/variables.rst
+++ /dev/null
@@ -1,4894 +0,0 @@
-.. _myrocks_server_variables:
-
-================================================================================
-MyRocks Server Variables
-================================================================================
-
-The MyRocks server variables expose configuration of the underlying RocksDB
-engine.  There several ways to set these variables:
-
-* For production deployments,
-  you should have all variables defined in the configuration file.
-
-* *Dynamic* variables can be changed at runtime using the ``SET`` statement.
-
-* If you want to test things out, you can set some of the variables
-  when starting ``mysqld`` using corresponding command-line options.
-
-If a variable was not set in either the configuration file
-or as a command-line option,
-the default value is used.
-
-Also, all variables can exist in one or both of the following scopes:
-
-* *Global* scope defines how the variable affects overall server operation.
-
-* *Session* scope defines how the variable affects operation
-  for individual client connections.
-
-.. tabularcolumns:: |p{10cm}|p{2cm}|p{2cm}|p{2cm}|
-
-.. list-table::
-   :header-rows: 1
-
-   * - Name
-     - Command Line
-     - Dynamic
-     - Scope
-   * - :ref:`rocksdb_access_hint_on_compaction_start`
-     - Yes
-     - No
-     - Global
-   * - :ref:`rocksdb_advise_random_on_open`
-     - Yes
-     - No
-     - Global
-   * - :ref:`rocksdb_allow_concurrent_memtable_write`
-     - Yes
-     - No
-     - Global
-   * - :ref:`rocksdb_allow_to_start_after_corruption`
-     - Yes
-     - No
-     - Global
-   * - :ref:`rocksdb_allow_mmap_reads`
-     - Yes
-     - No
-     - Global
-   * - :ref:`rocksdb_allow_mmap_writes`
-     - Yes
-     - No
-     - Global
-   * - :ref:`rocksdb_allow_unsafe_alter`
-     - Yes
-     - No
-     - Global
-   * - :ref:`rocksdb_alter_column_default_inplace`
-     - Yes
-     - Yes
-     - Global
-   * - :ref:`rocksdb_base_background_compactions`
-     - Yes
-     - No
-     - Global
-   * - :ref:`rocksdb_blind_delete_primary_key`
-     - Yes
-     - Yes
-     - Global, Session
-   * - :ref:`rocksdb_block_cache_size`
-     - Yes
-     - Yes
-     - Global
-   * - :ref:`rocksdb_bulk_load_partial_index`
-     - Yes
-     - Yes
-     - Local
-   * - :ref:`rocksdb_block_restart_interval`
-     - Yes
-     - No
-     - Global
-   * - :ref:`rocksdb_block_size`
-     - Yes
-     - No
-     - Global
-   * - :ref:`rocksdb_block_size_deviation`
-     - Yes
-     - No
-     - Global
-   * - :ref:`rocksdb_bulk_load`
-     - Yes
-     - Yes
-     - Global, Session
-   * - :ref:`rocksdb_bulk_load_allow_sk`
-     - Yes
-     - Yes
-     - Global, Session
-   * - :ref:`rocksdb_bulk_load_allow_unsorted`
-     - Yes
-     - Yes
-     - Global, Session
-   * - :ref:`rocksdb_bulk_load_size`
-     - Yes
-     - Yes
-     - Global
-   * - :ref:`rocksdb_bytes_per_sync`
-     - Yes
-     - Yes
-     - Global
-   * - :ref:`rocksdb_cache_dump`
-     - Yes
-     - No
-     - Global
-   * - :ref:`rocksdb_cache_index_and_filter_blocks`
-     - Yes
-     - No
-     - Global
-   * - :ref:`rocksdb_cancel_manual_compactions`
-     - Yes
-     - Yes
-     - Global
-   * - :ref:`rocksdb_checksums_pct`
-     - Yes
-     - Yes
-     - Global, Session
-   * - :ref:`rocksdb_collect_sst_properties`
-     - Yes
-     - No
-     - Global
-   * - :ref:`rocksdb_commit_in_the_middle`
-     - Yes
-     - Yes
-     - Global
-   * - :ref:`rocksdb_commit_time_batch_for_recovery`
-     - Yes
-     - Yes
-     - Global, Session
-   * - :ref:`rocksdb_compact_cf`
-     - Yes
-     - Yes
-     - Global
-   * - :ref:`rocksdb_compaction_readahead_size`
-     - Yes
-     - Yes
-     - Global
-   * - :ref:`rocksdb_compaction_sequential_deletes`
-     - Yes
-     - Yes
-     - Global
-   * - :ref:`rocksdb_compaction_sequential_deletes_count_sd`
-     - Yes
-     - Yes
-     - Global
-   * - :ref:`rocksdb_compaction_sequential_deletes_file_size`
-     - Yes
-     - Yes
-     - Global
-   * - :ref:`rocksdb_compaction_sequential_deletes_window`
-     - Yes
-     - Yes
-     - Global
-   * - :ref:`rocksdb_concurrent_prepare`
-     - Yes
-     - No
-     - Global
-   * - :ref:`rocksdb_create_checkpoint`
-     - Yes
-     - Yes
-     - Global
-   * - :ref:`rocksdb_create_if_missing`
-     - Yes
-     - No
-     - Global
-   * - :ref:`rocksdb_create_missing_column_families`
-     - Yes
-     - No
-     - Global
-   * - :ref:`rocksdb_create_temporary_checkpoint`
-     - Yes
-     - Yes
-     - Session
-   * - :ref:`rocksdb_datadir`
-     - Yes
-     - No
-     - Global
-   * - :ref:`rocksdb_db_write_buffer_size`
-     - Yes
-     - No
-     - Global
-   * - :ref:`rocksdb_deadlock_detect`
-     - Yes
-     - Yes
-     - Global, Session
-   * - :ref:`rocksdb_deadlock_detect_depth`
-     - Yes
-     - Yes
-     - Global, Session
-   * - :ref:`rocksdb_debug_optimizer_no_zero_cardinality`
-     - Yes
-     - Yes
-     - Global, Session
-   * - :ref:`rocksdb_debug_ttl_ignore_pk`
-     - Yes
-     - Yes
-     - Global
-   * - :ref:`rocksdb_debug_ttl_read_filter_ts`
-     - Yes
-     - Yes
-     - Global
-   * - :ref:`rocksdb_debug_ttl_rec_ts`
-     - Yes
-     - Yes
-     - Global
-   * - :ref:`rocksdb_debug_ttl_snapshot_ts`
-     - Yes
-     - Yes
-     - Global
-   * - :ref:`rocksdb_default_cf_options`
-     - Yes
-     - No
-     - Global
-   * - :ref:`rocksdb_delayed_write_rate`
-     - Yes
-     - Yes
-     - Global
-   * - :ref:`rocksdb_delete_cf`
-     - Yes
-     - Yes
-     - Global
-   * - :ref:`rocksdb_delete_obsolete_files_period_micros`
-     - Yes
-     - No
-     - Global
-   * - :ref:`rocksdb_disable_file_deletions`
-     - Yes
-     - Yes
-     - Session
-   * - :ref:`rocksdb_enable_bulk_load_api`
-     - Yes
-     - No
-     - Global
-   * - :ref:`rocksdb_enable_insert_with_update_caching`
-     - Yes
-     - Yes
-     - Global
-   * - :ref:`rocksdb_enable_iterate_bounds`
-     - Yes
-     - Yes
-     - Global, Local
-   * - :ref:`rocksdb_enable_pipelined_write`
-     - Yes
-     - No
-     - Global
-   * - :ref:`rocksdb_enable_remove_orphaned_dropped_cfs`
-     - Yes
-     - Yes
-     - Global
-   * - :ref:`rocksdb_enable_ttl`
-     - Yes
-     - No
-     - Global
-   * - :ref:`rocksdb_enable_ttl_read_filtering`
-     - Yes
-     - Yes
-     - Global
-   * - :ref:`rocksdb_enable_thread_tracking`
-     - Yes
-     - No
-     - Global
-   * - :ref: `rocksdb_enable_tmp_table`
-     - Yes
-     - No
-     - Global
-   * - :ref:`rocksdb_enable_write_thread_adaptive_yield`
-     - Yes
-     - No
-     - Global
-   * - :ref:`rocksdb_error_if_exists`
-     - Yes
-     - No
-     - Global
-   * - :ref:`rocksdb_error_on_suboptimal_collation`
-     - Yes
-     - No
-     - Global
-   * - :ref:`rocksdb_flush_log_at_trx_commit`
-     - Yes
-     - Yes
-     - Global, Session
-   * - :ref:`rocksdb_flush_memtable_on_analyze`
-     - Yes
-     - Yes
-     - Global, Session
-   * - :ref:`rocksdb_force_compute_memtable_stats`
-     - Yes
-     - Yes
-     - Global
-   * - :ref:`rocksdb_force_compute_memtable_stats_cachetime`
-     - Yes
-     - Yes
-     - Global
-   * - :ref:`rocksdb_force_flush_memtable_and_lzero_now`
-     - Yes
-     - Yes
-     - Global
-   * - :ref:`rocksdb_force_flush_memtable_now`
-     - Yes
-     - Yes
-     - Global
-   * - :ref:`rocksdb_force_index_records_in_range`
-     - Yes
-     - Yes
-     - Global, Session
-   * - :ref:`rocksdb_hash_index_allow_collision`
-     - Yes
-     - No
-     - Global
-   * - :ref:`rocksdb_ignore_unknown_options`
-     - Yes
-     - No
-     - Global
-   * - :ref:`rocksdb_index_type`
-     - Yes
-     - No
-     - Global
-   * - :ref:`rocksdb_info_log_level`
-     - Yes
-     - Yes
-     - Global
-   * - :ref: `rocksdb_instant_ddl`
-     - Yes
-     - Yes
-     - Global
-   * - :ref:`rocksdb_is_fd_close_on_exec`
-     - Yes
-     - No
-     - Global
-   * - :ref:`rocksdb_keep_log_file_num`
-     - Yes
-     - No
-     - Global
-   * - :ref:`rocksdb_large_prefix`
-     - Yes
-     - Yes
-     - Global
-   * - :ref:`rocksdb_lock_scanned_rows`
-     - Yes
-     - Yes
-     - Global, Session
-   * - :ref:`rocksdb_lock_wait_timeout`
-     - Yes
-     - Yes
-     - Global, Session
-   * - :ref:`rocksdb_log_file_time_to_roll`
-     - Yes
-     - No
-     - Global
-   * - :ref:`rocksdb_manifest_preallocation_size`
-     - Yes
-     - No
-     - Global
-   * - :ref:`rocksdb_manual_compaction_bottommost_level`
-     - Yes
-     - Yes
-     - Local
-   * - :ref:`rocksdb_manual_wal_flush`
-     - Yes
-     - No
-     - Global
-   * - :ref:`rocksdb_master_skip_tx_api`
-     - Yes
-     - Yes
-     - Global, Session
-   * - :ref:`rocksdb_max_background_compactions`
-     - Yes
-     - Yes
-     - Global
-   * - :ref:`rocksdb_max_background_flushes`
-     - Yes
-     - No
-     - Global
-   * - :ref:`rocksdb_max_background_jobs`
-     - Yes
-     - Yes
-     - Global
-   * - :ref:`rocksdb_max_bottom_pri_background_compactions`
-     - Yes
-     - No
-     - Global
-   * - :ref:`rocksdb_max_compaction_history`
-     - Yes
-     - Yes
-     - Global
-   * - :ref:`rocksdb_max_latest_deadlocks`
-     - Yes
-     - Yes
-     - Global
-   * - :ref:`rocksdb_max_log_file_size`
-     - Yes
-     - No
-     - Global
-   * - :ref:`rocksdb_max_manifest_file_size`
-     - Yes
-     - No
-     - Global
-   * - :ref:`rocksdb_max_open_files`
-     - Yes
-     - No
-     - Global
-   * - :ref:`rocksdb_max_row_locks`
-     - Yes
-     - Yes
-     - Global
-   * - :ref:`rocksdb_max_subcompactions`
-     - Yes
-     - No
-     - Global
-   * - :ref:`rocksdb_max_total_wal_size`
-     - Yes
-     - No
-     - Global
-   * - :ref:`rocksdb_merge_buf_size`
-     - Yes
-     - Yes
-     - Global, Session
-   * - :ref:`rocksdb_merge_combine_read_size`
-     - Yes
-     - Yes
-     - Global, Session
-   * - :ref:`rocksdb_merge_tmp_file_removal_delay_ms`
-     - Yes
-     - Yes
-     - Global, Session
-   * - :ref:`rocksdb_new_table_reader_for_compaction_inputs`
-     - Yes
-     - No
-     - Global
-   * - :ref:`rocksdb_no_block_cache`
-     - Yes
-     - No
-     - Global
-   * - :ref:`rocksdb_no_create_column_family`
-     - Yes
-     - No
-     - Global
-   * - :ref:`rocksdb_override_cf_options`
-     - Yes
-     - No
-     - Global
-   * - :ref:`rocksdb_paranoid_checks`
-     - Yes
-     - No
-     - Global
-   * - :ref:`rocksdb_partial_index_sort_max_mem`
-     - Yes
-     - Yes
-     - Local
-   * - :ref:`rocksdb_pause_background_work`
-     - Yes
-     - Yes
-     - Global
-   * - :ref:`rocksdb_perf_context_level`
-     - Yes
-     - Yes
-     - Global, Session
-   * - :ref:`rocksdb_persistent_cache_path`
-     - Yes
-     - No
-     - Global
-   * - :ref:`rocksdb_persistent_cache_size_mb`
-     - Yes
-     - No
-     - Global, Session
-   * - :ref:`rocksdb_pin_l0_filter_and_index_blocks_in_cache`
-     - Yes
-     - No
-     - Global
-   * - :ref:`rocksdb_print_snapshot_conflict_queries`
-     - Yes
-     - Yes
-     - Global
-   * - :ref:`rocksdb_rate_limiter_bytes_per_sec`
-     - Yes
-     - Yes
-     - Global
-   * - :ref:`rocksdb_read_free_rpl`
-     - Yes
-     - Yes
-     - Global
-   * - :ref:`rocksdb_read_free_rpl_tables`
-     - Yes
-     - Yes
-     - Global, Session
-   * - :ref:`rocksdb_records_in_range`
-     - Yes
-     - Yes
-     - Global, Session
-   * - :ref:`rocksdb_reset_stats`
-     - Yes
-     - Yes
-     - Global
-   * - :ref:`rocksdb_rollback_on_timeout`
-     - Yes
-     - Yes
-     - Global
-   * - :ref:`rocksdb_rpl_skip_tx_api`
-     - Yes
-     - Yes
-     - Global
-   * - :ref:`rocksdb_seconds_between_stat_computes`
-     - Yes
-     - Yes
-     - Global
-   * - :ref:`rocksdb_signal_drop_index_thread`
-     - Yes
-     - Yes
-     - Global
-   * - :ref:`rocksdb_sim_cache_size`
-     - Yes
-     - Yes
-     - Global
-   * - :ref:`rocksdb_skip_bloom_filter_on_read`
-     - Yes
-     - Yes
-     - Global, Session
-   * - :ref:`rocksdb_skip_fill_cache`
-     - Yes
-     - Yes
-     - Global, Session
-   * - :ref:`rocksdb_skip_locks_if_skip_unique_check`
-     - Yes
-     - Yes
-     - Global
-   * - :ref:`rocksdb_sst_mgr_rate_bytes_per_sec`
-     - Yes
-     - No
-     - Global
-   * - :ref:`rocksdb_stats_dump_period_sec`
-     - Yes
-     - No
-     - Global
-   * - :ref:`rocksdb_stats_level`
-     - Yes
-     - Yes
-     - Global
-   * - :ref:`rocksdb_stats_recalc_rate`
-     - Yes
-     - Yes
-     - Global, Session
-   * - :ref:`rocksdb_store_row_debug_checksums`
-     - Yes
-     - Yes
-     - Global, Session
-   * - :ref:`rocksdb_strict_collation_check`
-     - Yes
-     - Yes
-     - Global
-   * - :ref:`rocksdb_strict_collation_exceptions`
-     - Yes
-     - Yes
-     - Global
-   * - :ref:`rocksdb_table_cache_numshardbits`
-     - Yes
-     - No
-     - Global
-   * - :ref:`rocksdb_table_stats_background_thread_nice_value`
-     - Yes
-     - Yes
-     - Global
-   * - :ref:`rocksdb_table_stats_max_num_rows_scanned`
-     - Yes
-     - Yes
-     - Global
-   * - :ref:`rocksdb_table_stats_recalc_threshold_count`
-     - Yes
-     - Yes
-     - Global
-   * - :ref:`rocksdb_table_stats_recalc_threshold_pct`
-     - Yes
-     - Yes
-     - Global
-   * - :ref:`rocksdb_table_stats_sampling_pct`
-     - Yes
-     - Yes
-     - Global
-   * - :ref:`rocksdb_table_stats_use_table_scan`
-     - Yes
-     - Yes
-     - Global
-   * - :ref:`rocksdb_tmpdir`
-     - Yes
-     - Yes
-     - Global, Session
-   * - :ref:`rocksdb_two_write_queues`
-     - Yes
-     - No
-     - Global
-   * - :ref:`rocksdb_trace_block_cache_access`
-     - Yes
-     - Yes
-     - Global
-   * - :ref:`rocksdb_trace_queries`
-     - Yes
-     - Yes
-     - Global
-   * - :ref:`rocksdb_trace_sst_api`
-     - Yes
-     - Yes
-     - Global, Session
-   * - :ref:`rocksdb_track_and_verify_wals_in_manifest`
-     - No
-     - No
-     - Global
-   * - :ref:`rocksdb_unsafe_for_binlog`
-     - Yes
-     - Yes
-     - Global, Session
-   * - :ref:`rocksdb_update_cf_options`
-     - Yes
-     - Yes
-     - Global
-   * - :ref:`rocksdb_use_adaptive_mutex`
-     - Yes
-     - No
-     - Global
-   * - :ref:`rocksdb_use_default_sk_cf`
-     - Yes
-     - No
-     - Global
-   * - :ref:`rocksdb_use_direct_io_for_flush_and_compaction`
-     - Yes
-     - No
-     - Global
-   * - :ref:`rocksdb_use_direct_reads`
-     - Yes
-     - No
-     - Global
-   * - :ref:`rocksdb_use_fsync`
-     - Yes
-     - No
-     - Global
-   * - :ref:`rocksdb_validate_tables`
-     - Yes
-     - No
-     - Global
-   * - :ref:`rocksdb_verify_row_debug_checksums`
-     - Yes
-     - Yes
-     - Global, Session
-   * - :ref:`rocksdb_wal_bytes_per_sync`
-     - Yes
-     - Yes
-     - Global
-   * - :ref:`rocksdb_wal_dir`
-     - Yes
-     - No
-     - Global
-   * - :ref:`rocksdb_wal_recovery_mode`
-     - Yes
-     - Yes
-     - Global
-   * - :ref:`rocksdb_wal_size_limit_mb`
-     - Yes
-     - No
-     - Global
-   * - :ref:`rocksdb_wal_ttl_seconds`
-     - Yes
-     - No
-     - Global
-   * - :ref:`rocksdb_whole_key_filtering`
-     - Yes
-     - No
-     - Global
-   * - :ref:`rocksdb_write_batch_flush_threshold`
-     - Yes
-     - Yes
-     - Local
-   * - :ref:`rocksdb_write_batch_max_bytes`
-     - Yes
-     - Yes
-     - Global, Session
-   * - :ref:`rocksdb_write_disable_wal`
-     - Yes
-     - Yes
-     - Global, Session
-   * - :ref:`rocksdb_write_ignore_missing_column_families`
-     - Yes
-     - Yes
-     - Global, Session
-   * - :ref:`rocksdb_write_policy`
-     - Yes
-     - No
-     - Global
-
-.. _rocksdb_access_hint_on_compaction_start:
-
-.. rubric:: ``rocksdb_access_hint_on_compaction_start``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--rocksdb-access-hint-on-compaction-start``
-   * - Dynamic
-     - No
-   * - Scope
-     - Global
-   * - Data type
-     - String or numeric
-   * - Default
-     - ``NORMAL`` or ``1``
-
-Specifies the file access pattern once a compaction is started,
-applied to all input files of a compaction.
-Possible values are:
-
-* ``0`` = ``NONE``
-* ``1`` = ``NORMAL`` (default)
-* ``2`` = ``SEQUENTIAL``
-* ``3`` = ``WILLNEED``
-
-.. _rocksdb_advise_random_on_open:
-
-.. rubric:: ``rocksdb_advise_random_on_open``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--rocksdb-advise-random-on-open``
-   * - Dynamic
-     - No
-   * - Scope
-     - Global
-   * - Data type
-     - Boolean
-   * - Default
-     - ``ON``
-
-Specifies whether to hint the underlying file system
-that the file access pattern is random,
-when a data file is opened.
-Enabled by default.
-
-.. _rocksdb_allow_concurrent_memtable_write:
-
-.. rubric:: ``rocksdb_allow_concurrent_memtable_write``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--rocksdb-allow-concurrent-memtable-write``
-   * - Dynamic
-     - No
-   * - Scope
-     - Global
-   * - Data type
-     - Boolean
-   * - Default
-     - ``OFF``
-
-Specifies whether to allow multiple writers to update memtables in parallel.
-Disabled by default.
-
-.. _rocksdb_allow_to_start_after_corruption:
-
-.. rubric:: ``rocksdb_allow_to_start_after_corruption``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--rocksdb_allow_to_start_after_corruption``
-   * - Dynamic
-     - No
-   * - Scope
-     - Global
-   * - Data type
-     - Boolean
-   * - Default
-     - ``OFF``
-
-Specifies whether to allow server to restart once MyRocks reported data
-corruption. Disabled by default.
-
-Once corruption is detected server writes marker file (named
-ROCKSDB_CORRUPTED) in the data directory and aborts. If marker file exists,
-then mysqld exits on startup with an error message. The restart failure will
-continue until the problem is solved or until mysqld is started with this
-variable turned on in the command line.
-
-.. note:: Not all memtables support concurrent writes.
-
-.. _rocksdb_allow_mmap_reads:
-
-.. rubric:: ``rocksdb_allow_mmap_reads``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--rocksdb-allow-mmap-reads``
-   * - Dynamic
-     - No
-   * - Scope
-     - Global
-   * - Data type
-     - Boolean
-   * - Default
-     - ``OFF``
-
-Specifies whether to allow the OS to map a data file into memory for reads.
-Disabled by default.
-If you enable this, make sure that :ref:`rocksdb_use_direct_reads` is disabled.
-
-.. _rocksdb_allow_mmap_writes:
-
-.. rubric:: ``rocksdb_allow_mmap_writes``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--rocksdb-allow-mmap-writes``
-   * - Dynamic
-     - No
-   * - Scope
-     - Global
-   * - Data type
-     - Boolean
-   * - Default
-     - ``OFF``
-
-Specifies whether to allow the OS to map a data file into memory for writes.
-Disabled by default.
-
-.. _rocksdb_allow_unsafe_alter:
-
-.. rubric:: ``rocksdb_allow_unsafe_alter``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--rocksdb-allow-unsafe-alter``
-   * - Dynamic
-     - No
-   * - Scope
-     - Global
-   * - Data type
-     - Boolean
-   * - Default
-     - ``OFF``
-
-Enable crash unsafe INPLACE ADD|DROP partition.
-
-.. _rocksdb_alter_column_default_inplace:
-
-.. rubric:: ``rocksdb_alter_column_default_inplace``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--rocksdb-alter-column-default-inplace``
-   * - Dynamic
-     - Yes
-   * - Scope
-     - Global
-   * - Data type
-     - Boolean
-   * - Default
-     - ON
-
-Allows an inplace alter for the ``ALTER COLUMN`` default operation.
-
-.. _rocksdb_base_background_compactions:
-
-.. rubric:: ``rocksdb_base_background_compactions``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--rocksdb-base-background-compactions``
-   * - Dynamic
-     - No
-   * - Scope
-     - Global
-   * - Data type
-     - Numeric
-   * - Default
-     - ``1``
-
-Specifies the suggested number of concurrent background compaction jobs,
-submitted to the default LOW priority thread pool in RocksDB. Default is ``1``.
-Allowed range of values is from ``-1`` to ``64``.  Maximum depends on the
-:ref:`rocksdb_max_background_compactions` variable. This variable was
-replaced with :ref:`rocksdb_max_background_jobs`, which automatically
-decides how many threads to allocate towards flush/compaction.
-
-.. _rocksdb_blind_delete_primary_key:
-
-.. rubric:: ``rocksdb_blind_delete_primary_key``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--rocksdb-blind-delete-primary-key``
-   * - Dynamic
-     - Yes
-   * - Scope
-     - Global, Session
-   * - Data type
-     - Boolean
-   * - Default
-     - ``OFF``
-  
-The variable was implemented in :ref:`8.0.20-11`. Skips verifying if rows exists before executing deletes. The following conditions must be met:
-
-* The variable is enabled
-* Only a single table listed in the ``DELETE`` statement
-* The table has only a primary key with no secondary keys
-
-.. _rocksdb_block_cache_size:
-
-.. rubric:: ``rocksdb_block_cache_size``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--rocksdb-block-cache-size``
-   * - Dynamic
-     - No
-   * - Scope
-     - Global
-   * - Data type
-     - Numeric
-   * - Default
-     - ``536870912``
-
-Specifies the size of the LRU block cache for RocksDB.
-This memory is reserved for the block cache,
-which is in addition to any filesystem caching that may occur.
-
-Minimum value is ``1024``,
-because that's the size of one block.
-
-Default value is ``536870912``.
-
-Maximum value is ``9223372036854775807``.
-
-.. _rocksdb_block_restart_interval:
-
-.. rubric:: ``rocksdb_block_restart_interval``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--rocksdb-block-restart-interval``
-   * - Dynamic
-     - No
-   * - Scope
-     - Global
-   * - Data type
-     - Numeric
-   * - Default
-     - ``16``
-
-Specifies the number of keys for each set of delta encoded data.
-Default value is ``16``.
-Allowed range is from ``1`` to ``2147483647``.
-
-.. _rocksdb_block_size:
-
-.. rubric:: ``rocksdb_block_size``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--rocksdb-block-size``
-   * - Dynamic
-     - No
-   * - Scope
-     - Global
-   * - Data type
-     - Numeric
-   * - Default
-     - ``16 KB``
-
-Specifies the size of the data block for reading RocksDB data files.
-The default value is ``16 KB``.
-The allowed range is from ``1024`` to ``18446744073709551615`` bytes.
-
-.. _rocksdb_block_size_deviation:
-
-.. rubric:: ``rocksdb_block_size_deviation``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--rocksdb-block-size-deviation``
-   * - Dynamic
-     - No
-   * - Scope
-     - Global
-   * - Data type
-     - Numeric
-   * - Default
-     - ``10``
-
-Specifies the threshold for free space allowed in a data block
-(see :ref:`rocksdb_block_size`).
-If there is less space remaining,
-close the block (and write to new block).
-Default value is ``10``, meaning that the block is not closed
-until there is less than 10 bits of free space remaining.
-
-Allowed range is from ``1`` to ``2147483647``.
-
-.. _rocksdb_bulk_load_allow_sk:
-
-.. rubric:: ``rocksdb_bulk_load_allow_sk``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--rocksdb-bulk-load-allow-sk``
-   * - Dynamic
-     - Yes
-   * - Scope
-     - Global, Session
-   * - Data type
-     - Boolean
-   * - Default
-     - ``OFF``
-
-Enabling this variable allows secondary keys to be added using the bulk loading
-feature. This variable can be enabled or disabled only when the :ref:`rocksdb_bulk_load` is ``OFF``.
-
-.. _rocksdb_bulk_load_allow_unsorted:
-
-.. rubric:: ``rocksdb_bulk_load_allow_unsorted``
- 
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--rocksdb-bulk-load-allow-unsorted``
-   * - Dynamic
-     - Yes
-   * - Scope
-     - Global, Session
-   * - Data type
-     - Boolean
-   * - Default
-     - ``OFF``
-
-By default, the bulk loader requires its input to be sorted in the primary
-key order. If enabled, unsorted inputs are allowed too, which are then
-sorted by the bulkloader itself, at a performance penalty.
-
-.. _rocksdb_bulk_load:
-
-.. rubric:: ``rocksdb_bulk_load``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--rocksdb-bulk-load``
-   * - Dynamic
-     - Yes
-   * - Scope
-     - Global, Session
-   * - Data type
-     - Boolean
-   * - Default
-     - ``OFF``
-
-Specifies whether to use bulk load:
-MyRocks will ignore checking keys for uniqueness
-or acquiring locks during transactions.
-Disabled by default.
-Enable this only if you are certain that there are no row conflicts,
-for example, when setting up a new MyRocks instance from a MySQL dump.
-
-When the `rocksdb_bulk_load` variable is enabled, it behaves as if the variable `rocksdb_commit_in_the_middle` is enabled, even if the variable `rocksdb_commit_in_the_middle` is disabled.
-
-.. _rocksdb_bulk_load_partial_index:
-
-.. rubric:: ``rocksdb_bulk_load_partial_index``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--rocksdb-bulk-load-partial-index``
-   * - Dynamic
-     - Yes
-   * - Scope
-     - Local
-   * - Data type
-     - Boolean
-   * - Default
-     - ``ON``
-
-The variable was implemented in :ref:`8.0.27-18`. Materializes partial index during bulk load instead of leaving the index empty.
-
-.. _rocksdb_bulk_load_size:
-
-.. rubric:: ``rocksdb_bulk_load_size``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--rocksdb-bulk-load-size``
-   * - Dynamic
-     - Yes
-   * - Scope
-     - Global, Session
-   * - Data type
-     - Numeric
-   * - Default
-     - ``1000``
-
-Specifies the number of keys to accumulate
-before committing them to the storage engine when bulk load is enabled
-(see :ref:`rocksdb_bulk_load`).
-Default value is ``1000``,
-which means that a batch can contain up to 1000 records
-before they are implicitly committed.
-Allowed range is from ``1`` to ``1073741824``.
-
-.. _rocksdb_bytes_per_sync:
-
-.. rubric:: ``rocksdb_bytes_per_sync``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--rocksdb-bytes-per-sync``
-   * - Dynamic
-     - Yes
-   * - Scope
-     - Global
-   * - Data type
-     - Numeric
-   * - Default
-     - ``0``
-
-Specifies how often should the OS sync files to disk
-as they are being written, asynchronously, in the background.
-This operation can be used to smooth out write I/O over time.
-Default value is ``0`` meaning that files are never synced.
-Allowed range is up to ``18446744073709551615``.
-
-.. _rocksdb_cache_dump:
-
-.. rubric:: ``rocksdb_cache_dump``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--rocksdb-cache-dump``
-   * - Dynamic
-     - No
-   * - Scope
-     - Global
-   * - Data type
-     - Boolean
-   * - Default
-     - ``ON``
-
-The variable was implemented in :ref:`8.0.20-11`. Includes RocksDB block cache content in core dump. This variable is
-enabled by default.
-
-.. _rocksdb_cache_index_and_filter_blocks:
-
-.. rubric:: ``rocksdb_cache_index_and_filter_blocks``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--rocksdb-cache-index-and-filter-blocks``
-   * - Dynamic
-     - No
-   * - Scope
-     - Global
-   * - Data type
-     - Boolean
-   * - Default
-     - ``ON``
-
-Specifies whether RocksDB should use the block cache for caching the index
-and bloomfilter data blocks from each data file.
-Enabled by default.
-If you disable this feature,
-RocksDB will allocate additional memory to maintain these data blocks.
-
-.. _rocksdb_cancel_manual_compactions:
-
-.. rubric:: ``rocksdb_cancel_manual_compactions``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--rocksdb-cancel-manual-compactions``
-   * - Dynamic
-     - Yes
-   * - Scope
-     - Global
-   * - Data type
-     - Boolean
-   * - Default
-     - ``OFF``
-  
-The variable was implemented in :ref:`8.0.27-18`. Cancels all ongoing manual compactions.
-
-.. _rocksdb_checksums_pct:
-
-.. rubric:: ``rocksdb_checksums_pct``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--rocksdb-checksums-pct``
-   * - Dynamic
-     - Yes
-   * - Scope
-     - Global, Session
-   * - Data type
-     - Numeric
-   * - Default
-     - ``100``
-
-Specifies the percentage of rows to be checksummed.
-Default value is ``100`` (checksum all rows).
-Allowed range is from ``0`` to ``100``.
-
-.. _rocksdb_collect_sst_properties:
-
-.. rubric:: ``rocksdb_collect_sst_properties``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--rocksdb-collect-sst-properties``
-   * - Dynamic
-     - No
-   * - Scope
-     - Global
-   * - Data type
-     - Boolean
-   * - Default
-     - ``ON``
-
-Specifies whether to collect statistics on each data file
-to improve optimizer behavior.
-Enabled by default.
-
-.. _rocksdb_commit_in_the_middle:
-
-.. rubric:: ``rocksdb_commit_in_the_middle``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--rocksdb-commit-in-the-middle``
-   * - Dynamic
-     - Yes
-   * - Scope
-     - Global
-   * - Data type
-     - Boolean
-   * - Default
-     - ``OFF``
-
-Specifies whether to commit rows implicitly
-when a batch contains more than the value of
-:ref:`rocksdb_bulk_load_size`.
-
-This variable is disabled by default. 
-When the `rocksdb_bulk_load` variable is enabled, it behaves as if the variable `rocksdb_commit_in_the_middle` is enabled, even if the variable `rocksdb_commit_in_the_middle` is disabled.
-
-.. _rocksdb_commit_time_batch_for_recovery:
-
-.. rubric:: ``rocksdb_commit_time_batch_for_recovery``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--rocksdb-commit-time-batch-for-recovery``
-   * - Dynamic
-     - Yes
-   * - Scope
-     - Global, Session
-   * - Data type
-     - Boolean
-   * - Default
-     - ``OFF``
-
-Specifies whether to write the commit time write batch into the database or
-not.
-
-.. note:: If the commit time write batch is only useful for recovery, then
-          writing to WAL is enough.
-
-.. _rocksdb_compact_cf:
-
-.. rubric:: ``rocksdb_compact_cf``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--rocksdb-compact-cf``
-   * - Dynamic
-     - Yes
-   * - Scope
-     - Global
-   * - Data type
-     - String
-   * - Default
-     - 
-
-Specifies the name of the column family to compact.
-
-.. _rocksdb_compaction_readahead_size:
-
-.. rubric:: ``rocksdb_compaction_readahead_size``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--rocksdb-compaction-readahead-size``
-   * - Dynamic
-     - Yes
-   * - Scope
-     - Global
-   * - Data type
-     - Numeric
-   * - Default
-     - ``0``
-
-Specifies the size of reads to perform ahead of compaction.
-Default value is ``0``.
-Set this to at least 2 megabytes (``16777216``)
-when using MyRocks with spinning disks
-to ensure sequential reads instead of random.
-Maximum allowed value is ``18446744073709551615``.
-
-.. note:: If you set this variable to a non-zero value,
-   :ref:`rocksdb_new_table_reader_for_compaction_inputs` is enabled.
-
-.. _rocksdb_compaction_sequential_deletes:
-
-.. rubric:: ``rocksdb_compaction_sequential_deletes``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--rocksdb-compaction-sequential-deletes``
-   * - Dynamic
-     - Yes
-   * - Scope
-     - Global
-   * - Data type
-     - Numeric
-   * - Default
-     - ``0``
-
-Specifies the threshold to trigger compaction on a file
-if it has more than this number of sequential delete markers.
-Default value is ``0`` meaning that compaction is not triggered
-regardless of the number of delete markers.
-Maximum allowed value is ``2000000`` (two million delete markers).
-
-.. note::
-
-   Depending on workload patterns, MyRocks can potentially maintain large
-   numbers of delete markers, which increases latency of queries.  This
-   compaction feature will reduce latency, but may also increase the MyRocks
-   write rate.  Use this variable together with
-   :ref:`rocksdb_compaction_sequential_deletes_file_size` to only perform
-   compaction on large files.
-
-.. _rocksdb_compaction_sequential_deletes_count_sd:
-
-.. rubric:: ``rocksdb_compaction_sequential_deletes_count_sd``
- 
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--rocksdb-compaction-sequential-deletes-count-sd``
-   * - Dynamic
-     - Yes
-   * - Scope
-     - Global
-   * - Data type
-     - Boolean
-   * - Default
-     - ``OFF``
-
-Specifies whether to count single deletes as delete markers
-recognized by :ref:`rocksdb_compaction_sequential_deletes`.
-Disabled by default.
-
-.. _rocksdb_compaction_sequential_deletes_file_size:
-
-.. rubric:: ``rocksdb_compaction_sequential_deletes_file_size``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--rocksdb-compaction-sequential-deletes-file-size``
-   * - Dynamic
-     - Yes
-   * - Scope
-     - Global
-   * - Data type
-     - Numeric
-   * - Default
-     - ``0``
-
-Specifies the minimum file size required to trigger compaction on it
-by :ref:`rocksdb_compaction_sequential_deletes`.
-Default value is ``0``,
-meaning that compaction is triggered regardless of file size.
-Allowed range is from ``-1`` to ``9223372036854775807``.
-
-.. _rocksdb_compaction_sequential_deletes_window:
-
-.. rubric:: ``rocksdb_compaction_sequential_deletes_window``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--rocksdb-compaction-sequential-deletes-window``
-   * - Dynamic
-     - Yes
-   * - Scope
-     - Global
-   * - Data type
-     - Numeric
-   * - Default
-     - ``0``
-
-Specifies the size of the window for counting delete markers
-by :ref:`rocksdb_compaction_sequential_deletes`.
-Default value is ``0``.
-Allowed range is up to ``2000000`` (two million).
-
-.. _rocksdb_concurrent_prepare:
-
-.. rubric:: ``rocksdb_concurrent_prepare``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--rocksdb-concurrent_prepare``
-   * - Dynamic
-     - No
-   * - Scope
-     - Global
-   * - Data type
-     - Boolean
-   * - Default
-     - ``ON``
-
-When enabled this variable allows/encourages threads that are using
-two-phase commit to ``prepare`` in parallel. This variable was
-renamed in upstream to :ref:`rocksdb_two_write_queues`.
-
-.. _rocksdb_create_checkpoint:
-
-.. rubric:: ``rocksdb_create_checkpoint``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--rocksdb-create-checkpoint``
-   * - Dynamic
-     - Yes
-   * - Scope
-     - Global
-   * - Data type
-     - String
-   * - Default
-     - 
-
-Specifies the directory where MyRocks should create a checkpoint.
-Empty by default.
-
-.. _rocksdb_create_if_missing:
-
-.. rubric:: ``rocksdb_create_if_missing``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--rocksdb-create-if-missing``
-   * - Dynamic
-     - No
-   * - Scope
-     - Global
-   * - Data type
-     - Boolean
-   * - Default
-     - ``ON``
-
-Specifies whether MyRocks should create its database if it does not exist.
-Enabled by default.
-
-.. _rocksdb_create_missing_column_families:
-
-.. rubric:: ``rocksdb_create_missing_column_families``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--rocksdb-create-missing-column-families``
-   * - Dynamic
-     - No
-   * - Scope
-     - Global
-   * - Data type
-     - Boolean
-   * - Default
-     - ``OFF``
-
-Specifies whether MyRocks should create new column families
-if they do not exist.
-Disabled by default.
-
-.. _rocksdb_create_temporary_checkpoint:
-
-.. rubric:: ``rocksdb_create_temporary_checkpoint``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--rocksdb-create-temporary-checkpoint``
-   * - Dynamic
-     - Yes
-   * - Scope
-     - Session
-   * - Data type
-     - String
-
-This variable has been implemented in :ref:`8.0.15-6`.
-When specified it will create a temporary RocksDB 'checkpoint' or
-'snapshot' in the `datadir`. If the session ends with an existing
-checkpoint, or if the variable is reset to another value, the checkpoint
-will get removed. This variable should be used by backup tools. Prolonged
-use or other misuse can have serious side effects to the server instance.
-
-.. _rocksdb_datadir:
-
-.. rubric:: ``rocksdb_datadir``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--rocksdb-datadir``
-   * - Dynamic
-     - No
-   * - Scope
-     - Global
-   * - Data type
-     - String
-   * - Default
-     - ``./.rocksdb``
-
-Specifies the location of the MyRocks data directory.
-By default, it is created in the current working directory.
-
-.. _rocksdb_db_write_buffer_size:
-
-.. rubric:: ``rocksdb_db_write_buffer_size``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--rocksdb-db-write-buffer-size``
-   * - Dynamic
-     - No
-   * - Scope
-     - Global
-   * - Data type
-     - Numeric
-   * - Default
-     - ``0``
-
-Specifies the maximum size of all memtables used to store writes in MyRocks
-across all column families. When this size is reached, the data is flushed
-to persistent media.
-The default value is ``0``.
-The allowed range is up to ``18446744073709551615``.
-
-.. _rocksdb_deadlock_detect:
-
-.. rubric:: ``rocksdb_deadlock_detect``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--rocksdb-deadlock-detect``
-   * - Dynamic
-     - Yes
-   * - Scope
-     - Global, Session
-   * - Data type
-     - Boolean
-   * - Default
-     - ``OFF``
-
-Specifies whether MyRocks should detect deadlocks.
-Disabled by default.
-
-.. _rocksdb_deadlock_detect_depth:
-
-.. rubric:: ``rocksdb_deadlock_detect_depth``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--rocksdb-deadlock-detect-depth``
-   * - Dynamic
-     - Yes
-   * - Scope
-     - Global, Session
-   * - Data type
-     - Numeric
-   * - Default
-     - ``50``
-
-Specifies the number of transactions deadlock detection will traverse
-through before assuming deadlock.
-
-.. _rocksdb_debug_optimizer_no_zero_cardinality:
-
-.. rubric:: ``rocksdb_debug_optimizer_no_zero_cardinality``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--rocksdb-debug-optimizer-no-zero-cardinality``
-   * - Dynamic
-     - Yes
-   * - Scope
-     - Global
-   * - Data type
-     - Boolean
-   * - Default
-     - ``ON``
-
-Specifies whether MyRocks should prevent zero cardinality
-by always overriding it with some value.
-
-.. _rocksdb_debug_ttl_ignore_pk:
-
-.. rubric:: ``rocksdb_debug_ttl_ignore_pk``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--rocksdb-debug-ttl-ignore-pk``
-   * - Dynamic
-     - Yes
-   * - Scope
-     - Global
-   * - Data type
-     - Boolean
-   * - Default
-     - ``OFF``
-
-For debugging purposes only. If true, compaction filtering will not occur
-on Primary Key TTL data. This variable is a no-op in non-debug builds.
-
-.. _rocksdb_debug_ttl_read_filter_ts:
-
-.. rubric:: ``rocksdb_debug_ttl_read_filter_ts``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--rocksdb_debug-ttl-read-filter-ts``
-   * - Dynamic
-     - Yes
-   * - Scope
-     - Global
-   * - Data type
-     - Numeric
-   * - Default
-     - ``0``
-
-For debugging purposes only.  Overrides the TTL read
-filtering time to time + `debug_ttl_read_filter_ts`.
-A value of ``0`` denotes that the variable is not set.
-This variable is a no-op in non-debug builds.
-
-.. _rocksdb_debug_ttl_rec_ts:
-
-.. rubric:: ``rocksdb_debug_ttl_rec_ts``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--rocksdb-debug-ttl-rec-ts``
-   * - Dynamic
-     - Yes
-   * - Scope
-     - Global
-   * - Data type
-     - Numeric
-   * - Default
-     - ``0``
-
-For debugging purposes only.  Overrides the TTL of
-records to ``now()`` + `debug_ttl_rec_ts`.
-The value can be +/- to simulate a record inserted in the past vs a record
-inserted in the  future . A value of ``0`` denotes that the
-variable is not set.
-This variable is a no-op in non-debug builds.
-
-.. _rocksdb_debug_ttl_snapshot_ts:
-
-.. rubric:: ``rocksdb_debug_ttl_snapshot_ts``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--rocksdb_debug_ttl_ignore_pk``
-   * - Dynamic
-     - Yes
-   * - Scope
-     - Global
-   * - Data type
-     - Numeric
-   * - Default
-     - ``0``
-
-For debugging purposes only. Sets the snapshot during
-compaction to ``now()`` + `rocksdb_debug_set_ttl_snapshot_ts`.
-
-The value can be +/- to simulate a snapshot in the past vs a
-snapshot created in the  future . A value of ``0`` denotes
-that the variable is not set. This variable is a no-op in
-non-debug builds.
-
-.. _rocksdb_default_cf_options:
-
-.. rubric:: ``rocksdb_default_cf_options``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--rocksdb-default-cf-options``
-   * - Dynamic
-     - No
-   * - Scope
-     - Global
-   * - Data type
-     - String
- 
-The dafaul value is: 
-
-| block_based_table_factory= {cache_index_and_filter_blocks=1;
-|                             filter_policy=bloomfilter:10:false;
-|                             whole_key_filtering=1};
-| level_compaction_dynamic_level_bytes=true;
-| optimize_filters_for_hits=true;
-| compaction_pri=kMinOverlappingRatio;
-| compression=kLZ4Compression;
-| bottommost_compression=kLZ4Compression;
-
-Specifies the default column family options for MyRocks. On startup, the
-server applies this option to all existing column families. This option is
-read-only at runtime.
-
-.. _rocksdb_delayed_write_rate:
-
-.. rubric:: ``rocksdb_delayed_write_rate``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--rocksdb-delayed-write-rate``
-   * - Dynamic
-     - Yes
-   * - Scope
-     - Global
-   * - Data type
-     - Numeric
-   * - Default
-     - ``16777216``
-
-Specifies the write rate in bytes per second, which should be used
-if MyRocks hits a soft limit or threshold for writes.
-Default value is ``16777216`` (16 MB/sec).
-Allowed range is from ``0`` to ``18446744073709551615``.
-
-.. _rocksdb_delete_cf:
-
-.. rubric:: ``rocksdb_delete_cf``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--rocksdb-delete-cf``
-   * - Dynamic
-     - Yes
-   * - Scope
-     - Global
-   * - Data type
-     - String
-   * - Default
-     - 
-
-The variable was implemented in :ref:`8.0.20-11`. Deletes the column family by name. The default value is   , an empty
-string.
-
-For example: ::
-
-    SET @@global.ROCKSDB_DELETE_CF = 'cf_primary_key';
-
-.. _rocksdb_delete_obsolete_files_period_micros:
-
-.. rubric:: ``rocksdb_delete_obsolete_files_period_micros``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--rocksdb-delete-obsolete-files-period-micros``
-   * - Dynamic
-     - No
-   * - Scope
-     - Global
-   * - Data type
-     - Numeric
-   * - Default
-     - ``21600000000``   
-
-Specifies the period in microseconds to delete obsolete files
-regardless of files removed during compaction.
-Default value is ``21600000000`` (6 hours).
-Allowed range is up to ``9223372036854775807``.
-
-.. _rocksdb_disable_file_deletions:
-
-.. rubric:: ``rocksdb_disable_file_deletions``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--rocksdb-disable-file-deletions``
-   * - Dynamic
-     - Yes
-   * - Scope
-     - Session
-   * - Data type
-     - Boolean
-   * - Default
-     - ``OFF``
-
-This variable has been implemented in :ref:`8.0.15-6`.
-It allows a client to temporarily disable RocksDB deletion
-of old ``WAL`` and ``.sst`` files for the purposes of making a consistent
-backup. If the client session terminates for any reason after disabling
-deletions and has not re-enabled deletions, they will be explicitly
-re-enabled. This variable should be used by backup tools. Prolonged
-use or other misuse can have serious side effects to the server instance.
-
-.. _rocksdb_enable_bulk_load_api:
-
-.. rubric:: ``rocksdb_enable_bulk_load_api``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--rocksdb-enable-bulk-load-api``
-   * - Dynamic
-     - No
-   * - Scope
-     - Global
-   * - Data type
-     - Boolean
-   * - Default
-     - ``ON``
-
-Specifies whether to use the ``SSTFileWriter`` feature for bulk loading,
-This feature bypasses the memtable,
-but requires keys to be inserted into the table
-in either ascending or descending order.
-Enabled by default.
-If disabled, bulk loading uses the normal write path via the memtable
-and does not require keys to be inserted in any order.
-
-.. _rocksdb_enable_insert_with_update_caching:
-
-.. rubric:: ``rocksdb_enable_insert_with_update_caching``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--rocksdb-enable-insert-with-update-caching``
-   * - Dynamic
-     - Yes
-   * - Scope
-     - Global
-   * - Data type
-     - Boolean
-   * - Default
-     - ``ON``
-
-The variable was implemented in :ref:`8.0.20-11`. Specifies whether to enable optimization where the read is cached from a failed insertion attempt in INSERT ON DUPLICATE KEY UPDATE.
-
-.. _rocksdb_enable_iterate_bounds:
-
-.. rubric:: ``rocksdb_enable_iterate_bounds``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--rocksdb-enable-iterate-bounds``
-   * - Dynamic
-     - Yes
-   * - Scope
-     - Global, Local
-   * - Data type
-     - Boolean
-   * - Default
-     - ``TRUE``
-
-The variable was implemented in :ref:`8.0.20-11`. Enables the rocksdb iterator upper bounds and lower bounds in read options.
-
-.. _rocksdb_enable_pipelined_write:
-
-.. rubric:: ``rocksdb_enable_pipelined_write``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--rocksdb-enable-pipelined-write``
-   * - Dynamic
-     - No
-   * - Scope
-     - Global
-   * - Data type
-     - Boolean
-   * - Default
-     - ``OFF``
-
-The variable was implemented in :ref:`8.0.25-15`.
-       
-DBOptions::enable_pipelined_write for RocksDB.
-
-If ``enable_pipelined_write`` is ``true``, a separate write thread is maintained for WAL write and memtable write. A write thread first enters the WAL writer queue and then the memtable writer queue. A pending thread on the WAL writer queue only waits for the previous WAL write operations but does not wait for memtable write operations. Enabling the feature may improve write throughput and reduce latency of the prepare phase of a two-phase commit.
-
-.. _rocksdb_enable_remove_orphaned_dropped_cfs:
-
-.. rubric:: ``rocksdb_enable_remove_orphaned_dropped_cfs``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--rocksdb-enable-remove-orphaned-dropped-cfs``
-   * - Dynamic
-     - Yes
-   * - Scope
-     - Global
-   * - Data type
-     - Boolean
-   * - Default
-     - ``TRUE``
-
-The variable was implemented in :ref:`8.0.20-11`. Enables the removal of dropped column families (cfs) from metadata if the cfs do not exist in the cf manager.
-
-The default value is ``TRUE``.
-
-.. _rocksdb_enable_ttl:
-
-.. rubric:: ``rocksdb_enable_ttl``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--rocksdb-enable-ttl``
-   * - Dynamic
-     - No
-   * - Scope
-     - Global
-   * - Data type
-     - Boolean
-   * - Default
-     - ``ON``
-
-Specifies whether to keep expired TTL records during compaction.
-Enabled by default.
-If disabled, expired TTL records will be dropped during compaction.
-
-.. _rocksdb_enable_ttl_read_filtering:
-
-.. rubric:: ``rocksdb_enable_ttl_read_filtering``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--rocksdb-enable-ttl-read-filtering``
-   * - Dynamic
-     - Yes
-   * - Scope
-     - Global
-   * - Data type
-     - Boolean
-   * - Default
-     - ``ON``
-
-For tables with TTL, expired records are skipped/filtered
-out during processing and in query results. Disabling
-this will allow these records to be seen, but as a result
-rows may disappear in the middle of transactions as they
-are dropped during compaction. **Use with caution.**
-
-.. _rocksdb_enable_thread_tracking:
-
-.. rubric:: ``rocksdb_enable_thread_tracking``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--rocksdb-enable-thread-tracking``
-   * - Dynamic
-     - No
-   * - Scope
-     - Global
-   * - Data type
-     - Boolean
-   * - Default
-     - ``OFF``
-
-Specifies whether to enable tracking the status of threads
-accessing the database.
-Disabled by default.
-If enabled, thread status will be available via ``GetThreadList()``.
-
-.. _rocksdb_enable_tmp_table:
-
-.. rubric:: ``rocksdb_enable_tmp_table``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--rocksdb-enable-tmp-table``
-   * - Dynamic
-     - No
-   * - Scope
-     - Global
-   * - Data type
-     - Boolean
-   * - Default
-     - ``OFF``
-    
-This variable has been implemented in :ref:`8.0.29-21`. Specifies whether to enable rocksdb tmp tables. Disabled by default.
-
-.. _rocksdb_enable_write_thread_adaptive_yield:
-
-.. rubric:: ``rocksdb_enable_write_thread_adaptive_yield``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--rocksdb-enable-write-thread-adaptive-yield``
-   * - Dynamic
-     - No
-   * - Scope
-     - Global
-   * - Data type
-     - Boolean
-   * - Default
-     - ``OFF``
-
-Specifies whether the MyRocks write batch group leader
-should wait up to the maximum allowed time
-before blocking on a mutex.
-Disabled by default.
-Enable it to increase throughput for concurrent workloads.
-
-.. _rocksdb_error_if_exists:
-
-.. rubric:: ``rocksdb_error_if_exists``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--rocksdb-error-if-exists``
-   * - Dynamic
-     - No
-   * - Scope
-     - Global
-   * - Data type
-     - Boolean
-   * - Default
-     - ``OFF``
-
-Specifies whether to report an error when a database already exists.
-Disabled by default.
-
-.. _rocksdb_error_on_suboptimal_collation:
-
-.. rubric:: ``rocksdb_error_on_suboptimal_collation``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--rocksdb-error-on-suboptimal-collation``
-   * - Dynamic
-     - No
-   * - Scope
-     - Global
-   * - Data type
-     - Boolean
-   * - Default
-     - ``ON``
-
-Specifies whether to report an error instead of a warning if an index is
-created on a char field where the table has a sub-optimal collation (case
-insensitive). Enabled by default.
-
-.. _rocksdb_flush_log_at_trx_commit:
-
-.. rubric:: ``rocksdb_flush_log_at_trx_commit``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--rocksdb-flush-log-at-trx-commit``
-   * - Dynamic
-     - Yes
-   * - Scope
-     - Global, Session
-   * - Data type
-     - Numeric
-   * - Default
-     - ``1``
-
-Specifies whether to sync on every transaction commit,
-similar to `innodb_flush_log_at_trx_commit <https://dev.mysql.com/doc/refman/8.0/en/innodb-parameters.html#sysvar_innodb_flush_log_at_trx_commit>`_.
-Enabled by default, which ensures ACID compliance.
-
-Possible values:
-
-* ``0``: Do not sync on transaction commit.
-  This provides better performance, but may lead to data inconsistency
-  in case of a crash.
-
-* ``1``: Sync on every transaction commit.
-  This is set by default and recommended
-  as it ensures data consistency,
-  but reduces performance.
-
-* ``2``: Sync every second.
-
-.. _rocksdb_flush_memtable_on_analyze:
-
-.. rubric:: ``rocksdb_flush_memtable_on_analyze``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--rocksdb-flush-memtable-on-analyze``
-   * - Dynamic
-     - Yes
-   * - Scope
-     - Global, Session
-   * - Data type
-     - Boolean
-   * - Default
-     - ``ON``
-
-Specifies whether to flush the memtable when running ``ANALYZE`` on a table.
-Enabled by default.
-This ensures accurate cardinality
-by including data in the memtable for calculating stats.
-
-.. _rocksdb_force_compute_memtable_stats:
-
-.. rubric:: ``rocksdb_force_compute_memtable_stats``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--rocksdb-force-compute-memtable-stats``
-   * - Dynamic
-     - Yes
-   * - Scope
-     - Global
-   * - Data type
-     - Boolean
-   * - Default
-     - ``ON``
-
-Specifies whether data in the memtables should be included
-for calculating index statistics
-used by the query optimizer.
-Enabled by default.
-This provides better accuracy, but may reduce performance.
-
-.. _rocksdb_force_compute_memtable_stats_cachetime:
-
-.. rubric:: ``rocksdb_force_compute_memtable_stats_cachetime``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--rocksdb-force-compute-memtable-stats-cachetime``
-   * - Dynamic
-     - Yes
-   * - Scope
-     - Global
-   * - Data type
-     - Numeric
-   * - Default
-     - ``60000000``
-
-Specifies for how long the cached value of memtable statistics should
-be used instead of computing it every time during the query plan analysis.
-
-.. _rocksdb_force_flush_memtable_and_lzero_now:
-
-.. rubric:: ``rocksdb_force_flush_memtable_and_lzero_now``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--rocksdb-force-flush-memtable-and-lzero-now``
-   * - Dynamic
-     - Yes
-   * - Scope
-     - Global
-   * - Data type
-     - Boolean
-   * - Default
-     - ``OFF``
-
-Works similar to :ref:`rocksdb_force_flush_memtable_now`
-but also flushes all L0 files.
-
-.. _rocksdb_force_flush_memtable_now:
-
-.. rubric:: ``rocksdb_force_flush_memtable_now``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--rocksdb-force-flush-memtable-now``
-   * - Dynamic
-     - Yes
-   * - Scope
-     - Global
-   * - Data type
-     - Boolean
-   * - Default
-     - ``ON``
-
-The default value has been changed from ``OFF`` to ``ON`` in :ref:`8.0.29-21`. This variable forces MyRocks to immediately flush all memtables out to data files.
-
-.. warning:: Use with caution!
-   Write requests will be blocked until all memtables are flushed.
-
-.. _rocksdb_force_index_records_in_range:
-
-.. rubric:: ``rocksdb_force_index_records_in_range``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--rocksdb-force-index-records-in-range``
-   * - Dynamic
-     - Yes
-   * - Scope
-     - Global, Session
-   * - Data type
-     - Numeric
-   * - Default
-     - ``1``
-
-Specifies the value used to override the number of rows
-returned to query optimizer when ``FORCE INDEX`` is used.
-Default value is ``1``.
-Allowed range is from ``0`` to ``2147483647``.
-Set to ``0`` if you do not want to override the returned value.
-
-.. _rocksdb_hash_index_allow_collision:
-
-.. rubric:: ``rocksdb_hash_index_allow_collision``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--rocksdb-hash-index-allow-collision``
-   * - Dynamic
-     - No
-   * - Scope
-     - Global
-   * - Data type
-     - Boolean
-   * - Default
-     - ``ON``
-
-This variable was removed in :ref:`8.0.29-21`. The variable specifies whether hash collisions are allowed. 
-Enabled by default, which uses less memory. If disabled, full prefix is stored to prevent hash collisions.
-
-.. _rocksdb_ignore_unknown_options:
-
-.. rubric:: ``rocksdb_ignore_unknown_options``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ````
-   * - Dynamic
-     - No
-   * - Scope
-     - Global
-   * - Data type
-     - Boolean
-   * - Default
-     - ``ON``
-
-When enabled, it allows RocksDB to receive unknown options and not exit.
-
-.. _rocksdb_index_type:
-
-.. rubric:: ``rocksdb_index_type``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--rocksdb-index-type``
-   * - Dynamic
-     - No
-   * - Scope
-     - Global
-   * - Data type
-     - Enum
-   * - Default
-     - ``kBinarySearch``
-
-Specifies the type of indexing used by MyRocks:
-
-* ``kBinarySearch``: Binary search (default).
-
-* ``kHashSearch``: Hash search.
-
-.. _rocksdb_info_log_level:
-
-.. rubric:: ``rocksdb_info_log_level``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--rocksdb-info-log-level``
-   * - Dynamic
-     - Yes
-   * - Scope
-     - Global
-   * - Data type
-     - Enum
-   * - Default
-     - ``error_level``
-
-Specifies the level for filtering messages written by MyRocks
-to the ``mysqld`` log.
-
-* ``debug_level``: Maximum logging (everything including debugging
-  log messages)
-* ``info_level``
-* ``warn_level``
-* ``error_level`` (default)
-* ``fatal_level``: Minimum logging (only fatal error messages logged)
-
-.. _rocksdb_instant_ddl:
-
-.. rubric:: ``rocksdb_instant_ddl``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--rocksdb-instant-ddl``
-   * - Dynamic
-     - Yes
-   * - Scope
-     - Global
-   * - Data type
-     - Boolean
-   * - Default
-     - ``OFF``
-
-This variable has been implemented in :ref:`8.0.29-21`. Specifies whether to enable instant ddl during alter table. Disabled by default.
-
-.. _rocksdb_is_fd_close_on_exec:
-
-.. rubric:: ``rocksdb_is_fd_close_on_exec``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--rocksdb-is-fd-close-on-exec``
-   * - Dynamic
-     - No
-   * - Scope
-     - Global
-   * - Data type
-     - Boolean
-   * - Default
-     - ``ON``
-
-Specifies whether child processes should inherit open file jandles.
-Enabled by default.
-
-.. _rocksdb_large_prefix:
-
-.. rubric:: ``rocksdb_large_prefix``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--rocksdb-large-prefix``
-   * - Dynamic
-     - Yes
-   * - Scope
-     - Global
-   * - Data type
-     - Boolean
-   * - Default
-     - ``TRUE``
-
-
-When enabled, this option allows index key prefixes longer than 767 bytes (up to
-3072 bytes). The values for :ref:`rocksdb_large_prefix` should be the same between
-source and replica.
-
-.. note::
-
-    In version :ref:`8.0.16-7` and later, the default value is changed to ``TRUE``.
-
-.. _rocksdb_keep_log_file_num:
-
-.. rubric:: ``rocksdb_keep_log_file_num``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--rocksdb-keep-log-file-num``
-   * - Dynamic
-     - No
-   * - Scope
-     - Global
-   * - Data type
-     - Numeric
-   * - Default
-     - ``1000``
-
-Specifies the maximum number of info log files to keep.
-Default value is ``1000``.
-Allowed range is from ``1`` to ``18446744073709551615``.
-
-.. _rocksdb_lock_scanned_rows:
-
-.. rubric:: ``rocksdb_lock_scanned_rows``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--rocksdb-lock-scanned-rows``
-   * - Dynamic
-     - Yes
-   * - Scope
-     - Global, Session
-   * - Data type
-     - Boolean
-   * - Default
-     - ``OFF``
-
-Specifies whether to hold the lock on rows that are scanned during ``UPDATE``
-and not actually updated.
-Disabled by default.
-
-.. _rocksdb_lock_wait_timeout:
-
-.. rubric:: ``rocksdb_lock_wait_timeout``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--rocksdb-lock-wait-timeout``
-   * - Dynamic
-     - Yes
-   * - Scope
-     - Global, Session
-   * - Data type
-     - Numeric
-   * - Default
-     - ``1``
-
-Specifies the number of seconds MyRocks should wait to acquire a row lock
-before aborting the request.
-Default value is ``1``.
-Allowed range is up to ``1073741824``.
-
-.. _rocksdb_log_file_time_to_roll:
-
-.. rubric:: ``rocksdb_log_file_time_to_roll``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--rocksdb-log-file-time-to-roll``
-   * - Dynamic
-     - No
-   * - Scope
-     - Global
-   * - Data type
-     - Numeric
-   * - Default
-     - ``0``
-
-Specifies the period (in seconds) for rotating the info log files.
-Default value is ``0``, meaning that the log file is not rotated.
-Allowed range is up to ``18446744073709551615``.
-
-.. _rocksdb_manifest_preallocation_size:
-
-.. rubric:: ``rocksdb_manifest_preallocation_size``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--rocksdb-manifest-preallocation-size``
-   * - Dynamic
-     - No
-   * - Scope
-     - Global
-   * - Data type
-     - Numeric
-   * - Default
-     - ``0``
-
-Specifies the number of bytes to preallocate for the MANIFEST file
-used by MyRocks to store information
-about column families, levels, active files, etc.
-Default value is ``0``.
-Allowed range is up to ``18446744073709551615``.
-
-.. note::
-
-   A value of ``4194304`` (4 MB) is reasonable to reduce random I/O on XFS.
-
-.. _rocksdb_manual_compaction_bottommost_level:
-
-.. rubric:: ``rocksdb_manual_compaction_bottommost_level``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--rocksdb-manual-compaction-bottommost-level``
-   * - Dynamic
-     - Yes
-   * - Scope
-     - Local
-   * - Data type
-     - Enum
-   * - Default
-     - ``kForceOptimized``
-
-Option for bottommost level compaction during manual compaction:
-  
-  * kSkip - Skip bottommost level compaction
-
-  * kIfHaveCompactionFilter - Only compact bottommost level if there is a compaction filter
-
-  * kForce - Always compact bottommost level
-
-  * kForceOptimized -  Always compact bottommost level but in bottommost level avoid double-compacting files created in the same compaction
-
-.. _rocksdb_manual_wal_flush:
-
-.. rubric:: ``rocksdb_manual_wal_flush``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--rocksdb-manual-wal-flush``
-   * - Dynamic
-     - No
-   * - Scope
-     - Global
-   * - Data type
-     - Boolean
-   * - Default
-     - ``ON``
-
-This variable can be used to disable automatic/timed WAL flushing and instead
-rely on the application to do the flushing.
-
-.. _rocksdb_master_skip_tx_api:
-
-.. rubric:: ``rocksdb_master_skip_tx_api``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ````
-   * - Dynamic
-     - Yes
-   * - Scope
-     - Global, Session
-   * - Data type
-     - Boolean
-   * - Default
-     - ``OFF``
-
-The variable was implemented in :ref:`8.0.20-11`. When enabled, uses the WriteBatch API, which is faster. The session does not hold any lock on row access. This variable is not effective on replica.
-
-.. note::
-
-    Due to the disabled row locks, improper use of the variable can cause data
-    corruption or inconsistency.
-
-.. _rocksdb_max_background_compactions:
-
-.. rubric:: ``rocksdb_max_background_compactions``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--rocksdb-max-background-compactions``
-   * - Dynamic
-     - Yes
-   * - Scope
-     - Global
-   * - Data type
-     - Numeric
-   * - Default
-     - ``-1``
-
-The variable was implemented in :ref:`8.0.20-11`.
-
-Sets DBOptions:: max_background_compactions for RocksDB.
-The default value is ``-1`` The allowed range is ``-1`` to ``64``.
-This variable was replaced
-by :ref:`rocksdb_max_background_jobs`, which automatically decides how
-many threads to allocate towards flush/compaction.
-This variable was re-implemented in :ref:`8.0.20-11`.
-
-.. _rocksdb_max_background_flushes:
-
-.. rubric:: ``rocksdb_max_background_flushes``
- 
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--rocksdb-max-background-flushes``
-   * - Dynamic
-     - No
-   * - Scope
-     - Global
-   * - Data type
-     - Numeric
-   * - Default
-     - ``-1``
-
-The variable was implemented in :ref:`8.0.20-11`.
-
-Sets DBOptions:: max_background_flushes for RocksDB.
-The default value is ``-1``. The allowed range is ``-1`` to ``64``.
-This variable has been replaced
-by :ref:`rocksdb_max_background_jobs`, which automatically decides how
-many threads to allocate towards flush/compaction.
-This variable was re-implemented in :ref: `8.0.20-11`.
-
-.. _rocksdb_max_background_jobs:
-
-.. rubric:: ``rocksdb_max_background_jobs``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--rocksdb-max-background-jobs``
-   * - Dynamic
-     - Yes
-   * - Scope
-     - Global
-   * - Data type
-     - Numeric
-   * - Default
-     - ``2``
-
-This variable replaced :ref:`rocksdb_base_background_compactions`,
-:ref:`rocksdb_max_background_compactions`, and
-:ref:`rocksdb_max_background_flushes` variables. This variable specifies the maximum number of background jobs. It automatically decides
-how many threads to allocate towards flush/compaction. It was implemented to
-reduce the number of (confusing) options users and can tweak and push the
-responsibility down to RocksDB level.
-
-.. _rocksdb_max_bottom_pri_background_compactions:
-
-.. rubric:: ``rocksdb_max_bottom_pri_background_compactions``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--rocksdb_max_bottom_pri_background_compactions``
-   * - Dynamic
-     - No
-   * - Data type
-     - Unsigned integer
-   * - Default
-     - ``0``
-
-The variable was implemented in :ref:`8.0.20-11`. Creates a specified number of threads, sets a lower CPU priority, and letting compactions use them. The maximum compaction concurrency is capped by ``rocksdb_max_background_compactions`` or ``rocksdb_max_background_jobs``
-
-The minimum value is ``0`` and the maximum value is ``64``.
-
-.. _rocksdb_max_compaction_history:
-
-.. rubric:: ``rocksdb_max_compaction_history``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--rocksdb-max-compaction-history``
-   * - Dynamic
-     - Yes
-   * - Scope
-     - Global
-   * - Data type
-     - Unsigned integer
-   * - Default
-     - ``64``
-
-The minimum value is ``0`` and the maximum value is ``UINT64_MAX``.
-
-Tracks the history for at most ``rockdb_mx_compaction_history`` completed compactions. The history is in the INFORMATION_SCHEMA.ROCKSDB_COMPACTION_HISTORY table.
-
-.. _rocksdb_max_latest_deadlocks:
-
-.. rubric:: ``rocksdb_max_latest_deadlocks``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--rocksdb-max-latest-deadlocks``
-   * - Dynamic
-     - Yes
-   * - Scope
-     - Global
-   * - Data type
-     - Numeric
-   * - Default
-     - ``5``
-
-Specifies the maximum number of recent deadlocks to store.
-
-.. _rocksdb_max_log_file_size:
-
-.. rubric:: ``rocksdb_max_log_file_size``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--rocksdb-max-log-file-size``
-   * - Dynamic
-     - No
-   * - Scope
-     - Global
-   * - Data type
-     - Numeric
-   * - Default
-     - ``0``
-
-Specifies the maximum size for info log files,
-after which the log is rotated.
-Default value is ``0``, meaning that only one log file is used.
-Allowed range is up to ``18446744073709551615``.
-
-Also see :ref:`rocksdb_log_file_time_to_roll`.
-
-.. _rocksdb_max_manifest_file_size:
-
-.. rubric:: ``rocksdb_max_manifest_file_size``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--rocksdb-manifest-log-file-size``
-   * - Dynamic
-     - No
-   * - Scope
-     - Global
-   * - Data type
-     - Numeric
-   * - Default
-     - ``18446744073709551615``
-
-Specifies the maximum size of the MANIFEST data file,
-after which it is rotated.
-Default value is also the maximum, making it practically unlimited:
-only one manifest file is used.
-
-.. _rocksdb_max_open_files:
-
-.. rubric:: ``rocksdb_max_open_files``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--rocksdb-max-open-files``
-   * - Dynamic
-     - No
-   * - Scope
-     - Global
-   * - Data type
-     - Numeric
-   * - Default
-     - ``1000``
-
-Specifies the maximum number of file handles opened by MyRocks.
-Values in the range between ``0`` and ``open_files_limit``
-are taken as they are. If :ref:`rocksdb_max_open_files` value is
-greater than ``open_files_limit``, it will be reset to 1/2 of
-``open_files_limit``, and a warning will be emitted to the ``mysqld``
-error log. A value of ``-2`` denotes auto tuning: just sets
-:ref:`rocksdb_max_open_files` value to 1/2 of ``open_files_limit``.
-Finally, ``-1`` means no limit, i.e. an infinite number of file handles.
-
-.. warning::
-
-  Setting :ref:`rocksdb_max_open_files` to ``-1`` is dangerous,
-  as server may quickly run out of file handles in this case.
-
-.. _rocksdb_max_row_locks:
-
-.. rubric:: ``rocksdb_max_row_locks``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--rocksdb-max-row-locks``
-   * - Dynamic
-     - Yes
-   * - Scope
-     - Global
-   * - Data type
-     - Numeric
-   * - Default
-     - ``1048576``
-
-Specifies the limit on the maximum number of row locks a transaction can have
-before it fails.
-Default value is also the maximum, making it practically unlimited:
-transactions never fail due to row locks.
-
-.. _rocksdb_max_subcompactions:
-
-.. rubric:: ``rocksdb_max_subcompactions``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--rocksdb-max-subcompactions``
-   * - Dynamic
-     - No
-   * - Scope
-     - Global
-   * - Data type
-     - Numeric
-   * - Default
-     - ``1``
-
-Specifies the maximum number of threads allowed for each compaction job.
-Default value of ``1`` means no subcompactions (one thread per compaction job).
-Allowed range is up to ``64``.
-
-.. _rocksdb_max_total_wal_size:
-
-.. rubric:: ``rocksdb_max_total_wal_size``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--rocksdb-max-total-wal-size``
-   * - Dynamic
-     - No
-   * - Scope
-     - Global
-   * - Data type
-     - Numeric
-   * - Default
-     - 2 GB
-
-Specifies the maximum total size of WAL (write-ahead log) files,
-after which memtables are flushed.
-Default value is ``2 GB``
-The allowed range is up to ``9223372036854775807``.
-
-.. _rocksdb_merge_buf_size:
-
-.. rubric:: ``rocksdb_merge_buf_size``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--rocksdb-merge-buf-size``
-   * - Dynamic
-     - Yes
-   * - Scope
-     - Global
-   * - Data type
-     - Numeric
-   * - Default
-     - ``67108864``
-
-Specifies the size (in bytes) of the merge-sort buffers
-used to accumulate data during secondary key creation.
-New entries are written directly to the lowest level in the database,
-instead of updating indexes through the memtable and L0.
-These values are sorted using merge-sort,
-with buffers set to 64 MB by default (``67108864``).
-Allowed range is from ``100`` to ``18446744073709551615``.
-
-.. _rocksdb_merge_combine_read_size:
-
-.. rubric:: ``rocksdb_merge_combine_read_size``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--rocksdb-merge-combine-read-size``
-   * - Dynamic
-     - Yes
-   * - Scope
-     - Global
-   * - Data type
-     - Numeric
-   * - Default
-     - ``1073741824``
-
-Specifies the size (in bytes) of the merge-combine buffer
-used for the merge-sort algorithm
-as described in :ref:`rocksdb_merge_buf_size`.
-Default size is 1 GB (``1073741824``).
-Allowed range is from ``100`` to ``18446744073709551615``.
-
-.. _rocksdb_merge_tmp_file_removal_delay_ms:
-
-.. rubric:: ``rocksdb_merge_tmp_file_removal_delay_ms``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--rocksdb_merge_tmp_file_removal_delay_ms``
-   * - Dynamic
-     - Yes
-   * - Scope
-     - Global, Session
-   * - Data type
-     - Numeric
-   * - Default
-     - ``0``
-
-Fast secondary index creation creates merge files when needed. After finishing
-secondary index creation, merge files are removed. By default, the file removal
-is done without any sleep, so removing GBs of merge files within <1s may
-happen, which will cause trim stalls on Flash. This variable can be used to
-rate limit the delay in milliseconds.
-
-.. _rocksdb_new_table_reader_for_compaction_inputs:
-
-.. rubric:: ``rocksdb_new_table_reader_for_compaction_inputs``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--rocksdb-new-table-reader-for-compaction-inputs``
-   * - Dynamic
-     - No
-   * - Scope
-     - Global
-   * - Data type
-     - Boolean
-   * - Default
-     - ``OFF``
-
-This variable was removed in :ref:`8.0.29-21`. The variable specifies whether MyRocks should create a new file descriptor and table reader for each compaction input. 
-Disabled by default. If you enable this variable, the memory consumption may increase, but it will also allow to specify pre-fetch options for compaction input files without impacting table readers used for user queries.
-
-.. _rocksdb_no_block_cache:
-
-.. rubric:: ``rocksdb_no_block_cache``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--rocksdb-no-block-cache``
-   * - Dynamic
-     - No
-   * - Scope
-     - Global
-   * - Data type
-     - Boolean
-   * - Default
-     - ``OFF``
-
-Specifies whether to disable the block cache for column families.
-Variable is disabled by default,
-meaning that using the block cache is allowed.
-
-.. _rocksdb_no_create_column_family:
-
-.. rubric:: ``rocksdb_no_create_column_family``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--rocksdb-no-create-column-family``
-   * - Dynamic
-     - No
-   * - Scope
-     - Global
-   * - Data type
-     - Boolean
-   * - Default
-     - ``ON``
-
-Controls the processing of the column family name given in the ``COMMENT``
-clause in the ``CREATE TABLE`` or ``ALTER TABLE`` statement in case the column family
-name does not refer to an existing column family.
-
-If :ref:`rocksdb_no_create_column_family` is set to `NO`, a new column family will be created and the new index will
-be placed into it.
-
-If :ref:`rocksdb_no_create_column_family` is set to `YES`, no new column family will be created and the index will be
-placed into the `default` column family. A warning is issued in this case informing that
-the specified column family does not exist and cannot be created.
-
-.. seealso::
-
-   More information about column families
-      :ref:`ps.myrocks.column-family`
-
-.. _rocksdb_override_cf_options:
-
-.. rubric:: ``rocksdb_override_cf_options``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--rocksdb-override-cf-options``
-   * - Dynamic
-     - No
-   * - Scope
-     - Global
-   * - Data type
-     - String
-   * - Default
-       
-Specifies option overrides for each column family.
-Empty by default.
-
-.. _rocksdb_paranoid_checks:
-
-.. rubric:: ``rocksdb_paranoid_checks``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--rocksdb-paranoid-checks``
-   * - Dynamic
-     - No
-   * - Scope
-     - Global
-   * - Data type
-     - Boolean
-   * - Default
-     - ``ON``
-
-Specifies whether MyRocks should re-read the data file
-as soon as it is created to verify correctness.
-Enabled by default.
-
-.. _rocksdb_partial_index_sort_max_mem:
-
-.. rubric:: ``rocksdb_partial_index_sort_max_mem``
- 
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--rocksdb-partial-index-sort-max-mem``
-   * - Dynamic
-     - Yes
-   * - Scope
-     - Local
-   * - Data type
-     - Unsigned Integer
-   * - Default
-     - ``0``
-
-The variable was implemented in :ref:`8.0.27-18`. Maximum memory to use when sorting an unmaterialized group for partial indexes. The 0(zero) value is defined as no limit.
-
-.. _rocksdb_pause_background_work:
-
-.. rubric:: ``rocksdb_pause_background_work``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--rocksdb-pause-background-work``
-   * - Dynamic
-     - Yes
-   * - Scope
-     - Global
-   * - Data type
-     - Boolean
-   * - Default
-     - ``OFF``
-
-Specifies whether MyRocks should pause all background operations.
-Disabled by default. There is no practical reason for a user to ever
-use this variable because it is intended as a test synchronization tool
-for the MyRocks MTR test suites.
-
-.. warning::
-
-  If someone were to set a :ref:`rocksdb_force_flush_memtable_now` to
-  ``1`` while :ref:`rocksdb_pause_background_work` is set to ``1``,
-  the client that issued the ``rocksdb_force_flush_memtable_now=1`` will be
-  blocked indefinitely until :ref:`rocksdb_pause_background_work`
-  is set to ``0``.
-
-.. _rocksdb_perf_context_level:
-
-.. rubric:: ``rocksdb_perf_context_level``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--rocksdb-perf-context-level``
-   * - Dynamic
-     - Yes
-   * - Scope
-     - Global, Session
-   * - Data type
-     - Numeric
-   * - Default
-     - ``0``
-
-Specifies the level of information to capture with the Perf Context plugins.
-Default value is ``0``.
-Allowed range is up to ``4``.
-
-.. _rocksdb_persistent_cache_path:
-
-.. rubric:: ``rocksdb_persistent_cache_path``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--rocksdb-persistent-cache-path``
-   * - Dynamic
-     - No
-   * - Scope
-     - Global
-   * - Data type
-     - String
-   * - Default
-       
-Specifies the path to the persistent cache.
-Set this together with :ref:`rocksdb_persistent_cache_size_mb`.
-
-.. _rocksdb_persistent_cache_size_mb:
-
-.. rubric:: ``rocksdb_persistent_cache_size_mb``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--rocksdb-persistent-cache-size-mb``
-   * - Dynamic
-     - No
-   * - Scope
-     - Global
-   * - Data type
-     - Numeric
-   * - Default
-     - ``0``
-
-Specifies the size of the persisten cache in megabytes.
-Default is ``0`` (persistent cache disabled).
-Allowed range is up to ``18446744073709551615``.
-Set this together with :ref:`rocksdb_persistent_cache_path`.
-
-.. _rocksdb_pin_l0_filter_and_index_blocks_in_cache:
-
-.. rubric:: ``rocksdb_pin_l0_filter_and_index_blocks_in_cache``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--rocksdb-pin-l0-filter-and-index-blocks-in-cache``
-   * - Dynamic
-     - No
-   * - Scope
-     - Global
-   * - Data type
-     - Boolean
-   * - Default
-     - ``ON``
-
-Specifies whether MyRocks pins the filter and index blocks in the cache
-if :ref:`rocksdb_cache_index_and_filter_blocks` is enabled.
-Enabled by default.
-
-.. _rocksdb_print_snapshot_conflict_queries:
-
-.. rubric:: ``rocksdb_print_snapshot_conflict_queries``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--rocksdb-print-snapshot-conflict-queries``
-   * - Dynamic
-     - Yes
-   * - Scope
-     - Global
-   * - Data type
-     - Boolean
-   * - Default
-     - ``OFF``
-
-Specifies whether queries that generate snapshot conflicts
-should be logged to the error log.
-Disabled by default.
-
-.. _rocksdb_rate_limiter_bytes_per_sec:
-
-.. rubric:: ``rocksdb_rate_limiter_bytes_per_sec``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--rocksdb-rate-limiter-bytes-per-sec``
-   * - Dynamic
-     - Yes
-   * - Scope
-     - Global
-   * - Data type
-     - Numeric
-   * - Default
-     - ``0``
-
-Specifies the maximum rate at which MyRocks can write to media
-via memtable flushes and compaction.
-Default value is ``0`` (write rate is not limited).
-Allowed range is up to ``9223372036854775807``.
-
-.. _rocksdb_read_free_rpl:
-
-.. rubric:: ``rocksdb_read_free_rpl``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--rocksdb-read-free-rpl``
-   * - Dynamic
-     - Yes
-   * - Scope
-     - Global
-   * - Data type
-     - Enum
-   * - Default
-     - ``OFF``
-
-The variable was implemented in :ref:`8.0.20-11`. Uses read-free replication, which allows no row lookup during
-replication, on the replica.
-
-The options are the following:
-
-* OFF - Disables the variable
-* PK_SK - Enables the variable on all tables with a primary key
-* PK_ONLY - Enables the variable on tables where the only key is the primary key
-   
-.. _rocksdb_read_free_rpl_tables:
-
-.. rubric:: ``rocksdb_read_free_rpl_tables`` 
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--rocksdb-read-free-rpl-tables``
-   * - Dynamic
-     - Yes
-   * - Scope
-     - Global, Session
-   * - Data type
-     - String
-   * - Default
-     -       
-
-The variable was disabled in :ref:`8.0.20-11`. We recommend that you use ``rocksdb_read_free_rpl`` instead of this variable.
-
-This variable lists tables (as a regular expression)
-that should use read-free replication on the replica
-(that is, replication without row lookups).
-Empty by default.
-
-.. _rocksdb_records_in_range:
-
-.. rubric:: ``rocksdb_records_in_range``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--rocksdb-records-in-range``
-   * - Dynamic
-     - Yes
-   * - Scope
-     - Global, Session
-   * - Data type
-     - Numeric
-   * - Default
-     - ``0``
-
-Specifies the value to override the result of ``records_in_range()``.
-Default value is ``0``.
-Allowed range is up to ``2147483647``.
-
-.. _rocksdb_reset_stats:
-
-.. rubric:: ``rocksdb_reset_stats``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--rocksdb-reset-stats``
-   * - Dynamic
-     - Yes
-   * - Scope
-     - Global
-   * - Data type
-     - Boolean
-   * - Default
-     - ``OFF``
-
-Resets MyRocks internal statistics dynamically
-(without restarting the server).
-
-.. _rocksdb_rollback_on_timeout:
-
-.. rubric:: ``rocksdb_rollback_on_timeout``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--rocksdb-rollback-on-timeout``
-   * - Dynamic
-     - Yes
-   * - Scope
-     - Global
-   * - Data type
-     - Boolean
-   * - Default
-     - ``OFF``
-
-The variable was implemented in :ref:`8.0.20-11`. By default, only the last statement on a transaction is rolled back. If
-``--rocksdb-rollback-on-timeout=ON``, a transaction timeout causes a rollback of
-the entire transaction.
-
-.. _rocksdb_rpl_skip_tx_api:
-
-.. rubric:: ``rocksdb_rpl_skip_tx_api``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--rocksdb-rpl-skip-tx-api``
-   * - Dynamic
-     - No
-   * - Scope
-     - Global
-   * - Data type
-     - Boolean
-   * - Default
-     - ``OFF``
-
-Specifies whether write batches should be used for replication thread
-instead of the transaction API.
-Disabled by default.
-
-There are two conditions which are necessary to
-use it: row replication format and replica
-operating in super read only mode.
-
-.. _rocksdb_seconds_between_stat_computes:
-
-.. rubric:: ``rocksdb_seconds_between_stat_computes``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--rocksdb-seconds-between-stat-computes``
-   * - Dynamic
-     - Yes
-   * - Scope
-     - Global
-   * - Data type
-     - Numeric
-   * - Default
-     - ``3600``
-
-Specifies the number of seconds to wait
-between recomputation of table statistics for the optimizer.
-During that time, only changed indexes are updated.
-Default value is ``3600``.
-Allowed is from ``0`` to ``4294967295``.
-
-.. _rocksdb_signal_drop_index_thread:
-
-.. rubric:: ``rocksdb_signal_drop_index_thread``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--rocksdb-signal-drop-index-thread``
-   * - Dynamic
-     - Yes
-   * - Scope
-     - Global
-   * - Data type
-     - Boolean
-   * - Default
-     - ``OFF``
-
-Signals the MyRocks drop index thread to wake up.
-
-.. _rocksdb_sim_cache_size:
-
-.. rubric:: ``rocksdb_sim_cache_size``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--rocksdb-sim-cache-size``
-   * - Dynamic
-     - No
-   * - Scope
-     - Global
-   * - Data type
-     - Numeric
-   * - Default
-     - ``0``
-
-Enables the simulated cache, which allows us to figure out the hit/miss rate
-with a specific cache size without changing the real block cache.
-
-.. _rocksdb_skip_bloom_filter_on_read:
-
-.. rubric:: ``rocksdb_skip_bloom_filter_on_read``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--rocksdb-skip-bloom-filter-on_read``
-   * - Dynamic
-     - Yes
-   * - Scope
-     - Global, Session
-   * - Data type
-     - Boolean
-   * - Default
-     - ``OFF``
-
-Specifies whether bloom filters should be skipped on reads.
-Disabled by default (bloom filters are not skipped).
-
-.. _rocksdb_skip_fill_cache:
-
-.. rubric:: ``rocksdb_skip_fill_cache``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--rocksdb-skip-fill-cache``
-   * - Dynamic
-     - Yes
-   * - Scope
-     - Global, Session
-   * - Data type
-     - Boolean
-   * - Default
-     - ``OFF```
-
-Specifies whether to skip caching data on read requests.
-Disabled by default (caching is not skipped).
-
-.. _rocksdb_skip_locks_if_skip_unique_check:
-
-.. rubric:: ``rocksdb_skip_locks_if_skip_unique_check``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``rocksdb_skip_locks_if_skip_unique_check``
-   * - Dynamic
-     - Yes
-   * - Scope
-     - Global
-   * - Data type
-     - Boolean
-   * - Default
-     - OFF
-
-Skip row locking when unique checks are disabled.
-
-.. _rocksdb_sst_mgr_rate_bytes_per_sec:
-
-.. rubric:: ``rocksdb_sst_mgr_rate_bytes_per_sec``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--rocksdb-sst-mgr-rate-bytes-per-sec``
-   * - Dynamic
-     - Yes
-   * - Scope
-     - Global, Session
-   * - Data type
-     - Numeric
-   * - Default
-     - ``0``
-
-Specifies the maximum rate for writing to data files.
-Default value is ``0``. This option is not effective on HDD.
-Allowed range is from ``0`` to ``18446744073709551615``.
-
-.. _rocksdb_stats_dump_period_sec:
-
-.. rubric:: ``rocksdb_stats_dump_period_sec``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--rocksdb-stats-dump-period-sec``
-   * - Dynamic
-     - No
-   * - Scope
-     - Global
-   * - Data type
-     - Numeric
-   * - Default
-     - ``600``
-
-Specifies the period in seconds for performing a dump of the MyRocks statistics
-to the info log.
-Default value is ``600``.
-Allowed range is up to ``2147483647``.
-
-.. _rocksdb_stats_level:
-
-.. rubric:: ``rocksdb_stats_level``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--rocksdb-stats-level``
-   * - Dynamic
-     - Yes
-   * - Scope
-     - Global
-   * - Data type
-     - Numeric
-   * - Default
-     - ``0``
-
-The variable was implemented in :ref:`8.0.20-11`. Controls the RocksDB statistics level. The default value is "0" (kExceptHistogramOrTimers), which is the fastest level. The maximum value is "4".
-
-.. _rocksdb_stats_recalc_rate:
-
-.. rubric:: ``rocksdb_stats_recalc_rate``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--rocksdb-stats-recalc-rate``
-   * - Dynamic
-     - No
-   * - Scope
-     - Global
-   * - Data type
-     - Numeric
-   * - Default
-     - ``0``
-
-The variable was implemented in :ref:`8.0.20-11`. Specifies the number of indexes to recalculate per second. Recalculating index statistics periodically ensures it to match the actual sum from SST files.
-Default value is ``0``. Allowed range is up to ``4294967295``.
-
-.. _rocksdb_store_row_debug_checksums:
-
-.. rubric:: ``rocksdb_store_row_debug_checksums``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--rocksdb-store-row-debug-checksums``
-   * - Dynamic
-     - Yes
-   * - Scope
-     - Global
-   * - Data type
-     - Boolean
-   * - Default
-     - ``OFF``
-
-Specifies whether to include checksums when writing index or table records.
-Disabled by default.
-
-.. _rocksdb_strict_collation_check:
-
-.. rubric:: ``rocksdb_strict_collation_check``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--rocksdb-strict-collation-check``
-   * - Dynamic
-     - Yes
-   * - Scope
-     - Global
-   * - Data type
-     - Boolean
-   * - Default
-     - ``ON``
-
-This variable is considered **deprecated** in version 8.0.23-14.
-
-Specifies whether to check and verify
-that table indexes have proper collation settings.
-Enabled by default.
-
-.. _rocksdb_strict_collation_exceptions:
-
-.. rubric:: ``rocksdb_strict_collation_exceptions``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--rocksdb-strict-collation-exceptions``
-   * - Dynamic
-     - Yes
-   * - Scope
-     - Global
-   * - Data type
-     - String
-   * - Default
-     - 
-
-This variable is considered **deprecated** in version 8.0.23-14.
-
-Lists tables (as a regular expression) that should be excluded
-from verifying case-sensitive collation
-enforced by :ref:`rocksdb_strict_collation_check`.
-Empty by default.
-
-.. _rocksdb_table_cache_numshardbits:
-
-.. rubric:: ``rocksdb_table_cache_numshardbits``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--rocksdb-table-cache-numshardbits``
-   * - Dynamic
-     - No
-   * - Scope
-     - Global
-   * - Data type
-     - Numeric
-   * - Default
-     - ``6``
-
-Specifies the number if table caches.
-The default value is ``6``.
-The allowed range is from ``0`` to ``19``.
-
-.. _rocksdb_table_stats_background_thread_nice_value:
-
-.. rubric:: ``rocksdb_table_stats_background_thread_nice_value``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--rocksdb-table-stats-background-thread-nice-value``
-   * - Dynamic
-     - Yes
-   * - Scope
-     - Global
-   * - Data type
-     - Numeric
-   * - Default
-     - ``19``
-
-The variable was implemented in :ref:`8.0.20-11`.
-
-The nice value for index stats.
-The minimum = -20 (THREAD_PRIO_MIN)
-The maximum = 19 (THREAD_PRIO_MAX)
-
-.. _rocksdb_table_stats_max_num_rows_scanned:
-
-.. rubric:: ``rocksdb_table_stats_max_num_rows_scanned``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--rocksdb-table-stats-max-num-rows-scanned``
-   * - Dynamic
-     - Yes
-   * - Scope
-     - Global
-   * - Data type
-     - Numeric
-   * - Default
-     - ``0``
-
-The variable was implemented in :ref:`8.0.20-11`.
-
-The maximum number of rows to scan in a table scan based on
-a cardinality calculation.
-The minimum is ``0`` (every modification triggers a stats recalculation).
-The maximum is ``18,446,744,073,709,551,615``.
-
-.. _rocksdb_table_stats_recalc_threshold_count:
-
-.. rubric:: ``rocksdb_table_stats_recalc_threshold_count``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--rocksdb-table-stats-recalc-threshold-count``
-   * - Dynamic
-     - Yes
-   * - Scope
-     - Global
-   * - Data type
-     - Numeric
-   * - Default
-     - ``100``
-
-The variable was implemented in :ref:`8.0.20-11`.
-
-The number of modified rows to trigger a stats recalculation. This is a
-dependent variable for stats recalculation.
-The minimum is ``0``.
-The maximum is ``18,446,744,073,709,551,615``.
-
-.. _rocksdb_table_stats_recalc_threshold_pct:
-
-.. rubric:: ``rocksdb_table_stats_recalc_threshold_pct``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--rocksdb-table-stats-recalc-threshold-pct``
-   * - Dynamic
-     - Yes
-   * - Scope
-     - Global
-   * - Data type
-     - Numeric
-   * - Default
-     - ``10``
-
-The variable was implemented in :ref:`8.0.20-11`.
-
-The percentage of the number of modified rows over the total number of rows
-to trigger stats recalculations. This is a dependent variable for stats
-recalculation.
-The minimum value is ``0``
-The maximum value is ``100`` (RDB_TBL_STATS_RECALC_THRESHOLD_PCT_MAX).
-
-.. _rocksdb_table_stats_sampling_pct:
-
-.. rubric:: ``rocksdb_table_stats_sampling_pct``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--rocksdb-table-stats-sampling-pct``
-   * - Dynamic
-     - Yes
-   * - Scope
-     - Global
-   * - Data type
-     - Numeric
-   * - Default
-     - ``10``
-
-Specifies the percentage of entries to sample
-when collecting statistics about table properties.
-Default value is ``10``.
-Allowed range is from ``0`` to ``100``.
-
-.. _rocksdb_table_stats_use_table_scan:
-
-.. rubric:: ``rocksdb_table_stats_use_table_scan``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--rocksdb-table-stats-use-table-scan``
-   * - Dynamic
-     - Yes
-   * - Scope
-     - Global
-   * - Data type
-     - Boolean
-   * - Default
-     - ``FALSE``
-
-The variable was implemented in :ref:`8.0.20-11`. Enables table-scan-based index calculations.
-The default value is ``FALSE``.
-
-.. _rocksdb_tmpdir:
-
-.. rubric:: ``rocksdb_tmpdir``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--rocksdb-tmpdir``
-   * - Dynamic
-     - Yes
-   * - Scope
-     - Global, Session
-   * - Data type
-     - String
-   * - Default
-     - 
-
-Specifies the path to the directory for temporary files during DDL operations.
-
-.. _rocksdb_trace_block_cache_access:
-
-.. rubric:: ``rocksdb_trace_block_cache_access``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--rocksdb-trace-block-cache-access``
-   * - Dynamic
-     - Yes
-   * - Scope
-     - Global
-   * - Data type
-     - String
-   * - Default
-     - ``' '``
-
-The variable was implemented in :ref:`8.0.20-11`. Defines the block cache trace option string. The format is sampling frequency: max_trace_file_size:trace_file_name. The sampling frequency value and max_trace_file_size value are positive integers. The block accesses are saved to the ``rocksdb_datadir/block_cache_traces/trace_file_name``. The default value is an empty string.
-
-.. _rocksdb_trace_queries:
-
-.. rubric:: ``rocksdb_trace_queries``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--rocksdb-trace-queries``
-   * - Dynamic
-     - Yes
-   * - Scope
-     - Global
-   * - Data type
-     - String
-   * - Default
-     - ""
-
-This variable is a trace option string. The format is sampling_frequency:max_trace_file_size:trace_file_name. The sampling_frequency and max_trace_file_size are positive integers. The queries are saved to the rocksdb_datadir/queries_traces/trace_file_name.
-
-.. _rocksdb_trace_sst_api:
-
-.. rubric:: ``rocksdb_trace_sst_api``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--rocksdb-trace-sst-api``
-   * - Dynamic
-     - Yes
-   * - Scope
-     - Global
-   * - Data type
-     - Boolean
-   * - Default
-     - ``OFF``
-
-Specifies whether to generate trace output in the log
-for each call to ``SstFileWriter``.
-Disabled by default.
-
-.. _rocksdb_track_and_verify_wals_in_manifest:
-
-.. rubric:: ``rocksdb_track_and_verify_wals_in_manifest``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--rocksdb-track-and-verify-wals-in-manifest``
-   * - Dynamic
-     - No
-   * - Scope
-     - Global
-   * - Data type
-     - Boolean
-   * - Default
-     - ``ON``
-
-DBOptions::track_and_verify_wals_in_manifest for RocksDB.
-
-.. _rocksdb_two_write_queues:
-
-.. rubric:: ``rocksdb_two_write_queues``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--rocksdb-two_write_queues``
-   * - Dynamic
-     - No
-   * - Scope
-     - Global
-   * - Data type
-     - Boolean
-   * - Default
-     - ``ON``
-
-When enabled this variable allows/encourages threads that are using
-two-phase commit to ``prepare`` in parallel.
-
-.. _rocksdb_unsafe_for_binlog:
-
-.. rubric:: ``rocksdb_unsafe_for_binlog``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--rocksdb-unsafe-for-binlog``
-   * - Dynamic
-     - Yes
-   * - Scope
-     - Global, Session
-   * - Data type
-     - Boolean
-   * - Default
-     - ``OFF``
-
-Specifies whether to allow statement-based binary logging
-which may break consistency.
-Disabled by default.
-
-.. _rocksdb_update_cf_options:
-
-.. rubric:: ``rocksdb_update_cf_options``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--rocksdb-update-cf-options``
-   * - Dynamic
-     - No
-   * - Scope
-     - Global
-   * - Data type
-     - String
-   * - Default
-     - 
-
-Specifies option updates for each column family.
-Empty by default.
-
-.. _rocksdb_use_adaptive_mutex:
-
-.. rubric:: ``rocksdb_use_adaptive_mutex``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--rocksdb-use-adaptive-mutex``
-   * - Dynamic
-     - No
-   * - Scope
-     - Global
-   * - Data type
-     - Boolean
-   * - Default
-     - ``OFF``
-
-Specifies whether to use adaptive mutex which spins in user space before
-resorting to the kernel. Disabled by default.
-
-.. _rocksdb_use_default_sk_cf:
-
-.. rubric:: ``rocksdb_use_default_sk_cf``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--rocksdb-use-default-sk-cf``
-   * - Dynamic
-     - No
-   * - Scope
-     - Global
-   * - Data type
-     - Boolean
-   * - Default
-     - OFF
-  
-Use ``default_sk`` column family for secondary keys.
-
-.. _rocksdb_use_direct_io_for_flush_and_compaction:
-
-.. rubric:: ``rocksdb_use_direct_io_for_flush_and_compaction``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--rocksdb-use-direct-io-for-flush-and-compaction``
-   * - Dynamic
-     - No
-   * - Scope
-     - Global
-   * - Data type
-     - Boolean
-   * - Default
-     - ``OFF``
-
-Specifies whether to write to data files directly,
-without caches or buffers.
-Disabled by default.
-
-.. _rocksdb_use_direct_reads:
-
-.. rubric:: ``rocksdb_use_direct_reads``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--rocksdb-use-direct-reads``
-   * - Dynamic
-     - No
-   * - Scope
-     - Global
-   * - Data type
-     - Boolean
-   * - Default
-     - ``OFF``
-
-Specifies whether to read data files directly,
-without caches or buffers.
-Disabled by default.
-If you enable this,
-make sure that :ref:`rocksdb_allow_mmap_reads` is disabled.
-
-.. _rocksdb_use_fsync:
-
-.. rubric:: ``rocksdb_use_fsync``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--rocksdb-use-fsync``
-   * - Dynamic
-     - No
-   * - Scope
-     - Global
-   * - Data type
-     - Boolean
-   * - Default
-     - ``OFF``
-
-Specifies whether MyRocks should use ``fsync`` instead of ``fdatasync``
-when requesting a sync of a data file.
-Disabled by default.
-
-.. _rocksdb_validate_tables:
-
-.. rubric:: ``rocksdb_validate_tables``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--rocksdb-validate-tables``
-   * - Dynamic
-     - No
-   * - Scope
-     - Global
-   * - Data type
-     - Numeric
-   * - Default
-     - ``1``
-
-The variable was implemented in :ref:`8.0.20-11`. Specifies whether to verify that MySQL data dictionary is equal to the MyRocks data dictionary.
-
-* ``0``: do not verify.
-* ``1``: verify and fail on error (default).
-* ``2``: verify and continue with error.
-
-.. _rocksdb_verify_row_debug_checksums:
-
-.. rubric:: ``rocksdb_verify_row_debug_checksums``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--rocksdb-verify-row-debug-checksums``
-   * - Dynamic
-     - Yes
-   * - Scope
-     - Global, Session
-   * - Data type
-     - Boolean
-   * - Default
-     - ``OFF``
-
-Specifies whether to verify checksums when reading index or table records.
-Disabled by default.
-
-.. _rocksdb_wal_bytes_per_sync:
-
-.. rubric:: ``rocksdb_wal_bytes_per_sync``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--rocksdb-wal-bytes-per-sync``
-   * - Dynamic
-     - Yes
-   * - Scope
-     - Global
-   * - Data type
-     - Numeric
-   * - Default
-     - ``0``
-
-Specifies how often should the OS sync WAL (write-ahead log) files to disk
-as they are being written, asynchronously, in the background.
-This operation can be used to smooth out write I/O over time.
-Default value is ``0``, meaning that files are never synced.
-Allowed range is up to ``18446744073709551615``.
-
-.. _rocksdb_wal_dir:
-
-.. rubric:: ``rocksdb_wal_dir``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--rocksdb-wal-dir``
-   * - Dynamic
-     - No
-   * - Scope
-     - Global
-   * - Data type
-     - String
-   * - Default
-     - 
-
-Specifies the path to the directory where MyRocks stores WAL files.
-
-.. _rocksdb_wal_recovery_mode:
-
-.. rubric:: ``rocksdb_wal_recovery_mode``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--rocksdb-wal-recovery-mode``
-   * - Dynamic
-     - Yes
-   * - Scope
-     - Global
-   * - Data type
-     - Numeric
-   * - Default
-     - ``2``
-
-.. note::
-
-    In version :ref:`8.0.20-11` and later, the default is changed from ``1`` to ``2``.
-
-Specifies the level of tolerance when recovering write-ahead logs (WAL) files
-after a system crash.
-
-The following are the options:
-
- * ``0``: if the last WAL entry is corrupted, truncate the entry and either start the server normally or refuse to start.
-
- * ``1``: if a WAL entry is corrupted, the server fails to   start and does not recover from the crash.
-
- * ``2`` (default): if a corrupted WAL entry is detected, truncate all entries after the detected corrupted entry. You can select this setting for replication replicas.
-
- * ``3``: If a corrupted WAL entry is detected, skip only the corrupted entry and continue the apply WAL entries. This option can be dangerous.
-
-.. _rocksdb_wal_size_limit_mb:
-
-.. rubric:: ``rocksdb_wal_size_limit_mb``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--rocksdb-wal-size-limit-mb``
-   * - Dynamic
-     - No
-   * - Scope
-     - Global
-   * - Data type
-     - Numeric
-   * - Default
-     - ``0``
-
-Specifies the maximum size of all WAL files in megabytes
-before attempting to flush memtables and delete the oldest files.
-Default value is ``0`` (never rotated).
-Allowed range is up to ``9223372036854775807``.
-
-.. _rocksdb_wal_ttl_seconds:
-
-.. rubric:: ``rocksdb_wal_ttl_seconds``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--rocksdb-wal-ttl-seconds``
-   * - Dynamic
-     - No
-   * - Scope
-     - Global
-   * - Data type
-     - Numeric
-   * - Default
-     - ``0``
-
-Specifies the timeout in seconds before deleting archived WAL files.
-Default is ``0`` (archived WAL files are never deleted).
-Allowed range is up to ``9223372036854775807``.
-
-.. _rocksdb_whole_key_filtering:
-
-.. rubric:: ``rocksdb_whole_key_filtering``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--rocksdb-whole-key-filtering``
-   * - Dynamic
-     - No
-   * - Scope
-     - Global
-   * - Data type
-     - Boolean
-   * - Default
-     - ``ON``
-
-Specifies whether the bloomfilter should use the whole key for filtering
-instead of just the prefix.
-Enabled by default.
-Make sure that lookups use the whole key for matching.
-
-.. _rocksdb_write_batch_flush_threshold:
-
-.. rubric:: ``rocksdb_write_batch_flush_threshold``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--rocksdb-write-batch-flush-threshold``
-   * - Dynamic
-     - Yes
-   * - Scope
-     - Local
-   * - Data type
-     - Integer
-   * - Default
-     - 0
-
-This variable specifies the maximum size of the write batch in bytes before flushing. Only valid if ``rockdb_write_policy`` is WRITE_UNPREPARED. There is no limit if the variable is set to the default setting. 
-
-.. _rocksdb_write_batch_max_bytes:
-
-.. rubric:: ``rocksdb_write_batch_max_bytes``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--rocksdb-write-batch-max-bytes``
-   * - Dynamic
-     - Yes
-   * - Scope
-     - Global
-   * - Data type
-     - Numeric
-   * - Default
-     - ``0``
-
-Specifies the maximum size of a RocksDB write batch in bytes. ``0`` means no
-limit. In case user exceeds the limit following error will be shown:
-``ERROR HY000: Status error 10 received from RocksDB: Operation aborted: Memory
-limit reached``.
-
-.. _rocksdb_write_disable_wal:
-
-.. rubric:: ``rocksdb_write_disable_wal``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--rocksdb-write-disable-wal``
-   * - Dynamic
-     - Yes
-   * - Scope
-     - Global, Session
-   * - Data type
-     - Boolean
-   * - Default
-     - ``OFF``
-
-Lets you temporarily disable writes to WAL files,
-which can be useful for bulk loading.
-
-.. _rocksdb_write_ignore_missing_column_families:
-
-.. rubric:: ``rocksdb_write_ignore_missing_column_families``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--rocksdb-write-ignore-missing-column-families``
-   * - Dynamic
-     - Yes
-   * - Scope
-     - Global, Session
-   * - Data type
-     - Boolean
-   * - Default
-     - ``OFF``
-
-Specifies whether to ignore writes to column families that do not exist.
-Disabled by default (writes to non-existent column families are not ignored).
-
-.. _rocksdb_write_policy:
-
-.. rubric:: ``rocksdb_write_policy``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--rocksdb-write-policy``
-   * - Dynamic
-     - No
-   * - Scope
-     - Global
-   * - Data type
-     - String
-   * - Default
-     - ``write_committed``
-
-Specifies when two-phase commit data are written into the database.
-Allowed values are ``write_committed``, ``write_prepared``, and
-``write_unprepared``.
-
-.. tabularcolumns:: |p{5cm}|p{5cm}|
-
-.. list-table::
-   :header-rows: 1
-
-   * - Value
-     - Description
-   * - ``write_committed``
-     - Data written at commit time
-   * - ``write_prepared``
-     - Data written after the prepare phase of a two-phase transaction
-   * - ``write_unprepared``
-     - Data written before the prepare phase of a two-phase transaction
-
-
-
-.. include:: ../.res/replace.opt.txt
-.. include:: ../.res/replace.concept.txt
diff --git a/doc/source/myrocks/zenfs.rst b/doc/source/myrocks/zenfs.rst
deleted file mode 100644
index 4ef8a214880b..000000000000
--- a/doc/source/myrocks/zenfs.rst
+++ /dev/null
@@ -1,380 +0,0 @@
-.. _zenfs:
-
-============================================================================
-Installing and configuring Percona Server for MySQL with ZenFS support
-============================================================================
-
-Implemented in Percona Server for MySQL 8.0.26-16.
-
-A solid state drive (SSD) does not overwrite data like a magnetic hard disk drive. Data must be written to an empty page. An SSD issue is ``write amplification``. This issue is when the same data is written multiple times. 
-
-An SSD is organized in pages and blocks. Data is written in pages and erased in blocks. If, for example, you have 8KB data on a page. The application updates one sector (512 Bytes) of that page. The controller reads the page in RAM, marks the old page as ``stale``, updates the sector, and then writes a new page with this 8KB of data. The process is efficient use of the storage space but also shortens the SSD lifespan because the SSD parts do wear out. 
-
-Garbage collection can also cause large-scale write amplification. The ``stale`` data is erased in blocks, which can consist of hundreds of pages. The SSD controller searches for pages that are marked stale. Pages that are not stale but are stored in that block are moved to another block before the block is erased and marked ready for use. 
-
-The zone storage model organizes the SSD into a set of zones that are uniform in size and uses the Zoned Namespaces (ZNS) technology. ZNS is optimized for an SSD and exposes this zoned block storage interface between the host and SSD. ZNS enables smart data placement. Writes are sequential within a zone.
-
-ZenFS is a file system plugin for RocksDB which uses the RocksDB file system to place files into zones on a raw zoned block device (ZBD). The plugin adds native support for ZNS, avoids on device garbage collection, and minimizes write amplification. File data is stored in a set of extents. Within a zone, extents are a contiguous part of the address space. Garbage collection is an option, but this selection can cause write amplification.
-
-ZenFS depends on the ``libzbd`` user library and requires a Linux kernel implementation that supports NVMe Zoned Namespaces. The kernel
-must be configured with `zone block device support
-enabled <https://zonedstorage.io/docs/linux/config>`__.
-
-Read the `Western Digital and Percona deliver
-Utrastar DC ZN540 Zoned Namespace SSD support for Percona Server for
-MySQL <https://documents.westerndigital.com/content/dam/doc-library/en_us/assets/public/western-digital/collateral/company/western-digital-zns-ssd-perconal-blogpost.pdf>`__ PDF for more information.
-
-
-The following procedure installs Percona Server for MySQL and then configures 
-``--rocksdb-fs-uri=zenfs://dev:<short_block_device_name>`` for data storage.
-
-.. note::
-
-   The <block_device_name> can have a short name designation which is the <short_block_device_name>. For example, if the <block_device_name> is ``/dev/nvme0n2`` remove the ``/dev/`` portion and the <short_block_device_name> is ``nvme0n2``.
-   The block device name and short block device name must be substituted with the appropriate name from your system. To indicate that such a substitution is needed in statements, we use <block_device_name> and <short_block_device_name>.
-
-For the moment, the ZenFS plugin can be enabled in following distributions:
-
-.. list-table::
-   :widths: auto
-   :header-rows: 1
-
-   * - Distribution Name
-     - Notes
-   * - Debian 11.1
-     - Able to run the ZenFS plugin
-   * - Ubuntu 20.04.3
-     - Requires the 5.11 HWE kernel patched with the ``allow blk-zoned ioctls without CAPT_SYS_ADMIN`` patch
-
-If the ZenFS functionality is not enabled on Ubuntu 20.04, the binaries with ZenFS support can run on the standard 5.4 kernel.
-
-`Other Linux distributions <https://zonedstorage.io/docs/distributions/linux/>`__ are adding support for ZenFS, but Percona does not provide installation packages for those distributions.
-
-.. _zenfs-installation:
-
-Installation
-============================================================
-
-Start with the installation of *Percona Server for MySQL*. 
-
-1. The steps are listed here for convenience, for an explanation, see :ref:`apt-install`.
-
-
-   .. code-block:: bash
-
-      $ wget https://repo.percona.com/apt/percona-release_latest.$(lsb_release -sc)_all.deb	
-      $ sudo apt install gnupg2 lsb-release ./percona-release_latest.*_all.deb
-      $ sudo percona-release setup ps80
-
-2. Install Percona Server for MySQL with MyRocks and the ZenFS plugin package. The binaries are listed in the :ref:`installing_from_binary_tarball` section of the *Percona Server for MySQL* installation instructions.
-   
-   .. code-block:: bash
-	
-      $ sudo apt install percona-server-server
-	
-#. Install the RocksDB plugin package. This package copies ``ha_rocksdb.so`` into a predefined location. **The RocksDB storage engine is not enabled**.
-
-   .. code-block:: bash
-	
-	  $ sudo apt install percona-server-rocksdb
-
-
-.. _zenfs-configure:
-
-Configuration
-============================================================
-
-#. Identify your ZBD device, <block_device_name>, with `lsblk <https://manpages.debian.org/stretch/util-linux/lsblk.8.en.html>`__. Add the ``-o`` option and specify which columns to print. 
-
-   In the example, the ``NAME`` column returns the block device name, the ``SIZE`` column returns the size of the device, and the ``ZONED`` column returns information if the device uses the zone model. The value, ``host-managed``, identifies a ZBD model.
-
-   .. sourcecode:: bash
-
-      lsblk -o NAME,SIZE,ZONED
-      NAME                    SIZE  ZONED
-      sda                       247.9G  none
-      |-sda1                    230.9G  none
-      |-sda2                        1G  none
-      |-sda3                       16G  none
-      <short_block_device_name>   7.2T  host-managed
-
-		
-#. Change the ownership of <block_device_name> to the ``mysql:mysql`` user account.
-
-   .. code-block:: bash
-	
-	  $ sudo chown mysql:mysql <block_device_name>
-		
-#. Change the permissions so that the user or owner can read and write and the MySQL group can read, in case they must take a backup, for <block_device_name>.
-
-   .. code-block:: bash
-	
-	  $ sudo chmod 640 <block_device_name>
-
-#. Change the scheduler  to ``mq_deadline`` with a ``udev`` rule. Create ``/etc/udev/rules.d/60-scheduler.rules`` if the file does not exist, and add the following rule:
-
-   .. code-block:: text
-
-      ACTION=="add|change", KERNEL=="<short_block_device_name>", ATTR{queue/scheduler}="mq-deadline"
-
-#. Restart the machine to apply the rule.
-
-#. Verify if the rule was applied correctly by running the following line:
-
-   .. code-block:: bash
-
-    $ cat /sys/block/<short_block_device_name>/queue/scheduler
-
-#. Review that the output of the previous command matches:
-
-   .. code-block:: text
-
-    [mq-deadline] none
-
-#. Create an auxiliary directory for ZenFS. For example ``/var/lib/mysql_aux_nvme0n2``.
-
-   The ZenFS auxiliary directory is a regular (POSIX) file directory used internally to resolve file locks and shared access. There are no strict requirements for the location but the directory must be write accessible for the `mysql:mysql` UNIX system user account. Each ZBD must have an individual auxiliary directory. This directory is recommended to be at the same level as "/var/lib/mysql", which is the default Percona Server for MySQL directory.
-
-   .. note::
-
-      AppArmor is enabled by default in Debian 11. If your AppArmor mode is set to ``enforce``, you must edit the profile to allow access to these locations. Add the following rules to ``usr.sbin.mysqld``:
-
-      .. code-block:: bash
-
-         /var/lib/mysql_aux_*/ r,
-         /var/lib/mysql_aux_*/** rwk,
-
-      Don't forget to reload the policy if you make edits:
-
-      .. code-block:: bash
-
-         $ sudo service apparmor reload
-
-      For more information, see :ref:`enable-apparmor`.
-
-   .. note::
-	
-		 If you must configure ZenFS to use a directory inside ``/var/lib`` (owned by ``root:root`` without write permissions for other user accounts), edit your AppArmor profile (described in an earlier step), if needed, and do the following steps manually:
-		
-		 #. Create the ``aux_path`` for <block_device_name>:
-		
-		    .. code-block:: bash
-		
-			    $ sudo mkdir /var/lib/mysql_aux_<short_block_device_name>
-			
-		 #. Change the ownership of the ``aux_path``:
-		
-		    .. code-block:: bash
-		
-			    $ sudo chown mysql:mysql /var/lib/mysql_aux_<short_block_device_name>
-			
-		 #. Set the permissions for the ``aux_path`` for <block_device_name>:
-		
-		    .. code-block:: bash
-		
-			    $ sudo chmod 750 /var/lib/mysql_aux_<short_block_device_name>
-
-
-#. Change the ownership of <block_device_name>.
-
-   .. code-block:: bash
-
-          $ sudo chown mysql:mysql <block_device_name>
-
-#. Initialize ZenFS on <block_device_name>.
-
-   .. code-block:: bash
-
-	  $ sudo -H -u mysql zenfs mkfs --zbd=<short_block_device_name> --aux_path=/var/lib/mysql_aux_<short_block_device_name> --finish_threshold=0 --force
-		
-#. Stop *Percona Server for MySQL*:
-
-   .. code-block:: bash
-	
-	  sudo service mysql stop 
-		
-#. Edit my.cnf. Add the following line to the "[mysqld]" section:
-
-   .. code-block:: text 
-		
-	  [mysqld]
-	  ...
-	  loose-rocksdb-fs-uri=zenfs://dev:<short_block_device_name>
-	  ...
-        
-   .. note::
-	
-		The "loose-" prefix is important.
-		
-#. Start *Percona Server for MySQL*:
-
-   .. code-block:: bash
-	
-	  $ sudo service mysql start 
-		
-#. Enable ``RocksDB``:
-
-   .. code-block:: bash
-	
-	  $ sudo ps-admin --enable-rocksdb -u root -p
-
-#. Enter the MyRocks password.
-
-   Alternatively, enable RocksDB by adding the following lines to the my.cnf file:
-
-   .. code-block:: text
-
-	  [mysqld]
-    ...
-    plugin-load-add=rocksdb=ha_rocksdb.so
-    default-storage-engine=rocksdb
-    ...
-		
-#. Verify that the ".rocksdb" directory in the default data directory has only "LOG*" files:
-
-   .. code-block:: bash
-	
-	  $ sudo ls -la /var/lib/mysql/.rocksdb 
-		
-#. Verify that ZenFS is created on "rocksdb" and has the *RocksDB* data files:
-
-   .. code-block:: bash
-	
-	  $ sudo -H -u mysql zenfs list --zbd=<short_block_device_name> --path=./.rocksdb
-    #OR
-	  $ sudo -H -u mysql zenfs dump --zbd=<short_block_device_name>
-
-#. You can verify if the ZenFS was successfully created with the following command:
-
-   .. sourcecode:: bash
-
-      $ sudo -H -u mysql zenfs ls-uuid
-      ...
-      13e421af-1967-435c-ab15-faf4529710b6    <short_block_device_name>
-      ...
-
-#. You can check the available storage with the following command:
-
-   .. sourcecode:: bash
-
-      $ sudo -H -u mysql zenfs df --zbd=<short_block_device_name>
-      Free: 971453 MB
-      Used: 0 MB
-      Reclaimable: 0 MB
-      Space amplification: 0%
-      
-Backup and restore
-====================================================================
-
-Shut down the server and use the following command to backup a ZenFS file system, including metadata files, to a local filesystem. The ``zenfs`` backup and restore utility must have exclusive access to the ZenFS filesystem to take a consistent snapshot. The backup command only takes logical backups.
-
-The following command backs up everything from the root of the ZenFS drive:
-
-.. sourcecode:: bash
-
-    $ zenfs backup --zbd=${NULLB} --path="/home/user/bkp" --backup_path=/
-
-The options are the following:
-
-* The ``--path`` can be either an absolute path or a relative path. The backup command creates the directory in the ``--path`` if it does not exist. 
-
-* The ``--backup_path`` option can use any of the following path values based on the location. 
-
-  If the backup is for the ZenFS root drive, use any of the values in the following table:
-
-  .. list-table:: Back up from the ZenFS root drive
-     :header-rows: 1
-
-     * - Value 
-       - Description
-     * - <empty_string>
-       - Empty string 
-     * - /
-       - A forward slash
-     * - .
-       - A single period
-     * - ./
-       - A single period with a forward slash
-
-  If the backup is for a non-root ZenFS path, use any of the values in the following table:
-
-  .. list-table:: Back up from a non-root ZenFS path
-     :header-rows: 1
-
-     * - Value
-       - Description
-     * -  <directory>
-       - Only the directory name
-     * - /<directory>
-       - A forward slash with the directory name
-     * - ./<directory>
-       - A single period with a forward slash and the directory name
-     * -  <directory>/
-       -  The directory name with a forward slash
-     * - /<directory>/
-       - A forward slash with the directory name and an ending forward slash
-     * - ./<directory>/
-       - A single period, a forward slash, the directory name, and an ending forward slash
-
-
-Use the following command to restore a backup into the root of the ZenFS drive:
-
-.. sourcecode:: bash
-
-    $ zenfs restore --zbd=${NULLB} --path="/home/user/bkp/" --restore_path=/
-
-* The ``--path`` can be either an absolute path or a relative path. The backup command creates the directory in the ``--path`` if it does not exist. 
-
-* The ``--restore_path`` option can use any of the following path values based on the location.
-
-  If the restore is for the ZenFS root drive, use any of the values in the following tables:
-
-  .. list-table:: Restore to the ZenFS root drive
-     :header-rows: 1
-
-     * - Value 
-       - Description
-     * - <empty_string>
-       - Empty string 
-     * - /
-       - A forward slash
-     * - .
-       - A single period
-     * - ./
-       - A single period with a forward slash
-
-  If the restore is for a non-root ZenFS path, use any of the values in the following table:
-
-  .. list-table:: Restore to a non-root ZenFS path
-     :header-rows: 1
-
-     * - Value
-       - Description
-     * -  <directory>
-       - Only the directory name
-     * - /<directory>
-       - A forward slash with the directory name
-     * - ./<directory>
-       - A single period with a forward slash and the directory name
-     * -  <directory>/
-       -  The directory name with a forward slash
-     * - /<directory>/
-       - A forward slash with the directory name and an ending forward slash
-     * - ./<directory>/
-       - A single period, a forward slash, the directory name, and an ending forward slash
-
-
-Known Limitations
-====================================================================
-
-After a reboot the NVME ZBD configuration ("/dev/nvme02" in our examples) can disappear. The issue is OS-dependent and can be managed by the system administrators. One or more of the following events may have occurred:
-
-- A reboot changes the active "scheduler" from "[mq-deadline]". The following steps `reset the disk scheduler in RedHat using udev rules <https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/managing_storage_devices/setting-the-disk-scheduler_managing-storage-devices#setting-the-disk-scheduler-using-udev-rules_setting-the-disk-scheduler>`__. For Ubuntu, see `Input/output schedulers <https://wiki.archlinux.org/title/Improving_performance#Input/output_schedulers>`__.
-
-.. seealso:: For more information, review `Change I/O scheduler <https://www.golinuxcloud.com/how-to-change-io-scheduler-permanently-linux/>`__.
-
-- A reboot resets the device permissions from "640/mysql:mysql" to "660/root:disk". 
-
-
-
-
diff --git a/doc/source/percona-logo-color.png b/doc/source/percona-logo-color.png
deleted file mode 100644
index 042dc27d8057..000000000000
Binary files a/doc/source/percona-logo-color.png and /dev/null differ
diff --git a/doc/source/percona-logo.jpg b/doc/source/percona-logo.jpg
deleted file mode 100644
index 2828c6c41ea2..000000000000
Binary files a/doc/source/percona-logo.jpg and /dev/null differ
diff --git a/doc/source/percona-xtrabackup-logo.jpg b/doc/source/percona-xtrabackup-logo.jpg
deleted file mode 100644
index 6c9f9d668bba..000000000000
Binary files a/doc/source/percona-xtrabackup-logo.jpg and /dev/null differ
diff --git a/doc/source/percona-xtradb.png b/doc/source/percona-xtradb.png
deleted file mode 100644
index 1438c8b6fec1..000000000000
Binary files a/doc/source/percona-xtradb.png and /dev/null differ
diff --git a/doc/source/percona_favicon.ico b/doc/source/percona_favicon.ico
deleted file mode 100644
index f426064d6f50..000000000000
Binary files a/doc/source/percona_favicon.ico and /dev/null differ
diff --git a/doc/source/percona_xtradb.rst b/doc/source/percona_xtradb.rst
deleted file mode 100644
index 40e679c3db92..000000000000
--- a/doc/source/percona_xtradb.rst
+++ /dev/null
@@ -1,27 +0,0 @@
-=====================================
- The Percona XtraDB Storage Engine
-=====================================
-
-.. image:: percona-xtradb.png
-   :alt: Percona XtraDB
-   :align: right
-
-|xtradb.product| is an enhanced version of the |InnoDB| storage engine, designed
-to better scale on modern hardware.  It also includes a variety of other
-features useful in high-performance environments. It is fully backwards
-compatible, and so can be used as a drop-in replacement for standard |InnoDB|.
-
-
-|xtradb.product| includes all of |InnoDB| 's robust, reliable ``ACID``-compliant
-design and advanced ``MVCC`` architecture, and builds on that solid foundation
-with more features, more tunability, more metrics, and more scalability. In
-particular, it is designed to scale better on many cores, to use memory more
-efficiently, and to be more convenient and useful. The new features are
-especially designed to alleviate some of |InnoDB|'s limitations. We choose
-features and fixes based on customer requests and on our best judgment of
-real-world needs as a high-performance consulting company.
-
-|xtradb.product| engine will not have further binary releases, it is
-distributed as part of |Percona Server|.
-
-.. include:: .res/replace.txt
diff --git a/doc/source/performance/adaptive_network_buffers.rst b/doc/source/performance/adaptive_network_buffers.rst
deleted file mode 100644
index f488f7c859e2..000000000000
--- a/doc/source/performance/adaptive_network_buffers.rst
+++ /dev/null
@@ -1,35 +0,0 @@
-.. _adaptive_network_buffers:
-
-===========================
-Adaptive Network Buffers 
-===========================
-
-To find the buffer size of the current connection, use the ``network_buffer_length`` status variable. Add ``SHOW GLOBAL`` to review the cumulative buffer sizes for all connections. This variable can help to estimate the maximum size of the network buffer's overhead.
-
-Network buffers grow towards the `max_allowed_packet <https://dev.mysql.com/doc/refman/8.0/en/server-system-variables.html#sysvar_max_allowed_packet>`_ size and do not shrink until the connection is terminated. For example, if the connections are selected at random from the pool, an occasional big query eventually increases the buffers of all connections. The combination of `max_allowed packet` set to a value between 64MB to 128MB and the connection number between 256 to 1024 can create a large memory overhead.
-
-*Percona Server for MySQL* version 8.0.23-14 introduces the :ref:`net_buffer_shrink_interval` variable to solve this issue. The default value is 0 (zero). If you set the value higher than 0, Percona Server records the network buffer's maximum use size for the number of seconds set by `net_buffer_shrink_interval`. When the next interval starts, the network buffer is set to the recorded size. This action removes spikes in the buffer size.
-
-You can achieve similar results by disconnecting and reconnecting the TCP connections, but this solution is a heavier process. This process disconnects and reconnects connections with small buffers. 
-
-.. _net_buffer_shrink_interval:
-
-.. rubric:: ``net_buffer_shrink_interval``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - --net-buffer-shrink-interval=#
-   * - Scope
-     - Global
-   * - Dynamic
-     - Yes
-   * - Data type
-     - integer 
-   * - Default
-     - 0
-
-The interval is measured in seconds. The default value is 0, which disables the functionality. The minimum value is 0, and the maximum value is 31536000. 
diff --git a/doc/source/performance/aio_page_requests.rst b/doc/source/performance/aio_page_requests.rst
deleted file mode 100644
index 6508083920a9..000000000000
--- a/doc/source/performance/aio_page_requests.rst
+++ /dev/null
@@ -1,54 +0,0 @@
-.. _aio_page_requests:
-
-=======================================
-Multiple page asynchronous I/O requests
-=======================================
-
-I/O unit size in *InnoDB* is only one page, even if doing read ahead. 16KB
-I/O unit size is too small for sequential reads, and much less efficient than
-larger I/O unit size.
-
-*InnoDB* uses Linux asynchronous I/O (``aio``) by default. By submitting multiple
-consecutive 16KB read requests at once, Linux internally can merge requests and
-reads can be done more efficiently.
-
-`On a HDD RAID 1+0 environment
-<http://yoshinorimatsunobu.blogspot.hr/2013/10/making-full-table-scan-10x-faster-in.html>`_,
-more than 1000MB/s disk reads can be achieved by submitting 64 consecutive pages
-requests at once, while only
-160MB/s disk reads is shown by submitting single page request.
-
-With this feature *InnoDB* submits multiple page I/O requests.
-
-Version Specific Information
-============================
-
-* `8.0.12-1` - The feature was ported from *Percona Server for MySQL* 5.7.
-
-Status Variables
-================
-
-.. _Innodb_buffered_aio_submitted:
-
-.. rubric:: ``Innodb_buffered_aio_submitted``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Data type
-     - Numeric
-   * - Scope
-     - Global
-
-This variable shows the number of submitted buffered asynchronous I/O requests.
-
-Other Reading
-=============
-
- * `Making full table scan 10x faster in InnoDB
-   <http://yoshinorimatsunobu.blogspot.hr/2013/10/making-full-table-scan-10x-faster-in.html>`_
-
- * `Bug #68659	InnoDB Linux native aio should submit more i/o requests at once
-   <https://bugs.mysql.com/bug.php?id=68659>`_
diff --git a/doc/source/performance/jemalloc-profiling.rst b/doc/source/performance/jemalloc-profiling.rst
deleted file mode 100644
index e0826b033332..000000000000
--- a/doc/source/performance/jemalloc-profiling.rst
+++ /dev/null
@@ -1,234 +0,0 @@
-.. _jemalloc-profiling:
-
-=================================================
-Jemalloc Memory Allocation Profiling
-=================================================
-
-Implemented in :ref:`8.0.25-15`, *Percona Server for MySQL* can take advantage of the memory-profiling ability of the jemalloc allocator. This ability provides a method to investigate memory-related issues.
-
-
-Requirements
-----------------
-
-This memory-profiling requires :ref:`jemalloc_detected`. This read-only variable returns ``true`` if jemalloc with the profiling-enabled option is being used by *Percona Server for MySQL*. 
-
-As root, customize jemalloc with the following flags:
-
-.. list-table::
-    :widths: 20 40
-    :header-rows: 1
-
-    * - Option
-      - Description
-    * - `--enable-stats`
-      - Enables statistics-gathering ability
-    * - `--enable-prof`
-      - Enables heap profiling and the ability to detect leaks. 
-
-Using ``LD_PRELOAD``. Build the library, configure the malloc configuration with the ``prof:true`` string, and then use ``LD_PRELOAD`` to  preload the ``libjemalloc.so`` library. The libprocess ``MemoryProfiler`` class detects the library automatically and enables the profiling support.
-
-The following is an example of the required commands:
-
-.. sourcecode:: bash
-
-    ./configure --enable-stats --enable-prof && make && make install
-    MALLOC_CONF=prof:true 
-    LD_PRELOAD=/usr/lib/libjemalloc.so
-
-.. note:
-
-    Ensure the ``libjemalloc.so`` exists in the LD path.
-
-Use *Percona Server for MySQL* with jemalloc with profiling enabled
-----------------------------------------------------------
-
-To detect if jemalloc is set, run the following command:
-
-.. sourcecode::  mysql
-
-    SELECT @@jemalloc_detected;
-
-To enable jemalloc profiling in a MySQL client, run the following command:
-
-.. sourcecode:: bash
-
-    set global jemalloc_profiling=on;
-
-
-The :ref:`malloc_stats_totals` table returns the statistics, in bytes, of the memory usage. The command takes no parameters and returns the results as a table.
-
-The following example commands display this result:
-
-.. sourcecode:: mysql
-
-    use performance_schema;
-
-    SELECT * FROM malloc_stats_totals;
-    +----+------------+------------+------------+-------------+------------+
-    | id | ALLOCATION | MAPPED     | RESIDENT   | RETAINED    | METADATA   |
-    +----+------------+------------+------------+-------------+------------+
-    |  1 | 390977528  | 405291008  | 520167424  | 436813824   | 9933744    |
-    +----+------------+------------+------------+-------------+------------+
-    1 row in set (0.00 sec)
-
-The :ref:`malloc_stats` table returns the cumulative totals, in bytes, of several statistics per type of arena. The command takes no parameters and returns the results as a table.
-
-The following example commands display this result:
-
-.. sourcecode:: mysql
-
-    use performance_schema;
-
-    mysql> SELECT * FROM malloc_stats ORDER BY TYPE DESC LIMIT 3;
-    +--------+-------------+-------------+-------------+-------------+
-    | TYPE   | ALLOCATED   | NMALLOC     | NDALLOC     | NRESQUESTS  |
-    +--------+-------------+-------------+-------------+-------------+
-    | small  | 23578872    | 586156      | 0           | 2649417     |
-    | large  | 367382528   | 2218        | 0           | 6355        |
-    | huge   | 0           | 0           | 0           | |
-    +--------+-------------+-------------+-------------+-------------+
-    3 rows in set (0.00 sec)
-
-Dumping the profile
----------------------
-
-The profiling samples the ``malloc()`` calls and stores the sampled stack traces in a separate location in memory. These samples can be dumped into the filesystem. A dump returns a detailed view of the state of the memory. 
-
-The process is global; therefore, only a single concurrent run is available and only the most recent runs are stored on disk. 
-
-Use the following command to create a profile dump file:
-
-.. sourcecode:: mysql
-
-    flush memory profile;
-
-The generated memory profile dumps are written to the `/tmp` directory.
-
-You can analyze the dump files with ``jeprof`` program, which must be installed on the host system in the appropriate path. This program is a perl script that post-processes the dump files in their raw format. The program has no connection to the ``jemalloc`` library and the version numbers are not required to match.
-
-To verify the dump, run the following command:
-
-.. sourcecode:: bash
-
-    ls /tmp/jeprof_mysqld*
-    /tmp/jeprof_mysqld.1.0.170013202213
-    jeprof --show_bytes /tmp/jeprof_mysqld.1.0.170013202213 jeprof.*.heap
-
-You can also access the memory profile to plot a graph of the memory use. This ability requires that ``jeprof`` and ``dot`` are in the `/tmp` path. For the graph to display useful information, the binary file must contain symbol information.
-
-
-Run the following command:
-
-.. sourcecode:: bash
-
-    jeprof --dot /usr/sbin/mysqld /tmp/jeprof_mysqld.1.0.170013202213 > /tmp/jeprof1.dot
-    dot --Tpng /tmp/jeprof1.dot > /tmp/jeprof1.png 
-
-.. note:: 
-
-    An example of `allocation graph <https://github.com/jemalloc/jemalloc/wiki/Use-Case%3A-Leak-Checking>`__. 
-
-
-PERFORMANCE_SCHEMA Tables
----------------------------------
-
-In :ref:`8.0.25.14`, the following tables are implemented to retrieve memory allocation statistics for a running instance or return the cumulative number of allocations requested or allocations returned for a running instance.
-
-More information about the stats that are returned can be found in `jemalloc <http://jemalloc.net/jemalloc.3.html>`__.
-
-.. _malloc_stats_totals:
-
-malloc_stats_totals
----------------------
-
-The current stats for allocations. All measurements are in bytes.
-
-.. list-table::
-    :widths: 20 40
-    :header-rows: 1
-
-    * - Column Name
-      - Description
-    * - ALLOCATED
-      - The total amount the application allocated
-    * - ACTIVE 
-      - The total amount allocated by the application of active pages. A multiple of the page size and this value is greater than or equal to the `stats.allocated` value. The sum does not include allocator metadata pages and `stats.arenas.<i>.pdirty` or `stats.arenas.<i>.pmuzzy`.
-    * - MAPPED
-      - The total amount in chunks that are mapped by the allocator in active extents. This value does not include inactive chunks. The value is at least as large as the `stats.active` and is a multiple of the chunk size.
-    * - RESIDENT
-      - A maximum number the allocator has mapped in physically resident data pages. All allocator metadata pages and unused dirty pages are included in this value. Pages may not be physically resident if they correspond to demand-zeroed virtual memory that has not yet been touched. This value is a maximum rather than a precise value and is a multiple of the page size. The value is greater than the `stats.active`.
-    * - RETAINED
-      - The amount retained by the virtual memory mappings of the operating system. This value does not include any returned mappings. This type of memory, usually de-committed, untouched, or purged. The value is associated with physical memory and is excluded from mapped memory statistics.
-    * - METADATA
-      - The total amount dedicated to metadata. This value contains the base allocations which are used for bootstrap-sensitive allocator metadata structures. Transparent huge pages usage is not included.
-
-.. _malloc_stats:
-
-malloc_stats
------------------
-
-The cumulative number of allocations requested or allocations returned for a running instance.
-
-.. list-table::
-    :widths: 20 40
-    :header-rows: 1
-
-    * - Column Name
-      - Description
-    * - Type
-      - The type of object: small, large, and huge
-    * - ALLOCATED
-      - The number of bytes that are currently allocated to the application.
-    * - NMALLOC
-      - A cumulative number of times an allocation was requested from the arena's bins. The number includes times when the allocation satisfied an allocation request or filled a relevant `tcache` if `opt.tcache` is enabled.
-    * - NDALLOC
-      - A cumulative number of times an allocation was returned to the arena's bins. The number includes times when the allocation was deallocated or flushed the relevant `tcache` if `opt.tcache` is enabled.
-    * - NREQUESTS
-      - The cumulative number of allocation requests satisfied.
-
-System Variables
-------------------
-
-The following variables have been added:
-
-.. _jemalloc_detected:
-
-jemalloc_detected
-+++++++++++++++++++
-
-Description: This read-only variable returns ``true`` if jemalloc with profiling enabled is detected. The following options are required:
-
-    * Jemalloc is installed and compiled with profiling enabled
-
-    * *Percona Server for MySQL* is configured to use jemalloc by using the environment variable ``LD_PRELOAD``. 
-
-    * The environment variable ``MALLOC_CONF`` is set to ``prof:true``.
-
-The following options are:
-
-    * Scope: Global
-    * Variable Type: Boolean
-    * Default Value: false
- 
-.. _jemalloc_profiling:
-
-jemalloc_profiling
-+++++++++++++++++++
-
-Description: Enables jemalloc profiling. The variable requires :ref:`jemalloc_detected`.
-
-    * Command Line: --jemalloc_profiling[=(OFF|ON)]
-    * Config File: Yes
-    * Scope: Global
-    * Dynamic: Yes
-    * Variable Type: Boolean
-    * Default Value: OFF
-
-Disable Profiling
---------------------
-
-To disable jemalloc profiling, in a MySQL client, run the following command:
-
-.. sourcecode:: mysql
-
-    set global jemalloc_profiling=off;
\ No newline at end of file
diff --git a/doc/source/performance/prefix_index_queries_optimization.rst b/doc/source/performance/prefix_index_queries_optimization.rst
deleted file mode 100644
index 9634f21302a8..000000000000
--- a/doc/source/performance/prefix_index_queries_optimization.rst
+++ /dev/null
@@ -1,55 +0,0 @@
-.. _prefix_index_queries_optimization:
-
-=================================
-Prefix Index Queries Optimization
-=================================
-
-*Percona Server for MySQL* has ported Prefix Index Queries Optimization feature from
-Facebook patch for *MySQL*.
-
-Prior to this *InnoDB* would always fetch the clustered index for all prefix
-columns in an index, even when the value of a particular record was smaller
-than the prefix length. This implementation optimizes that case to use the
-record from the secondary index and avoid the extra lookup.
-
-Status Variables
-================
-
-.. _Innodb_secondary_index_triggered_cluster_reads:
-
-.. rubric:: ``Innodb_secondary_index_triggered_cluster_reads``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Data type
-     - Numeric
-   * - Scope
-     - Global
-
-This variable shows the number of times secondary index lookup triggered
-cluster lookup.
-
-.. _Innodb_secondary_index_triggered_cluster_reads_avoided:
-
-.. rubric:: ``Innodb_secondary_index_triggered_cluster_reads_avoided``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Data type
-     - Numeric
-   * - Scope
-     - Global
-
-This variable shows the number of times prefix optimization avoided
-triggering cluster lookup.
-
-Version Specific Information
-================================================================================
-
-* :ref:`8.0.12-1`: The feature was ported from *Percona Server for MySQL* 5.7
diff --git a/doc/source/performance/procfs-plugin.rst b/doc/source/performance/procfs-plugin.rst
deleted file mode 100644
index c1498ecdd95f..000000000000
--- a/doc/source/performance/procfs-plugin.rst
+++ /dev/null
@@ -1,144 +0,0 @@
-.. _procfs-plugin:
-
-======================================================================
-The ProcFS plugin
-======================================================================
-
-.. important::
-
-    This feature is **tech preview** quality.
-
-Implemented in :ref:`8.0.25-15`, the ProcFS plugin provides access to the Linux performance counters by running SQL queries against a Percona Server for MySQL 8.0. 
-
-You may be unable to capture operating system metrics in certain environments, such as Cloud installations or MySQL-as-a-Service installations. These metrics are essential for complete system performance monitoring.
-
-The plugin does the following:
-
-* Reads selected files from the ``/proc`` file system and the ``/sys`` file system.
-
-* Populates the file names and their content as rows in the `INFORMATION_SCHEMA.PROCFS` view.
-
-The system variable :ref:`procfs_files_spec` provides access to the ``/proc`` and the ``/sys`` files and directories. This variable cannot be changed at run time, preventing a compromised account from giving itself greater access to those file systems. 
-
-
-Manually Installing the PLUGIN
---------------------------------
-
-We recommend installing the plugin as part of the package. If needed, you can install this plugin manually. Copy the ``procfs.so`` file to the mysql plugin installation directory and execute the following command:
-
-.. sourcecode:: mysql
-
-
-    INSTALL PLUGIN procfs SONAME 'procfs.so';
-
-Access Privileges Required 
------------------------------
-
-Only users with the ``ACCESS_PROCFS`` dynamic privilege can access the ``INFORMATION_SCHEMA.PROCFS`` view. During the plugin startup, this dynamic privilege is registered with the server.
-
-After the plugin installation, grant a user access to the INFORMATION_SCHEMA.PROCFS view by executing the following command:
-
-.. sourcecode:: mysql
-
-
-    GRANT ACCESS_PROCFS ON *.* TO 'user'@'host';
-
-.. important::
-
-  An SELinux policy or an AppArmor profile may prevent access to file locations needed by the ProcFS plugin, such as the ``/proc/sys/fs/file-nr`` directory or any sub-directories or files under ``/proc/irq/``. Either edit the policy or profile to ensure that the plugin has the necessary access. If the policy and profile do not allow access, the plugin may may have unexpected behavior.
-
-  For more information, see :ref:`selinux` and :ref:`enable-apparmor`.
-
-Using the ProcFS plugin
--------------------------------------
-
-Authorized users can obtain information from individual files by specifying the exact file name within a WHERE clause. Files that are not included are ignored and considered not to exist.
-
-All files that match the :ref:`procfs_files_spec` are opened, read, stored in memory, and, finally, returned to the client. It is critical to add a WHERE clause to return only specific files to limit the impact of the plugin on the server's performance. A failure to use a WHERE clause can lead to lengthy query response times, high load, and high memory usage on the server. The WHERE clause can contain either an equality operator, the LIKE operator, or the IN operator. The LIKE operator limits file globbing. You can write file access patterns in the `glob(7) style <https://man7.org/linux/man-pages/man7/glob.7.html>`__, such as ``/sys/block/sd[a-z]/stat;/proc/version*``
-
-The following example returns the ``proc/version``:
-
-.. sourcecode:: mysql
-
-    SELECT * FROM INFORMATION_SCHEMA.PROCFS WHERE FILE = '/proc/version';
-
-Tables
------------
-
-.. _PROCFS:
-
-.. rubric:: PROCFS
-
-The schema definition of the INFORMATION_SCHEMA.PROCFS view is:
-
-.. sourcecode:: mysql
-
-    CREATE TEMPORARY TABLE `PROCFS` (
-    `FILE` varchar(1024) NOT NULL DEFAULT '',
-    `CONTENTS` longtext NOT NULL
-    ) ENGINE=InnoDB DEFAULT CHARSET=utf8;
-
-Status variables provide the basic metrics:
-
-.. list-table::
-    :widths: 10 40
-    :header-rows: 1
-
-    * - Name 
-      - Description
-    * - procfs_access_violations
-      - The number of attempted queries by users without the ACCESS_PROCFS privilege.
-    * - procfs_queries
-      - The number of queries made against the procfs view.
-    * - procfs_files_read
-      - The number of files read to provide content
-    * - procfs_bytes_read
-      - The number of bytes read to provide content
-      
-Variable
----------
-
-.. _procfs_files_spec:
-
-.. rubric:: `procfs_files_spec`
-
-.. list-table::
-    :widths: 20 40
-    :header-rows: 1
-
-    * - Parameter
-      - Description
-    * - Introduced
-      - 8.0.25-14
-    * - Dynamic
-      - Yes
-    * - Scope
-      - Global
-    * - Read, Write, or Read-Only
-      - Read-Only
-  
-The default value for ``procfs_files_spec`` is: /proc/cpuinfo;/proc/irq//;/proc/loadavg/proc/net/dev;/proc/net/sockstat;/proc/net/sockstat_rhe4;/proc/net/tcpstat;/proc/self/net/netstat;/proc/self/stat;/proc/self/io;/proc/self/numa_maps/proc/softirqs;/proc/spl/kstat/zfs/arcstats;/proc/stat;/proc/sys/fs/file-nr;/proc/version;/proc/vmstat
-
-Enables access to the ``/proc`` and ``/sys`` directories and files. This variable is global, read only, and is set by using either the `mysqld` command line or by editing :file:`my.cnf`. 
-
-
-Limitations
-------------
-The following limitations are:
-
-    * Only first 60k of /proc/ /sys/ files are returned
-
-    * The file name size is limited to 1k
-
-    * The plugin cannot read files if path does not start from /proc or /sys
-
-    * Complex WHERE conditions may force the plugin to read all configured files.
-
-Uninstall plugin
------------------
-
-The following statement removes the procfs plugin. 
-
-.. sourcecode:: mysql
-
-    UNINSTALL PLUGIN procfs;
\ No newline at end of file
diff --git a/doc/source/performance/query_limit_records.rst b/doc/source/performance/query_limit_records.rst
deleted file mode 100644
index b5c356aa7c90..000000000000
--- a/doc/source/performance/query_limit_records.rst
+++ /dev/null
@@ -1,111 +0,0 @@
-.. _query-limit-estimates:
-
-=========================================================
-Limiting the Estimation of Records in a Query
-=========================================================
-
-:Availability:  The feature is **technical preview** quality.
-
-This page describes an alternative when running queries against a large number
-of table partitions. When a query runs, InnoDB estimates the records in each
-partition. This process can result in more pages read and more disk I/O, if the
-buffer pool must fetch the pages from disk. This process increases the query
-time if there are a large number of partitions.
-
-The addition of two variables makes it possible to override `records_in_range
-<https://dev.mysql.com/doc/internals/en/records-in-range.html>`__ which
-effectively bypasses the process.
-
-.. warning::
-
-    The use of these variables may result in improper index selection by the
-    optimizer.
-
-.. _innodb_records_in_range:
-
-.. rubric:: ``innodb_records_in_range``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--innodb-records-in-range``
-   * - Scope
-     - Global
-   * - Dynamic
-     - Yes
-   * - Data type
-     - Numeric
-   * - Default
-     - 0
-
-:Availability:  The feature is **technical preview** quality.
-
-The variable provides a method to limit the number of records estimated for a
-query.
-
-.. code-block:: MySQL
-
-    mysql> SET @@GLOBAL.innodb_records_in_range=100;
-    100
-
-.. _innodb_force_index_records_in_range:
-
-.. rubric:: ``innodb_force_index_records_in_range``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--innodb-force-index-records-in-range``
-   * - Scope
-     - Global
-   * - Dynamic
-     - Yes
-   * - Data type
-     - Numeric
-   * - Default
-     - 0
-
-:Availability:  The feature is **technical preview** quality.
-
-This variable provides a method to override the `records_in_range` result when a
-FORCE INDEX is used in a query.
-
-.. code-block:: MySQL
-
-    mysql> SET @@GLOBAL.innodb_force_index_records_in_range=100;
-    100
-
-.. _favor_range_scan:
-
-Using the favor_range_scan optimizer switch
---------------------------------------------
-
-:Availability:  The feature is **technical preview** quality.
-
-In specific scenarios, the optimizer chooses to scan a table instead of using a range scan. The conditions are the following:
-
-* Table with an extremely large number of rows
-
-* Compound primary keys made of two or more columns
-
-* WHERE clause contains multiple range conditions
-
-The `optimizer_switch <https://dev.mysql.com/doc/refman/8.0/en/switchable-optimizations.html>`__ controls the optimizer behavior. The `favor_range_scan` switch arbitrarily lowers the cost of a range scan by a factor of 10.
-
-The available values are:
-
-* ON
-
-* OFF (Default)
-
-* DEFAULT
-
-::
-
-    mysql> SET optimizer_switch='favor_range_scan=on';
diff --git a/doc/source/performance/threadpool.rst b/doc/source/performance/threadpool.rst
deleted file mode 100644
index 0332b5f5783f..000000000000
--- a/doc/source/performance/threadpool.rst
+++ /dev/null
@@ -1,353 +0,0 @@
-.. _threadpool:
-
-=============
- Thread Pool
-=============
-
-*MySQL* executes statements using one thread per client connection. Once the number of connections increases past a certain point performance will degrade.
-
-This feature enables the server to keep the top performance even with a large number of client connections by introducing a dynamic thread pool. By using the thread pool server would decrease the number of threads, which will then reduce the context switching and hot locks contentions. Using the thread pool will have the most effect with ``OLTP`` workloads (relatively short CPU-bound queries).
-
-In order to enable the thread pool variable :ref:`thread_handling` should be set up to ``pool-of-threads`` value. This can be done by adding: ::
-
- thread_handling=pool-of-threads
-
-Although the default values for the thread pool should provide good performance, additional tuning
-can be performed with the dynamic system variables.
-
-.. note::
-
-  Current implementation of the thread pool is built in the server, unlike the upstream version which is implemented as a plugin. Another significant implementation difference is that this implementation doesn't try to minimize the number of concurrent transactions like the ``MySQL Enterprise Threadpool``. Because of these differences, this implementation is not compatible with the upstream version.
-
-Priority connection scheduling
-==============================
-
-Even though thread pool puts a limit on the number of concurrently running queries, the number of open transactions may remain high, because connections with already started transactions are put to the end of the queue. Higher number of open transactions has a number of implications on the currently running queries. To improve the performance new :ref:`thread_pool_high_prio_tickets` variable has been introduced.
-
-This variable controls the high priority queue policy. Each new connection is assigned this many tickets to enter the high priority queue. Whenever a query has to be queued to be executed later because no threads are available, the thread pool puts the connection into the high priority queue if the following conditions apply:
-
-  1. The connection has an open transaction in the server.
-  2. The number of high priority tickets of this connection is non-zero.
-
-If both the above conditions hold, the connection is put into the high priority queue and its tickets value is decremented. Otherwise the connection is put into the common queue with the initial tickets value specified with this option.
-
-Each time the thread pool looks for a new connection to process, first it checks the high priority queue, and picks connections from the common queue only when the high priority one is empty.
-
-The goal is to minimize the number of open transactions in the server. In many cases it is beneficial to give short-running transactions a chance to commit faster and thus deallocate server resources and locks without waiting in the same queue with other connections that are about to start a new transaction, or those that have run out of their high priority tickets.
-
-The default thread pool behavior is to always put events from already started transactions into the high priority queue, as we believe that results in better performance in vast majority of cases.
-
-With the value of ``0``, all connections are always put into the common queue, i.e. no priority scheduling is used as in the original implementation in *MariaDB*. The higher is the value, the more chances each transaction gets to enter the high priority queue and commit before it is put in the common queue.
-
-In some cases it is required to prioritize all statements for a specific connection regardless of whether they are executed as a part of a multi-statement transaction or in the autocommit mode. Or vice versa, some connections may require using the low priority queue for all statements unconditionally. To implement this new :ref:`thread_pool_high_prio_mode` variable has been introduced in *Percona Server for MySQL*.
-
-.. _low_priority_queue_throttling:
-
-Low priority queue throttling
------------------------------
-
-One case that can limit thread pool performance and even lead to deadlocks under high concurrency is a situation when thread groups are oversubscribed due to active threads reaching the oversubscribe limit, but all/most worker threads are actually waiting on locks currently held by a transaction from another connection that is not currently in the thread pool.
-
-What happens in this case is that those threads in the pool that have marked themselves inactive are not accounted to the oversubscribe limit. As a result, the number of threads (both active and waiting) in the pool grows until it hits :ref:`thread_pool_max_threads` value. If the connection executing the transaction which is holding the lock has managed to enter the thread pool by then, we get a large (depending on the :ref:`thread_pool_max_threads` value) number of concurrently running threads, and thus, suboptimal performance as a result. Otherwise, we get a deadlock as no more threads can be created to process those transaction(s) and release the lock(s).
-
-Such situations are prevented by throttling the low priority queue when the total number of worker threads (both active and waiting ones) reaches the oversubscribe limit. That is, if there are too many worker threads, do not start new transactions and create new threads until queued events from the already started transactions are processed.
-
-Handling of Long Network Waits
-==============================
-
-Certain types of workloads (large result sets, BLOBs, slow clients) can have longer waits on network I/O (socket reads and writes). Whenever server waits, this should be communicated to the Thread Pool, so it can start new query by either waking a waiting thread or sometimes creating a new one. This implementation has been ported from *MariaDB* patch `MDEV-156`.
-
-Version Specific Information
-============================
-
- * `8.0.12-1`: ``Thread Pool`` feature was ported from *Percona Server for MySQL* 5.7.
-
-System Variables
-================
-
-.. _thread_pool_idle_timeout:
-
-.. rubric:: ``thread_pool_idle_timeout``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - Yes
-   * - Config file
-     - Yes
-   * - Scope
-     - Global
-   * - Dynamic
-     - Yes
-   * - Data type
-     - Numeric
-   * - Default
-     - 60 (seconds)
-
-This variable can be used to limit the time an idle thread should wait before exiting.
-
-.. _thread_pool_high_prio_mode:
-
-.. rubric:: ``thread_pool_high_prio_mode``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - Yes
-   * - Config file
-     - Yes
-   * - Scope
-     - Global, Session
-   * - Dynamic
-     - Yes
-   * - Data type
-     - String
-   * - Default
-     - ``transactions``
-   * - Allowed values
-     - ``transactions``, ``statements``, ``none``
-
-This variable is used to provide more fine-grained control over high priority scheduling either globally or per connection.
-
-The following values are allowed:
-
-  * ``transactions`` (the default). In this mode only statements from already started transactions may go into the high priority queue depending on the number of high priority tickets currently available in a connection (see :ref:`thread_pool_high_prio_tickets`).
-
-  * ``statements``. In this mode all individual statements go into the high priority queue, regardless of connection's transactional state and the number of available high priority tickets. This value can be used to prioritize ``AUTOCOMMIT`` transactions or other kinds of statements such as administrative ones for specific connections. Note that setting this value globally essentially disables high priority scheduling, since in this case all statements from all connections will use a single queue (the high priority one)
-
-  * ``none``. This mode disables high priority queue for a connection. Some connections (e.g. monitoring) may be insensitive to execution latency and/or never allocate any server resources that would otherwise impact performance in other connections and thus, do not really require high priority scheduling. Note that setting :ref:`thread_pool_high_prio_mode` to ``none`` globally has essentially the same effect as setting it to ``statements`` globally: all connections will always use a single queue (the low priority one in this case).
-
-.. _thread_pool_high_prio_tickets:
-
-.. rubric:: ``thread_pool_high_prio_tickets``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - Yes
-   * - Config file
-     - Yes
-   * - Scope
-     - Global, Session
-   * - Dynamic
-     - Yes
-   * - Data type
-     - Numeric
-   * - Default
-     - 4294967295
-
-This variable controls the high priority queue policy. Each new connection is assigned this many tickets to enter the high priority queue. Setting this variable to ``0`` will disable the high priority queue.
-
-.. _thread_pool_max_threads:
-
-.. rubric:: ``thread_pool_max_threads``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - Yes
-   * - Config file
-     - Yes
-   * - Scope
-     - Global
-   * - Dynamic
-     - Yes
-   * - Data type
-     - Numeric
-   * - Default
-     - 100000
-
-This variable can be used to limit the maximum number of threads in the pool. Once this number is reached no new threads will be created.
-
-.. _thread_pool_oversubscribe:
-
-.. rubric:: ``thread_pool_oversubscribe``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - Yes
-   * - Config file
-     - Yes
-   * - Scope
-     - Global
-   * - Dynamic
-     - Yes
-   * - Data type
-     - Numeric
-   * - Default
-     - 3
-
-The higher the value of this parameter the more threads can be run at the same time, if the values is lower than ``3`` it could lead to more sleeps and wake-ups.
-
-.. _thread_pool_size:
-
-.. rubric:: ``thread_pool_size``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - Yes
-   * - Config file
-     - Yes
-   * - Scope
-     - Global
-   * - Dynamic
-     - Yes
-   * - Data type
-     - Numeric
-   * - Default
-     - Number of processors
-
-This variable can be used to define the number of threads that can use the CPU at the same time.
-
-.. _thread_pool_stall_limit:
-
-.. rubric:: ``thread_pool_stall_limit``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - Yes
-   * - Config file
-     - Yes
-   * - Scope
-     - Global
-   * - Dynamic
-     - No
-   * - Data type
-     - Numeric
-   * - Default
-     - 500 (ms)
-
-The number of milliseconds before a running thread is considered stalled. When this limit is reached thread pool will wake up or create another thread. This is being used to prevent a long-running query from monopolizing the pool.
-
-.. rubric:: Upgrading from a version before 8.0.14 to 8.0.14 or higher
-
-Starting with `8.0.14`, *Percona Server for MySQL* uses the upstream implementation of the admin_port. The variables :ref:`extra_port` and :ref:`extra_max_connections` are removed and not supported. It is essential to remove the ``extra_port`` and ``extra_max_connections`` variables from your configuration file before you attempt to upgrade from a release before `8.0.14` to *Percona Server for MySQL* version `8.0.14` or higher. Otherwise, a server produces a boot error and refuses to start.
-
-.. seealso::
-    *MySQL* Documentation:
-        - `admin_port <https://dev.mysql.com/doc/refman/8.0/en/server-system-variables.html#sysvar_admin_port>`__
-
-.. _extra_port:
-
-.. rubric:: ``extra_port``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - Yes
-   * - Config file
-     - Yes
-   * - Scope
-     - Global
-   * - Dynamic
-     - No
-   * - Data type
-     - Numeric
-   * - Default
-     - 0
-
-The varible was removed in :ref:`8.0.14`. This variable can be used to specify an additional port that *Percona Server for MySQL* will listen on. This can be used in case no new connections can be established
-due to all worker threads being busy or being locked when ``pool-of-threads``
-feature is enabled. To connect to the extra port the following command can be
-used: 
-
-.. code-block:: bash
-
-  mysql --port='extra-port-number' --protocol=tcp
-
-.. _extra_max_connections:
-
-.. rubric:: ``extra_max_connections``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - Yes
-   * - Config file
-     - Yes
-   * - Scope
-     - Global
-   * - Dynamic
-     - Yes
-   * - Data type
-     - Numeric
-   * - Default
-     - 1
-     
-The varible was removed in :ref:`8.0.14`. This variable can be used to specify the maximum allowed number of connections
-plus one extra ``SUPER`` users connection on the :ref:`extra_port`. This
-can be used with the :ref:`extra_port` variable to access the server in
-case no new connections can be established due to all worker threads being busy
-or being locked when ``pool-of-threads`` feature is enabled.
-
-Status Variables
-=====================
-
-.. _Threadpool_idle_threads:
-
-.. rubric:: ``Threadpool_idle_threads``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Data type
-     - Numeric
-   * - Scope
-     - Global
-
-This status variable shows the number of idle threads in the pool.
-
-.. _Threadpool_threads:
-
-.. rubric:: ``Threadpool_threads``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Data type
-     - Numeric
-   * - Scope
-     - Global
-
-This status variable shows the number of threads in the pool.
-
-Other Reading
-=============
-
- * `Thread pool in MariaDB 5.5  <https://kb.askmonty.org/en/threadpool-in-55/>`_
-
- * `Thread pool implementation in Oracle MySQL <http://mikaelronstrom.blogspot.com/2011_10_01_archive.html>`_
diff --git a/doc/source/performance/xtradb_performance_improvements_for_io-bound_highly-concurrent_workloads.rst b/doc/source/performance/xtradb_performance_improvements_for_io-bound_highly-concurrent_workloads.rst
deleted file mode 100644
index 5f7a3bd2bc9f..000000000000
--- a/doc/source/performance/xtradb_performance_improvements_for_io-bound_highly-concurrent_workloads.rst
+++ /dev/null
@@ -1,154 +0,0 @@
-.. _xtradb_performance_improvements_for_io-bound_highly-concurrent_workloads:
-
-=========================================================================
-XtraDB Performance Improvements for I/O-Bound Highly-Concurrent Workloads
-=========================================================================
-
-.. _ps.buffer-pool.free-list.priority-refill:
-
-Priority refill for the buffer pool free list
-=============================================
-
-In highly-concurrent I/O-bound workloads the following situation may happen:
-
- 1. Buffer pool free lists are used faster than they are refilled by the LRU
-    cleaner thread.
-
- 2. Buffer pool free lists become empty and more and more query and utility
-    (i.e. purge) threads stall, checking whether a buffer pool free list has
-    became non-empty, sleeping, performing single-page LRU flushes.
-
- 3. The number of buffer pool free list mutex waiters increases.
-
- 4. When the LRU manager thread (or a single page LRU flush by a query thread)
-    finally produces a free page, it is starved from putting it on the buffer
-    pool free list as it must acquire the buffer pool free list mutex too.
-    However, being one thread in up to hundreds, the chances of a prompt
-    acquisition are low.
-
-This is addressed by delegating all the LRU flushes to the to the LRU manager
-thread, never attempting to evict a page or perform a LRU single page flush by
-a query thread, and introducing a backoff algorithm to reduce buffer pool free
-list mutex pressure on empty buffer pool free lists. This is controlled through
-a new system variable :ref:`innodb_empty_free_list_algorithm`.
-
-.. _innodb_empty_free_list_algorithm:
-
-.. rubric:: ``innodb_empty_free_list_algorithm``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - Yes
-   * - Config File
-     - Yes
-   * - Scope
-     - Global
-   * - Dynamic
-     - Yes
-   * - Data type
-     - legacy, backoff
-   * - Default
-     - legacy
-
-When ``legacy`` option is set, server will use the upstream algorithm and when
-the ``backoff`` is selected, *Percona* implementation will be used.
-
-.. _lru_manager_threads:
-
-Multi-threaded LRU flusher
-==========================
-
-*Percona Server for MySQL* features a true multi-threaded LRU flushing. In this scheme,
-each buffer pool instance has its own dedicated LRU manager thread that is
-tasked with performing LRU flushes and evictions to refill the free list of that
-buffer pool instance. Existing multi-threaded flusher no longer does any LRU
-flushing and is tasked with flush list flushing only.
-
-* All threads still synchronize on each coordinator thread iteration. If a
-  particular flushing job is stuck on one of the worker threads, the rest will
-  idle until the stuck one completes.
-* The coordinator thread heuristics focus on flush list adaptive flushing
-  without considering the state of free lists, which might be in need of urgent
-  refill for a subset of buffer pool instances on a loaded server.
-* LRU flushing is serialized with flush list flushing for each buffer pool
-  instance, introducing the risk that the right flushing mode will not happen
-  for a particular instance because it is being flushed in the other mode.
-
-The following *InnoDB* metrics are no longer accounted, as their semantics do
-not make sense under the current LRU flushing design:
-``buffer_LRU_batch_flush_avg_time_slot``, ``buffer_LRU_batch_flush_avg_pass``,
-``buffer_LRU_batch_flush_avg_time_thread``,
-``buffer_LRU_batch_flush_avg_time_est``.
-
-The need for *InnoDB* recovery thread writer threads is also removed,
-consequently all associated code is deleted.
-
-.. _doublewrite_buffer:
-
-Doublewrite buffer
-===========================
-
-As of *Percona Server for MySQL* 8.0.20-11, the parallel doublewrite buffer is replaced with the `MySQL implementation <https://dev.mysql.com/doc/refman/8.0/en/innodb-doublewrite-buffer.html>`_.
-
-.. _innodb_parallel_doublewrite_path:
-
-.. rubric:: ``innodb_parallel_doublewrite_path``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - Yes
-   * - Scope
-     - Global
-   * - Dynamic
-     - No
-   * - Data type
-     - String
-   * - Default
-     - ``xb_doublewrite``
-
-As of *Percona Server for MySQL* 8.0.20-11, this variable is considered **deprecated** and has no effect. You should use `innodb_doublewrite_dir <https://dev.mysql.com/doc/refman/8.0/en/innodb-parameters.html#sysvar_innodb_doublewrite_dir>`_.
-
-This variable is used to specify the location of the parallel doublewrite file.
-It accepts both absolute and relative paths. In the latter case they are
-treated as relative to the data directory.
-
-*Percona Server for MySQL* has introduced several options, only available in builds
-compiled with ``UNIV_PERF_DEBUG`` C preprocessor define.
-
-.. _innodb_sched_priority_master:
-
-.. rubric:: ``innodb_sched_priority_master``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - Yes
-   * - Config file
-     - Yes
-   * - Scope
-     - Global
-   * - Dynamic
-     - Yes
-   * - Data type
-     - Boolean
-
-This variable can be added to the configuration file.
-
-Other Reading
-=============
-
-* Bug :mysqlbug:`74637` - make dirty page flushing more adaptive
-* Bug :mysqlbug:`67808` - in innodb engine, double write and multi-buffer pool
-  instance reduce concurrency
-* Bug :mysqlbug:`69232` - buf_dblwr->mutex can be splited into two
diff --git a/doc/source/ps-variables.rst b/doc/source/ps-variables.rst
deleted file mode 100644
index 3a56d171463a..000000000000
--- a/doc/source/ps-variables.rst
+++ /dev/null
@@ -1,1514 +0,0 @@
-.. _ps_variables:
-
-================================================================================
- List of variables introduced in *Percona Server for MySQL* 8.0
-================================================================================
-
-System Variables
-================
-
-.. tabularcolumns:: |p{8.5cm}|p{1.5cm}|p{1.5cm}|p{2cm}|p{1.5cm}|
-
-.. list-table::
-   :header-rows: 1
-
-   * - Name
-     - Cmd-Line
-     - Option File
-     - Var Scope
-     - Dynamic
-   * - :ref:`audit_log_buffer_size`
-     - Yes
-     - Yes
-     - Global
-     - No
-   * - :ref:`audit_log_file`
-     - Yes
-     - Yes
-     - Global
-     - No
-   * - :ref:`audit_log_flush`
-     - Yes
-     - Yes
-     - Global
-     - Yes
-   * - :ref:`audit_log_format`
-     - Yes
-     - Yes
-     - Global
-     - No
-   * - :ref:`audit_log_handler`
-     - Yes
-     - Yes
-     - Global
-     - No
-   * - :ref:`audit_log_policy`
-     - Yes
-     - Yes
-     - Global
-     - Yes
-   * - :ref:`audit_log_rotate_on_size`
-     - Yes
-     - Yes
-     - Global
-     - No
-   * - :ref:`audit_log_rotations`
-     - Yes
-     - Yes
-     - Global
-     - No
-   * - :ref:`audit_log_strategy`
-     - Yes
-     - Yes
-     - Global
-     - No
-   * - :ref:`audit_log_syslog_facility`
-     - Yes
-     - Yes
-     - Global
-     - No
-   * - :ref:`audit_log_syslog_ident`
-     - Yes
-     - Yes
-     - Global
-     - No
-   * - :ref:`audit_log_syslog_priority`
-     - Yes
-     - Yes
-     - Global
-     - No
-   * - :ref:`csv_mode`
-     - Yes
-     - Yes
-     - Both
-     - Yes
-   * - :ref:`enforce_storage_engine`
-     - Yes
-     - Yes
-     - Global
-     - No
-   * - :ref:`expand_fast_index_creation`
-     - Yes
-     - No
-     - Both
-     - Yes
-   * - :ref:`extra_max_connections`
-     - Yes
-     - Yes
-     - Global
-     - Yes
-   * - :ref:`extra_port`
-     - Yes
-     - Yes
-     - Global
-     - No
-   * - :ref:`have_backup_locks`
-     - Yes
-     - No
-     - Global
-     - No
-   * - :ref:`have_backup_safe_binlog_info`
-     - Yes
-     - No
-     - Global
-     - No
-   * - :ref:`have_snapshot_cloning`
-     - Yes
-     - No
-     - Global
-     - No
-   * - :ref:`innodb_cleaner_lsn_age_factor`
-     - Yes
-     - Yes
-     - Global
-     - Yes
-   * - :ref:`innodb_corrupt_table_action`
-     - Yes
-     - Yes
-     - Global
-     - Yes
-   * - :ref:`innodb_empty_free_list_algorithm`
-     - Yes
-     - Yes
-     - Global
-     - Yes
-   * - :ref:`innodb_encrypt_online_alter_logs`
-     - Yes
-     - Yes
-     - Global
-     - Yes
-   * - :ref:`innodb_encrypt_tables`
-     - Yes
-     - Yes
-     - Global
-     - Yes
-   * - :ref:`innodb_kill_idle_transaction`
-     - Yes
-     - Yes
-     - Global
-     - Yes
-   * - :ref:`innodb_max_bitmap_file_size`
-     - Yes
-     - Yes
-     - Global
-     - Yes
-   * - :ref:`innodb_max_changed_pages`
-     - Yes
-     - Yes
-     - Global
-     - Yes
-   * - :ref:`innodb_print_lock_wait_timeout_info`
-     - Yes
-     - Yes
-     - Global
-     - Yes
-   * - :ref:`innodb_show_locks_held`
-     - Yes
-     - Yes
-     - Global
-     - Yes
-   * - :ref:`innodb_temp_tablespace_encrypt`
-     - Yes
-     - Yes
-     - Global
-     - No
-   * - :ref:`innodb_track_changed_pages`
-     - Yes
-     - Yes
-     - Global
-     - No
-   * - :ref:`keyring_vault_config`
-     - Yes
-     - Yes
-     - Global
-     - Yes
-   * - :ref:`keyring_vault_timeout`
-     - Yes
-     - Yes
-     - Global
-     - Yes
-   * - :ref:`log_slow_filter`
-     - Yes
-     - Yes
-     - Both
-     - Yes
-   * - :ref:`log_slow_rate_limit`
-     - Yes
-     - Yes
-     - Both
-     - Yes
-   * - :ref:`log_slow_rate_type`
-     - Yes
-     - Yes
-     - Global
-     - Yes
-   * - :ref:`log_slow_sp_statements`
-     - Yes
-     - Yes
-     - Global
-     - Yes
-   * - :ref:`log_slow_verbosity`
-     - Yes
-     - Yes
-     - Both
-     - Yes
-   * - :ref:`log_warnings_suppress`
-     - Yes
-     - Yes
-     - Global
-     - Yes
-   * - :ref:`proxy_protocol_networks`
-     - Yes
-     - Yes
-     - Global
-     - No
-   * - :ref:`query_response_time_flush`
-     - Yes
-     - No
-     - Global
-     - No
-   * - :ref:`query_response_time_range_base`
-     - Yes
-     - Yes
-     - Global
-     - Yes
-   * - :ref:`query_response_time_stats`
-     - Yes
-     - Yes
-     - Global
-     - Yes
-   * - :ref:`slow_query_log_always_write_time`
-     - Yes
-     - Yes
-     - Global
-     - Yes
-   * - :ref:`slow_query_log_use_global_control`
-     - Yes
-     - Yes
-     - Global
-     - Yes
-   * - :ref:`thread_pool_high_prio_mode`
-     - Yes
-     - Yes
-     - Both
-     - Yes
-   * - :ref:`thread_pool_high_prio_tickets`
-     - Yes
-     - Yes
-     - Both
-     - Yes
-   * - :ref:`thread_pool_idle_timeout`
-     - Yes
-     - Yes
-     - Global
-     - Yes
-   * - :ref:`thread_pool_max_threads`
-     - Yes
-     - Yes
-     - Global
-     - Yes
-   * - :ref:`thread_pool_oversubscribe`
-     - Yes
-     - Yes
-     - Global
-     - Yes
-   * - :ref:`thread_pool_size`
-     - Yes
-     - Yes
-     - Global
-     - Yes
-   * - :ref:`thread_pool_stall_limit`
-     - Yes
-     - Yes
-     - Global
-     - No
-   * - :ref:`thread_statistics`
-     - Yes
-     - Yes
-     - Global
-     - Yes
-   * - :ref:`tokudb_alter_print_error`
-     -
-     -
-     -
-     -
-   * - :ref:`tokudb_analyze_delete_fractionref
-     -
-     -
-     -
-     -
-   * - :ref:`tokudb_analyze_in_background`
-     - Yes
-     - Yes
-     - Both
-     - Yes
-   * - :ref:`tokudb_analyze_mode`
-     - Yes
-     - Yes
-     - Both
-     - Yes
-   * - :ref:`tokudb_analyze_throttle`
-     - Yes
-     - Yes
-     - Both
-     - Yes
-   * - :ref:`tokudb_analyze_time`
-     - Yes
-     - Yes
-     - Both
-     - Yes
-   * - :ref:`tokudb_auto_analyze`
-     - Yes
-     - Yes
-     - Both
-     - Yes
-   * - :ref:`tokudb_block_size`
-     -
-     -
-     -
-     -
-   * - :ref:`tokudb_bulk_fetch`
-     -
-     -
-     -
-     -
-   * - :ref:`tokudb_cache_size`
-     -
-     -
-     -
-     -
-   * - :ref:`tokudb_cachetable_pool_threads`
-     - Yes
-     - Yes
-     - Global
-     - No
-   * - :ref:`tokudb_cardinality_scale_percent`
-     -
-     -
-     -
-     -
-   * - :ref:`tokudb_check_jemalloc`
-     -
-     -
-     -
-     -
-   * - :ref:`tokudb_checkpoint_lock`
-     -
-     -
-     -
-     -
-   * - :ref:`tokudb_checkpoint_on_flush_logs`
-     -
-     -
-     -
-     -
-   * - :ref:`tokudb_checkpoint_pool_threads`
-     - Yes
-     - Yes
-     - Global
-     - No
-   * - :ref:`tokudb_checkpointing_period`
-     -
-     -
-     -
-     -
-   * - :ref:`tokudb_cleaner_iterations`
-     -
-     -
-     -
-     -
-   * - :ref:`tokudb_cleaner_period`
-     -
-     -
-     -
-     -
-   * - :ref:`tokudb_client_pool_threads`
-     - Yes
-     - Yes
-     - Global
-     - No
-   * - :ref:`tokudb_commit_sync`
-     -
-     -
-     -
-     -
-   * - :ref:`tokudb_compress_buffers_before_eviction`
-     - Yes
-     - Yes
-     - Global
-     - No
-   * - :ref:`tokudb_create_index_online`
-     -
-     -
-     -
-     -
-   * - :ref:`tokudb_data_dir`
-     -
-     -
-     -
-     -
-   * - :ref:`tokudb_debug`
-     -
-     -
-     -
-     -
-   * - :ref:`tokudb_directio`
-     -
-     -
-     -
-     -
-   * - :ref:`tokudb_disable_hot_alter`
-     -
-     -
-     -
-     -
-   * - :ref:`tokudb_disable_prefetching`
-     -
-     -
-     -
-     -
-   * - :ref:`tokudb_disable_slow_alter`
-     -
-     -
-     -
-     -
-   * - :ref:`tokudb_empty_scan`
-     -
-     -
-     -
-     -
-   * - :ref:`tokudb_enable_partial_eviction`
-     - Yes
-     - Yes
-     - Global
-     - No
-   * - :ref:`tokudb_fanout`
-     - Yes
-     - Yes
-     - Both
-     - Yes
-   * - :ref:`tokudb_fs_reserve_percent`
-     -
-     -
-     -
-     -
-   * - :ref:`tokudb_fsync_log_period`
-     -
-     -
-     -
-     -
-   * - :ref:`tokudb_hide_default_row_format`
-     -
-     -
-     -
-     -
-   * - :ref:`tokudb_killed_time`
-     -
-     -
-     -
-     -
-   * - :ref:`tokudb_last_lock_timeout`
-     -
-     -
-     -
-     -
-   * - :ref:`tokudb_load_save_space`
-     -
-     -
-     -
-     -
-   * - :ref:`tokudb_loader_memory_size`
-     -
-     -
-     -
-     -
-   * - :ref:`tokudb_lock_timeout`
-     -
-     -
-     -
-     -
-   * - :ref:`tokudb_lock_timeout_debug`
-     -
-     -
-     -
-     -
-   * - :ref:`tokudb_log_dir`
-     -
-     -
-     -
-     -
-   * - :ref:`tokudb_max_lock_memory`
-     -
-     -
-     -
-     -
-   * - :ref:`tokudb_optimize_index_fraction`
-     -
-     -
-     -
-     -
-   * - :ref:`tokudb_optimize_index_name`
-     -
-     -
-     -
-     -
-   * - :ref:`tokudb_optimize_throttle`
-     -
-     -
-     -
-     -
-   * - :ref:`tokudb_pk_insert_mode`
-     -
-     -
-     -
-     -
-   * - :ref:`tokudb_prelock_empty`
-     -
-     -
-     -
-     -
-   * - :ref:`tokudb_read_block_size`
-     -
-     -
-     -
-     -
-   * - :ref:`tokudb_read_buf_size`
-     -
-     -
-     -
-     -
-   * - :ref:`tokudb_read_status_frequency`
-     -
-     -
-     -
-     -
-   * - :ref:`tokudb_row_format`
-     -
-     -
-     -
-     -
-   * - :ref:`tokudb_rpl_check_readonly`
-     -
-     -
-     -
-     -
-   * - :ref:`tokudb_rpl_lookup_rows`
-     -
-     -
-     -
-     -
-   * - :ref:`tokudb_rpl_lookup_rows_delay`
-     -
-     -
-     -
-     -
-   * - :ref:`tokudb_rpl_unique_checks`
-     -
-     -
-     -
-     -
-   * - :ref:`tokudb_rpl_unique_checks_delay`
-     -
-     -
-     -
-     -
-   * - :ref:`tokudb_strip_frm_data`
-     - Yes
-     - Yes
-     - Global
-     - No
-   * - :ref:`tokudb_support_xa`
-     -
-     -
-     -
-     -
-   * - :ref:`tokudb_tmp_dir`
-     -
-     -
-     -
-     -
-   * - :ref:`tokudb_version`
-     -
-     -
-     -
-     -
-   * - :ref:`tokudb_write_status_frequency`
-     -
-     -
-     -
-     -
-   * - :ref:`userstat`
-     - Yes
-     - Yes
-     - Global
-     - Yes
-   * - :ref:`version_comment`
-     - Yes
-     - Yes
-     - Global
-     - Yes
-   * - :ref:`version_suffix`
-     - Yes
-     - Yes
-     - Global
-     - Yes
-
-Status Variables
-================
-
-.. tabularcolumns:: |p{13cm}|p{1.5cm}|p{1.5cm}|
-
-.. list-table::
-   :header-rows: 1
-
-   * - Name
-     - Var Type
-     - Var Scope
-   * - :ref:`Binlog_snapshot_file`
-     - String
-     - Global
-   * - :ref:`Binlog_snapshot_position`
-     - Numeric
-     - Global
-   * - :ref:`Com_lock_binlog_for_backup`
-     - Numeric
-     - Both
-   * - :ref:`Com_lock_tables_for_backup`
-     - Numeric
-     - Both
-   * - :ref:`Com_show_client_statistics`
-     - Numeric
-     - Both
-   * - :ref:`Com_show_index_statistics`
-     - Numeric
-     - Both
-   * - :ref:`Com_show_table_statistics`
-     - Numeric
-     - Both
-   * - :ref:`Com_show_thread_statistics`
-     - Numeric
-     - Both
-   * - :ref:`Com_show_user_statistics`
-     - Numeric
-     - Both
-   * - :ref:`Com_unlock_binlog`
-     - Numeric
-     - Both
-   * - :ref:`Innodb_background_log_sync`
-     - Numeric
-     - Global
-   * - :ref:`Innodb_buffer_pool_pages_LRU_flushed`
-     - Numeric
-     - Global
-   * - :ref:`Innodb_buffer_pool_pages_made_not_young`
-     - Numeric
-     - Global
-   * - :ref:`Innodb_buffer_pool_pages_made_young`
-     - Numeric
-     - Global
-   * - :ref:`Innodb_buffer_pool_pages_old`
-     - Numeric
-     - Global
-   * - :ref:`Innodb_checkpoint_age`
-     - Numeric
-     - Global
-   * - :ref:`Innodb_checkpoint_max_age`
-     - Numeric
-     - Global
-   * - :ref:`Innodb_ibuf_free_list`
-     - Numeric
-     - Global
-   * - :ref:`Innodb_ibuf_segment_size`
-     - Numeric
-     - Global
-   * - :ref:`Innodb_lsn_current`
-     - Numeric
-     - Global
-   * - :ref:`Innodb_lsn_flushed`
-     - Numeric
-     - Global
-   * - :ref:`Innodb_lsn_last_checkpoint`
-     - Numeric
-     - Global
-   * - :ref:`Innodb_master_thread_active_loops`
-     - Numeric
-     - Global
-   * - :ref:`Innodb_master_thread_idle_loops`
-     - Numeric
-     - Global
-   * - :ref:`Innodb_max_trx_id`
-     - Numeric
-     - Global
-   * - :ref:`Innodb_mem_adaptive_hash`
-     - Numeric
-     - Global
-   * - :ref:`Innodb_mem_dictionary`
-     - Numeric
-     - Global
-   * - :ref:`Innodb_oldest_view_low_limit_trx_id`
-     - Numeric
-     - Global
-   * - :ref:`Innodb_purge_trx_id`
-     - Numeric
-     - Global
-   * - :ref:`Innodb_purge_undo_no`
-     - Numeric
-     - Global
-   * - :ref:`Threadpool_idle_threads`
-     - Numeric
-     - Global
-   * - :ref:`Threadpool_threads`
-     - Numeric
-     - Global
-   * - :ref:`Tokudb_DB_OPENS`
-     -
-     -
-   * - :ref:`Tokudb_DB_CLOSES`
-     -
-     -
-   * - :ref:`Tokudb_DB_OPEN_CURRENT`
-     -
-     -
-   * - :ref:`Tokudb_DB_OPEN_MAX`
-     -
-     -
-   * - :ref:`Tokudb_LEAF_ENTRY_MAX_COMMITTED_XR`
-     -
-     -
-   * - :ref:`Tokudb_LEAF_ENTRY_MAX_PROVISIONAL_XR`
-     -
-     -
-   * - :ref:`Tokudb_LEAF_ENTRY_EXPANDED`
-     -
-     -
-   * - :ref:`Tokudb_LEAF_ENTRY_MAX_MEMSIZE`
-     -
-     -
-   * - :ref:`Tokudb_LEAF_ENTRY_APPLY_GC_BYTES_IN`
-     -
-     -
-   * - :ref:`Tokudb_LEAF_ENTRY_APPLY_GC_BYTES_OUT`
-     -
-     -
-   * - :ref:`Tokudb_LEAF_ENTRY_NORMAL_GC_BYTES_IN`
-     -
-     -
-   * - :ref:`Tokudb_LEAF_ENTRY_NORMAL_GC_BYTES_OUT`
-     -
-     -
-   * - :ref:`Tokudb_CHECKPOINT_PERIOD`
-     -
-     -
-   * - :ref:`Tokudb_CHECKPOINT_FOOTPRINT`
-     -
-     -
-   * - :ref:`Tokudb_CHECKPOINT_LAST_BEGAN`
-     -
-     -
-   * - :ref:`Tokudb_CHECKPOINT_LAST_COMPLETE_BEGAN`
-     -
-     -
-   * - :ref:`Tokudb_CHECKPOINT_LAST_COMPLETE_ENDED`
-     -
-     -
-   * - :ref:`Tokudb_CHECKPOINT_DURATION`
-     -
-     -
-   * - :ref:`Tokudb_CHECKPOINT_DURATION_LAST`
-     -
-     -
-   * - :ref:`Tokudb_CHECKPOINT_LAST_LSN`
-     -
-     -
-   * - :ref:`Tokudb_CHECKPOINT_TAKEN`
-     -
-     -
-   * - :ref:`Tokudb_CHECKPOINT_FAILED`
-     -
-     -
-   * - :ref:`Tokudb_CHECKPOINT_WAITERS_NOW`
-     -
-     -
-   * - :ref:`Tokudb_CHECKPOINT_WAITERS_MAX`
-     -
-     -
-   * - :ref:`Tokudb_CHECKPOINT_CLIENT_WAIT_ON_MO`
-     -
-     -
-   * - :ref:`Tokudb_CHECKPOINT_CLIENT_WAIT_ON_CS`
-     -
-     -
-   * - :ref:`Tokudb_CHECKPOINT_BEGIN_TIME`
-     -
-     -
-   * - :ref:`Tokudb_CHECKPOINT_LONG_BEGIN_TIME`
-     -
-     -
-   * - :ref:`Tokudb_CHECKPOINT_LONG_BEGIN_COUNT`
-     -
-     -
-   * - :ref:`Tokudb_CHECKPOINT_END_TIME`
-     -
-     -
-   * - :ref:`Tokudb_CHECKPOINT_LONG_END_TIME`
-     -
-     -
-   * - :ref:`Tokudb_CHECKPOINT_LONG_END_COUNT`
-     -
-     -
-   * - :ref:`Tokudb_CACHETABLE_MISS`
-     -
-     -
-   * - :ref:`Tokudb_CACHETABLE_MISS_TIME`
-     -
-     -
-   * - :ref:`Tokudb_CACHETABLE_PREFETCHES`
-     -
-     -
-   * - :ref:`Tokudb_CACHETABLE_SIZE_CURRENT`
-     -
-     -
-   * - :ref:`Tokudb_CACHETABLE_SIZE_LIMIT`
-     -
-     -
-   * - :ref:`Tokudb_CACHETABLE_SIZE_WRITING`
-     -
-     -
-   * - :ref:`Tokudb_CACHETABLE_SIZE_NONLEAF`
-     -
-     -
-   * - :ref:`Tokudb_CACHETABLE_SIZE_LEAF`
-     -
-     -
-   * - :ref:`Tokudb_CACHETABLE_SIZE_ROLLBACK`
-     -
-     -
-   * - :ref:`Tokudb_CACHETABLE_SIZE_CACHEPRESSURE`
-     -
-     -
-   * - :ref:`Tokudb_CACHETABLE_SIZE_CLONED`
-     -
-     -
-   * - :ref:`Tokudb_CACHETABLE_EVICTIONS`
-     -
-     -
-   * - :ref:`Tokudb_CACHETABLE_CLEANER_EXECUTIONS`
-     -
-     -
-   * - :ref:`Tokudb_CACHETABLE_CLEANER_PERIOD`
-     -
-     -
-   * - :ref:`Tokudb_CACHETABLE_CLEANER_ITERATIONS`
-     -
-     -
-   * - :ref:`Tokudb_CACHETABLE_WAIT_PRESSURE_COUNT`
-     -
-     -
-   * - :ref:`Tokudb_CACHETABLE_WAIT_PRESSURE_TIME`
-     -
-     -
-   * - :ref:`Tokudb_CACHETABLE_LONG_WAIT_PRESSURE_COUNT`
-     -
-     -
-   * - :ref:`Tokudb_CACHETABLE_LONG_WAIT_PRESSURE_TIME`
-     -
-     -
-   * - :ref:`Tokudb_CACHETABLE_POOL_CLIENT_NUM_THREADS`
-     -
-     -
-   * - :ref:`Tokudb_CACHETABLE_POOL_CLIENT_NUM_THREADS_ACTIVE`
-     -
-     -
-   * - :ref:`Tokudb_CACHETABLE_POOL_CLIENT_QUEUE_SIZE`
-     -
-     -
-   * - :ref:`Tokudb_CACHETABLE_POOL_CLIENT_MAX_QUEUE_SIZE`
-     -
-     -
-   * - :ref:`Tokudb_CACHETABLE_POOL_CLIENT_TOTAL_ITEMS_PROCESSED`
-     -
-     -
-   * - :ref:`Tokudb_CACHETABLE_POOL_CLIENT_TOTAL_EXECUTION_TIME`
-     -
-     -
-   * - :ref:`Tokudb_CACHETABLE_POOL_CACHETABLE_NUM_THREADS`
-     -
-     -
-   * - :ref:`Tokudb_CACHETABLE_POOL_CACHETABLE_NUM_THREADS_ACTIVE`
-     -
-     -
-   * - :ref:`Tokudb_CACHETABLE_POOL_CACHETABLE_QUEUE_SIZE`
-     -
-     -
-   * - :ref:`Tokudb_CACHETABLE_POOL_CACHETABLE_MAX_QUEUE_SIZE`
-     -
-     -
-   * - :ref:`Tokudb_CACHETABLE_POOL_CACHETABLE_TOTAL_ITEMS_PROCESSED`
-     -
-     -
-   * - :ref:`Tokudb_CACHETABLE_POOL_CACHETABLE_TOTAL_EXECUTION_TIME`
-     -
-     -
-   * - :ref:`Tokudb_CACHETABLE_POOL_CHECKPOINT_NUM_THREADS`
-     -
-     -
-   * - :ref:`Tokudb_CACHETABLE_POOL_CHECKPOINT_NUM_THREADS_ACTIVE`
-     -
-     -
-   * - :ref:`Tokudb_CACHETABLE_POOL_CHECKPOINT_QUEUE_SIZE`
-     -
-     -
-   * - :ref:`Tokudb_CACHETABLE_POOL_CHECKPOINT_MAX_QUEUE_SIZE`
-     -
-     -
-   * - :ref:`Tokudb_CACHETABLE_POOL_CHECKPOINT_TOTAL_ITEMS_PROCESSED`
-     -
-     -
-   * - :ref:`Tokudb_CACHETABLE_POOL_CHECKPOINT_TOTAL_EXECUTION_TIME`
-     -
-     -
-   * - :ref:`Tokudb_LOCKTREE_MEMORY_SIZE`
-     -
-     -
-   * - :ref:`Tokudb_LOCKTREE_MEMORY_SIZE_LIMIT`
-     -
-     -
-   * - :ref:`Tokudb_LOCKTREE_ESCALATION_NUM`
-     -
-     -
-   * - :ref:`Tokudb_LOCKTREE_ESCALATION_SECONDS`
-     -
-     -
-   * - :ref:`Tokudb_LOCKTREE_LATEST_POST_ESCALATION_MEMORY_SIZE`
-     -
-     -
-   * - :ref:`Tokudb_LOCKTREE_OPEN_CURRENT`
-     -
-     -
-   * - :ref:`Tokudb_LOCKTREE_PENDING_LOCK_REQUESTS`
-     -
-     -
-   * - :ref:`Tokudb_LOCKTREE_STO_ELIGIBLE_NUM`
-     -
-     -
-   * - :ref:`Tokudb_LOCKTREE_STO_ENDED_NUM`
-     -
-     -
-   * - :ref:`Tokudb_LOCKTREE_STO_ENDED_SECONDS`
-     -
-     -
-   * - :ref:`Tokudb_LOCKTREE_WAIT_COUNT`
-     -
-     -
-   * - :ref:`Tokudb_LOCKTREE_WAIT_TIME`
-     -
-     -
-   * - :ref:`Tokudb_LOCKTREE_LONG_WAIT_COUNT`
-     -
-     -
-   * - :ref:`Tokudb_LOCKTREE_LONG_WAIT_TIME`
-     -
-     -
-   * - :ref:`Tokudb_LOCKTREE_TIMEOUT_COUNT`
-     -
-     -
-   * - :ref:`Tokudb_LOCKTREE_WAIT_ESCALATION_COUNT`
-     -
-     -
-   * - :ref:`Tokudb_LOCKTREE_WAIT_ESCALATION_TIME`
-     -
-     -
-   * - :ref:`Tokudb_LOCKTREE_LONG_WAIT_ESCALATION_COUNT`
-     -
-     -
-   * - :ref:`Tokudb_LOCKTREE_LONG_WAIT_ESCALATION_TIME`
-     -
-     -
-   * - :ref:`Tokudb_DICTIONARY_UPDATES`
-     -
-     -
-   * - :ref:`Tokudb_DICTIONARY_BROADCAST_UPDATES`
-     -
-     -
-   * - :ref:`Tokudb_DESCRIPTOR_SET`
-     -
-     -
-   * - :ref:`Tokudb_MESSAGES_IGNORED_BY_LEAF_DUE_TO_MSN`
-     -
-     -
-   * - :ref:`Tokudb_TOTAL_SEARCH_RETRIES`
-     -
-     -
-   * - :ref:`Tokudb_SEARCH_TRIES_GT_HEIGHT`
-     -
-     -
-   * - :ref:`Tokudb_SEARCH_TRIES_GT_HEIGHTPLUS3`
-     -
-     -
-   * - :ref:`Tokudb_LEAF_NODES_FLUSHED_NOT_CHECKPOINT`
-     -
-     -
-   * - :ref:`Tokudb_LEAF_NODES_FLUSHED_NOT_CHECKPOINT_BYTES`
-     -
-     -
-   * - :ref:`Tokudb_LEAF_NODES_FLUSHED_NOT_CHECKPOINT_UNCOMPRESSED_BYTES`
-     -
-     -
-   * - :ref:`Tokudb_LEAF_NODES_FLUSHED_NOT_CHECKPOINT_SECONDS`
-     -
-     -
-   * - :ref:`Tokudb_NONLEAF_NODES_FLUSHED_TO_DISK_NOT_CHECKPOINT`
-     -
-     -
-   * - :ref:`Tokudb_NONLEAF_NODES_FLUSHED_TO_DISK_NOT_CHECKPOINT_BYTES`
-     -
-     -
-   * - :ref:`Tokudb_NONLEAF_NODES_FLUSHED_TO_DISK_NOT_CHECKPOINT_UNCOMPRESSE`
-     -
-     -
-   * - :ref:`Tokudb_NONLEAF_NODES_FLUSHED_TO_DISK_NOT_CHECKPOINT_SECONDS`
-     -
-     -
-   * - :ref:`Tokudb_LEAF_NODES_FLUSHED_CHECKPOINT`
-     -
-     -
-   * - :ref:`Tokudb_LEAF_NODES_FLUSHED_CHECKPOINT_BYTES`
-     -
-     -
-   * - :ref:`Tokudb_LEAF_NODES_FLUSHED_CHECKPOINT_UNCOMPRESSED_BYTES`
-     -
-     -
-   * - :ref:`Tokudb_LEAF_NODES_FLUSHED_CHECKPOINT_SECONDS`
-     -
-     -
-   * - :ref:`Tokudb_NONLEAF_NODES_FLUSHED_TO_DISK_CHECKPOINT`
-     -
-     -
-   * - :ref:`Tokudb_NONLEAF_NODES_FLUSHED_TO_DISK_CHECKPOINT_BYTES`
-     -
-     -
-   * - :ref:`Tokudb_NONLEAF_NODES_FLUSHED_TO_DISK_CHECKPOINT_UNCOMPRESSED_BY`
-     -
-     -
-   * - :ref:`Tokudb_NONLEAF_NODES_FLUSHED_TO_DISK_CHECKPOINT_SECONDS`
-     -
-     -
-   * - :ref:`Tokudb_LEAF_NODE_COMPRESSION_RATIO`
-     -
-     -
-   * - :ref:`Tokudb_NONLEAF_NODE_COMPRESSION_RATIO`
-     -
-     -
-   * - :ref:`Tokudb_OVERALL_NODE_COMPRESSION_RATIO`
-     -
-     -
-   * - :ref:`Tokudb_NONLEAF_NODE_PARTIAL_EVICTIONS`
-     -
-     -
-   * - :ref:`Tokudb_NONLEAF_NODE_PARTIAL_EVICTIONS_BYTES`
-     -
-     -
-   * - :ref:`Tokudb_LEAF_NODE_PARTIAL_EVICTIONS`
-     -
-     -
-   * - :ref:`Tokudb_LEAF_NODE_PARTIAL_EVICTIONS_BYTES`
-     -
-     -
-   * - :ref:`Tokudb_LEAF_NODE_FULL_EVICTIONS`
-     -
-     -
-   * - :ref:`Tokudb_LEAF_NODE_FULL_EVICTIONS_BYTES`
-     -
-     -
-   * - :ref:`Tokudb_NONLEAF_NODE_FULL_EVICTIONS`
-     -
-     -
-   * - :ref:`Tokudb_NONLEAF_NODE_FULL_EVICTIONS_BYTES`
-     -
-     -
-   * - :ref:`Tokudb_LEAF_NODES_CREATED`
-     -
-     -
-   * - :ref:`Tokudb_NONLEAF_NODES_CREATED`
-     -
-     -
-   * - :ref:`Tokudb_LEAF_NODES_DESTROYED`
-     -
-     -
-   * - :ref:`Tokudb_NONLEAF_NODES_DESTROYED`
-     -
-     -
-   * - :ref:`Tokudb_MESSAGES_INJECTED_AT_ROOT_BYTES`
-     -
-     -
-   * - :ref:`Tokudb_MESSAGES_FLUSHED_FROM_H1_TO_LEAVES_BYTES`
-     -
-     -
-   * - :ref:`Tokudb_MESSAGES_IN_TREES_ESTIMATE_BYTES`
-     -
-     -
-   * - :ref:`Tokudb_MESSAGES_INJECTED_AT_ROOT`
-     -
-     -
-   * - :ref:`Tokudb_BROADCASE_MESSAGES_INJECTED_AT_ROOT`
-     -
-     -
-   * - :ref:`Tokudb_BASEMENTS_DECOMPRESSED_TARGET_QUERY`
-     -
-     -
-   * - :ref:`Tokudb_BASEMENTS_DECOMPRESSED_PRELOCKED_RANGE`
-     -
-     -
-   * - :ref:`Tokudb_BASEMENTS_DECOMPRESSED_PREFETCH`
-     -
-     -
-   * - :ref:`Tokudb_BASEMENTS_DECOMPRESSED_FOR_WRITE`
-     -
-     -
-   * - :ref:`Tokudb_BUFFERS_DECOMPRESSED_TARGET_QUERY`
-     -
-     -
-   * - :ref:`Tokudb_BUFFERS_DECOMPRESSED_PRELOCKED_RANGE`
-     -
-     -
-   * - :ref:`Tokudb_BUFFERS_DECOMPRESSED_PREFETCH`
-     -
-     -
-   * - :ref:`Tokudb_BUFFERS_DECOMPRESSED_FOR_WRITE`
-     -
-     -
-   * - :ref:`Tokudb_PIVOTS_FETCHED_FOR_QUERY`
-     -
-     -
-   * - :ref:`Tokudb_PIVOTS_FETCHED_FOR_QUERY_BYTES`
-     -
-     -
-   * - :ref:`Tokudb_PIVOTS_FETCHED_FOR_QUERY_SECONDS`
-     -
-     -
-   * - :ref:`Tokudb_PIVOTS_FETCHED_FOR_PREFETCH`
-     -
-     -
-   * - :ref:`Tokudb_PIVOTS_FETCHED_FOR_PREFETCH_BYTES`
-     -
-     -
-   * - :ref:`Tokudb_PIVOTS_FETCHED_FOR_PREFETCH_SECONDS`
-     -
-     -
-   * - :ref:`Tokudb_PIVOTS_FETCHED_FOR_WRITE`
-     -
-     -
-   * - :ref:`Tokudb_PIVOTS_FETCHED_FOR_WRITE_BYTES`
-     -
-     -
-   * - :ref:`Tokudb_PIVOTS_FETCHED_FOR_WRITE_SECONDS`
-     -
-     -
-   * - :ref:`Tokudb_BASEMENTS_FETCHED_TARGET_QUERY`
-     -
-     -
-   * - :ref:`Tokudb_BASEMENTS_FETCHED_TARGET_QUERY_BYTES`
-     -
-     -
-   * - :ref:`Tokudb_BASEMENTS_FETCHED_TARGET_QUERY_SECONDS`
-     -
-     -
-   * - :ref:`Tokudb_BASEMENTS_FETCHED_PRELOCKED_RANGE`
-     -
-     -
-   * - :ref:`Tokudb_BASEMENTS_FETCHED_PRELOCKED_RANGE_BYTES`
-     -
-     -
-   * - :ref:`Tokudb_BASEMENTS_FETCHED_PRELOCKED_RANGE_SECONDS`
-     -
-     -
-   * - :ref:`Tokudb_BASEMENTS_FETCHED_PREFETCH`
-     -
-     -
-   * - :ref:`Tokudb_BASEMENTS_FETCHED_PREFETCH_BYTES`
-     -
-     -
-   * - :ref:`Tokudb_BASEMENTS_FETCHED_PREFETCH_SECONDS`
-     -
-     -
-   * - :ref:`Tokudb_BASEMENTS_FETCHED_FOR_WRITE`
-     -
-     -
-   * - :ref:`Tokudb_BASEMENTS_FETCHED_FOR_WRITE_BYTES`
-     -
-     -
-   * - :ref:`Tokudb_BASEMENTS_FETCHED_FOR_WRITE_SECONDS`
-     -
-     -
-   * - :ref:`Tokudb_BUFFERS_FETCHED_TARGET_QUERY`
-     -
-     -
-   * - :ref:`Tokudb_BUFFERS_FETCHED_TARGET_QUERY_BYTES`
-     -
-     -
-   * - :ref:`Tokudb_BUFFERS_FETCHED_TARGET_QUERY_SECONDS`
-     -
-     -
-   * - :ref:`Tokudb_BUFFERS_FETCHED_PRELOCKED_RANGE`
-     -
-     -
-   * - :ref:`Tokudb_BUFFERS_FETCHED_PRELOCKED_RANGE_BYTES`
-     -
-     -
-   * - :ref:`Tokudb_BUFFERS_FETCHED_PRELOCKED_RANGE_SECONDS`
-     -
-     -
-   * - :ref:`Tokudb_BUFFERS_FETCHED_PREFETCH`
-     -
-     -
-   * - :ref:`Tokudb_BUFFERS_FETCHED_PREFETCH_BYTES`
-     -
-     -
-   * - :ref:`Tokudb_BUFFERS_FETCHED_PREFETCH_SECONDS`
-     -
-     -
-   * - :ref:`Tokudb_BUFFERS_FETCHED_FOR_WRITE`
-     -
-     -
-   * - :ref:`Tokudb_BUFFERS_FETCHED_FOR_WRITE_BYTES`
-     -
-     -
-   * - :ref:`Tokudb_BUFFERS_FETCHED_FOR_WRITE_SECONDS`
-     -
-     -
-   * - :ref:`Tokudb_LEAF_COMPRESSION_TO_MEMORY_SECONDS`
-     -
-     -
-   * - :ref:`Tokudb_LEAF_SERIALIZATION_TO_MEMORY_SECONDS`
-     -
-     -
-   * - :ref:`Tokudb_LEAF_DECOMPRESSION_TO_MEMORY_SECONDS`
-     -
-     -
-   * - :ref:`Tokudb_LEAF_DESERIALIZATION_TO_MEMORY_SECONDS`
-     -
-     -
-   * - :ref:`Tokudb_NONLEAF_COMPRESSION_TO_MEMORY_SECONDS`
-     -
-     -
-   * - :ref:`Tokudb_NONLEAF_SERIALIZATION_TO_MEMORY_SECONDS`
-     -
-     -
-   * - :ref:`Tokudb_NONLEAF_DECOMPRESSION_TO_MEMORY_SECONDS`
-     -
-     -
-   * - :ref:`Tokudb_NONLEAF_DESERIALIZATION_TO_MEMORY_SECONDS`
-     -
-     -
-   * - :ref:`Tokudb_PROMOTION_ROOTS_SPLIT`
-     -
-     -
-   * - :ref:`Tokudb_PROMOTION_LEAF_ROOTS_INJECTED_INTO`
-     -
-     -
-   * - :ref:`Tokudb_PROMOTION_H1_ROOTS_INJECTED_INTO`
-     -
-     -
-   * - :ref:`Tokudb_PROMOTION_INJECTIONS_AT_DEPTH_0`
-     -
-     -
-   * - :ref:`Tokudb_PROMOTION_INJECTIONS_AT_DEPTH_1`
-     -
-     -
-   * - :ref:`Tokudb_PROMOTION_INJECTIONS_AT_DEPTH_2`
-     -
-     -
-   * - :ref:`Tokudb_PROMOTION_INJECTIONS_AT_DEPTH_3`
-     -
-     -
-   * - :ref:`Tokudb_PROMOTION_INJECTIONS_LOWER_THAN_DEPTH_3`
-     -
-     -
-   * - :ref:`Tokudb_PROMOTION_STOPPED_NONEMPTY_BUFFER`
-     -
-     -
-   * - :ref:`Tokudb_PROMOTION_STOPPED_AT_HEIGHT_1`
-     -
-     -
-   * - :ref:`Tokudb_PROMOTION_STOPPED_CHILD_LOCKED_OR_NOT_IN_MEMORY`
-     -
-     -
-   * - :ref:`Tokudb_PROMOTION_STOPPED_CHILD_NOT_FULLY_IN_MEMORY`
-     -
-     -
-   * - :ref:`Tokudb_PROMOTION_STOPPED_AFTER_LOCKING_CHILD`
-     -
-     -
-   * - :ref:`Tokudb_BASEMENT_DESERIALIZATION_FIXED_KEY`
-     -
-     -
-   * - :ref:`Tokudb_BASEMENT_DESERIALIZATION_VARIABLE_KEY`
-     -
-     -
-   * - :ref:`Tokudb_PRO_RIGHTMOST_LEAF_SHORTCUT_SUCCESS`
-     -
-     -
-   * - :ref:`Tokudb_PRO_RIGHTMOST_LEAF_SHORTCUT_FAIL_POS`
-     -
-     -
-   * - :ref:`Tokudb_RIGHTMOST_LEAF_SHORTCUT_FAIL_REACTIVE`
-     -
-     -
-   * - :ref:`Tokudb_CURSOR_SKIP_DELETED_LEAF_ENTRY`
-     -
-     -
-   * - :ref:`Tokudb_FLUSHER_CLEANER_TOTAL_NODES`
-     -
-     -
-   * - :ref:`Tokudb_FLUSHER_CLEANER_H1_NODES`
-     -
-     -
-   * - :ref:`Tokudb_FLUSHER_CLEANER_HGT1_NODES`
-     -
-     -
-   * - :ref:`Tokudb_FLUSHER_CLEANER_EMPTY_NODES`
-     -
-     -
-   * - :ref:`Tokudb_FLUSHER_CLEANER_NODES_DIRTIED`
-     -
-     -
-   * - :ref:`Tokudb_FLUSHER_CLEANER_MAX_BUFFER_SIZE`
-     -
-     -
-   * - :ref:`Tokudb_FLUSHER_CLEANER_MIN_BUFFER_SIZE`
-     -
-     -
-   * - :ref:`Tokudb_FLUSHER_CLEANER_TOTAL_BUFFER_SIZE`
-     -
-     -
-   * - :ref:`Tokudb_FLUSHER_CLEANER_MAX_BUFFER_WORKDONE`
-     -
-     -
-   * - :ref:`Tokudb_FLUSHER_CLEANER_MIN_BUFFER_WORKDONE`
-     -
-     -
-   * - :ref:`Tokudb_FLUSHER_CLEANER_TOTAL_BUFFER_WORKDONE`
-     -
-     -
-   * - :ref:`Tokudb_FLUSHER_CLEANER_NUM_LEAF_MERGES_STARTED`
-     -
-     -
-   * - :ref:`Tokudb_FLUSHER_CLEANER_NUM_LEAF_MERGES_RUNNING`
-     -
-     -
-   * - :ref:`Tokudb_FLUSHER_CLEANER_NUM_LEAF_MERGES_COMPLETED`
-     -
-     -
-   * - :ref:`Tokudb_FLUSHER_CLEANER_NUM_DIRTIED_FOR_LEAF_MERGE`
-     -
-     -
-   * - :ref:`Tokudb_FLUSHER_FLUSH_TOTAL`
-     -
-     -
-   * - :ref:`Tokudb_FLUSHER_FLUSH_IN_MEMORY`
-     -
-     -
-   * - :ref:`Tokudb_FLUSHER_FLUSH_NEEDED_IO`
-     -
-     -
-   * - :ref:`Tokudb_FLUSHER_FLUSH_CASCADES`
-     -
-     -
-   * - :ref:`Tokudb_FLUSHER_FLUSH_CASCADES_1`
-     -
-     -
-   * - :ref:`Tokudb_FLUSHER_FLUSH_CASCADES_2`
-     -
-     -
-   * - :ref:`Tokudb_FLUSHER_FLUSH_CASCADES_3`
-     -
-     -
-   * - :ref:`Tokudb_FLUSHER_FLUSH_CASCADES_4`
-     -
-     -
-   * - :ref:`Tokudb_FLUSHER_FLUSH_CASCADES_5`
-     -
-     -
-   * - :ref:`Tokudb_FLUSHER_FLUSH_CASCADES_GT_5`
-     -
-     -
-   * - :ref:`Tokudb_FLUSHER_SPLIT_LEAF`
-     -
-     -
-   * - :ref:`Tokudb_FLUSHER_SPLIT_NONLEAF`
-     -
-     -
-   * - :ref:`Tokudb_FLUSHER_MERGE_LEAF`
-     -
-     -
-   * - :ref:`Tokudb_FLUSHER_MERGE_NONLEAF`
-     -
-     -
-   * - :ref:`Tokudb_FLUSHER_BALANCE_LEAF`
-     -
-     -
-   * - :ref:`Tokudb_HOT_NUM_STARTED`
-     -
-     -
-   * - :ref:`Tokudb_HOT_NUM_COMPLETED`
-     -
-     -
-   * - :ref:`Tokudb_HOT_NUM_ABORTED`
-     -
-     -
-   * - :ref:`Tokudb_HOT_MAX_ROOT_FLUSH_COUNT`
-     -
-     -
-   * - :ref:`Tokudb_TXN_BEGIN`
-     -
-     -
-   * - :ref:`Tokudb_TXN_BEGIN_READ_ONLY`
-     -
-     -
-   * - :ref:`Tokudb_TXN_COMMITS`
-     -
-     -
-   * - :ref:`Tokudb_TXN_ABORTS`
-     -
-     -
-   * - :ref:`Tokudb_LOGGER_NEXT_LSN`
-     -
-     -
-   * - :ref:`Tokudb_LOGGER_WRITES`
-     -
-     -
-   * - :ref:`Tokudb_LOGGER_WRITES_BYTES`
-     -
-     -
-   * - :ref:`Tokudb_LOGGER_WRITES_UNCOMPRESSED_BYTES`
-     -
-     -
-   * - :ref:`Tokudb_LOGGER_WRITES_SECONDS`
-     -
-     -
-   * - :ref:`Tokudb_LOGGER_WAIT_LONG`
-     -
-     -
-   * - :ref:`Tokudb_LOADER_NUM_CREATED`
-     -
-     -
-   * - :ref:`Tokudb_LOADER_NUM_CURRENT`
-     -
-     -
-   * - :ref:`Tokudb_LOADER_NUM_MAX`
-     -
-     -
-   * - :ref:`Tokudb_MEMORY_MALLOC_COUNT`
-     -
-     -
-   * - :ref:`Tokudb_MEMORY_FREE_COUNT`
-     -
-     -
-   * - :ref:`Tokudb_MEMORY_REALLOC_COUNT`
-     -
-     -
-   * - :ref:`Tokudb_MEMORY_MALLOC_FAIL`
-     -
-     -
-   * - :ref:`Tokudb_MEMORY_REALLOC_FAIL`
-     -
-     -
-   * - :ref:`Tokudb_MEMORY_REQUESTED`
-     -
-     -
-   * - :ref:`Tokudb_MEMORY_USED`
-     -
-     -
-   * - :ref:`Tokudb_MEMORY_FREED`
-     -
-     -
-   * - :ref:`Tokudb_MEMORY_MAX_REQUESTED_SIZE`
-     -
-     -
-   * - :ref:`Tokudb_MEMORY_LAST_FAILED_SIZE`
-     -
-     -
-   * - :ref:`Tokudb_MEM_ESTIMATED_MAXIMUM_MEMORY_FOOTPRINT`
-     -
-     -
-   * - :ref:`Tokudb_MEMORY_MALLOCATOR_VERSION`
-     -
-     -
-   * - :ref:`Tokudb_MEMORY_MMAP_THRESHOLD`
-     -
-     -
-   * - :ref:`Tokudb_FILESYSTEM_THREADS_BLOCKED_BY_FULL_DISK`
-     -
-     -
-   * - :ref:`Tokudb_FILESYSTEM_FSYNC_TIME`
-     -
-     -
-   * - :ref:`Tokudb_FILESYSTEM_FSYNC_NUM`
-     -
-     -
-   * - :ref:`Tokudb_FILESYSTEM_LONG_FSYNC_TIME`
-     -
-     -
-   * - :ref:`Tokudb_FILESYSTEM_LONG_FSYNC_NUM`
-     -
-     -
diff --git a/doc/source/ps-versions-comparison.rst b/doc/source/ps-versions-comparison.rst
deleted file mode 100644
index 6e864ab83081..000000000000
--- a/doc/source/ps-versions-comparison.rst
+++ /dev/null
@@ -1,124 +0,0 @@
-.. _ps_versions_comparison:
-
-========================================================
-List of features available in |Percona Server| releases
-========================================================
-
-.. tabularcolumns:: p{5cm}|p{5cm}|
-
-.. list-table::
-   :header-rows: 1
-
-   * - |Percona Server| 5.7
-     - |Percona Server| 8.0
-   * - Improved Buffer Pool Scalability
-     - Improved Buffer Pool Scalability
-   * - Improved InnoDB I/O Scalability
-     - Improved InnoDB I/O Scalability
-   * - Multiple Adaptive Hash Search Partitions
-     - Multiple Adaptive Hash Search Partitions
-   * - Atomic write support for Fusion-io devices
-     - Atomic write support for Fusion-io devices
-   * - Query Cache Enhancements
-     - |-implemented|
-   * - Improved NUMA support
-     - |-implemented|
-   * - Thread Pool 
-     - Thread Pool
-   * - Suppress Warning Messages
-     - Suppress Warning Messages
-   * - Ability to change database for mysqlbinlog
-     - Ability to change database for mysqlbinlog
-   * - Fixed Size for the Read Ahead Area
-     - Fixed Size for the Read Ahead Area
-   * - Improved MEMORY Storage Engine 
-     - Improved MEMORY Storage Engine 
-   * - Restricting the number of binlog files 
-     - Restricting the number of binlog files
-   * - Ignoring missing tables in mysqldump
-     - Ignoring missing tables in mysqldump
-   * - Too Many Connections Warning
-     - Too Many Connections Warning
-   * - Handle Corrupted Tables
-     - Handle Corrupted Tables
-   * - Lock-Free SHOW SLAVE STATUS
-     - Lock-Free SHOW REPLICA STATUS
-   * - Expanded Fast Index Creation
-     - Expanded Fast Index Creation
-   * - Percona Toolkit UDFs
-     - Percona Toolkit UDFs
-   * - Support for Fake Changes
-     - Support for Fake Changes
-   * - Kill Idle Transactions
-     - Kill Idle Transactions
-   * - XtraDB changed page tracking
-     - XtraDB changed page tracking
-   * - Enforcing Storage Engine
-     - |replaced|
-   * - Utility user
-     - Utility user
-   * - Extending the secure-file-priv server option
-     - Extending the secure-file-priv server option
-   * - Expanded Program Option Modifiers
-     - |-implemented|
-   * - PAM Authentication Plugin
-     - PAM Authentication Plugin
-   * - Log Archiving for XtraDB
-     - Log Archiving for XtraDB
-   * - User Statistics
-     - User Statistics
-   * - Slow Query Log
-     - Slow Query Log
-   * - Count InnoDB Deadlocks
-     - Count InnoDB Deadlocks
-   * - Log All Client Commands (syslog)
-     - Log All Client Commands (syslog)
-   * - Response Time Distribution
-     - |-implemented|
-   * - Show Storage Engines
-     - Show Storage Engines
-   * - Show Lock Names
-     - Show Lock Names
-   * - Process List
-     - Process List
-   * - Misc. INFORMATION_SCHEMA Tables
-     - Misc. INFORMATION_SCHEMA Tables
-   * - Extended Show Engine InnoDB Status
-     - Extended Show Engine InnoDB Status
-   * - Thread Based Profiling
-     - Thread Based Profiling
-   * - XtraDB Performance Improvements for I/O-Bound Highly-Concurrent Workloads
-     - XtraDB Performance Improvements for I/O-Bound Highly-Concurrent Workloads
-   * - Page cleaner thread tuning
-     - Page cleaner thread tuning
-   * - Statement Timeout
-     - Statement Timeout
-   * - Extended SELECT INTO OUTFILE/DUMPFILE
-     - Extended SELECT INTO OUTFILE/DUMPFILE
-   * - Per-query variable statement
-     - Per-query variable statement
-   * - Extended mysqlbinlog
-     - Extended mysqlbinlog
-   * - Slow Query Log Rotation and Expiration
-     - Slow Query Log Rotation and Expiration
-   * - Metrics for scalability measurement
-     - |-implemented|
-   * - Audit Log
-     - Audit Log
-   * - Backup Locks
-     - Backup Locks
-   * - CSV engine mode for standard-compliant quote and comma parsing
-     - CSV engine mode for standard-compliant quote and comma parsing
-   * - Super read-only
-     - Super read-only
-
-
-Other Reading
-=============
-
-* `What Is New in MySQL 5.7 <http://dev.mysql.com/doc/refman/5.7/en/mysql-nutshell.html>`_
-
-* `What Is New in MySQL 8.0 <http://dev.mysql.com/doc/refman/8.0/en/mysql-nutshell.html>`_
-
-.. |replaced| replace:: Replaced with upstream implementation
-.. |-implemented| replace:: Feature not implemented
diff --git a/doc/source/release-notes/8.0.29-21.rst b/doc/source/release-notes/8.0.29-21.rst
deleted file mode 100644
index c061f1e1cece..000000000000
--- a/doc/source/release-notes/8.0.29-21.rst
+++ /dev/null
@@ -1,55 +0,0 @@
-.. _8.0.29-21:
-
-================================================================================
-*Percona Server for MySQL* 8.0.29-21 (2022-08-08)
-================================================================================
-
-`Percona Server for MySQL <https://www.percona.com/software/mysql-database/percona-server>`_ 8.0.29-21
-includes all the features and bug fixes available in the
-`MySQL 8.0.29 Community Edition <https://dev.mysql.com/doc/relnotes/mysql/8.0/en/news-8-0-29.html>`__
-in addition to enterprise-grade features developed by Percona.
-
-.. include:: ../_res/rn/ps-mysql-blurb.txt
-
-.. contents::
-   :local:
-
-Release Highlights
-=================================================
-
-Improvements and bug fixes introduced by Oracle for *MySQL* 8.0.29 and included in Percona Server for MySQL are the following:
-
-* The Performance Schema tracks if a query was processed on the PRIMARY engine, InnoDB, or a SECONDARY engine, HeatWave. An EXECUTION_ENGINE column, which indicates the engine used, was added to the Performance Schema statement event tables and the `sys.processlist` and the `sys.x$processlist` views.
-* Added support for the `IF NOT EXISTS` option for the `CREATE FUNCTION`, `CREATE PROCEDURE`, and `CREATE TRIGGER` statements.
-* Added support for `ALTER TABLE ... DROP COLUMN ALGORITHM=INSTANT`. 
-* An anonymous user with the `PROCESS` privilege was unable to select `processlist` table rows.
-
-Find the full list of bug fixes and changes in the `MySQL 8.0.29 Release Notes <https://dev.mysql.com/doc/relnotes/mysql/8.0/en/news-8-0-29.html>`__.
-
-.. note::
-    
-    Percona Server for MySQL has changed the default for `supported DDL column operations <https://dev.mysql.com/doc/refman/8.0/en/innodb-online-ddl-operations.html>`__ to `ALGORITHM=INPLACE`. This fixes the corruption issue with the INSTANT ADD/DROP COLUMNS (find more details in `PS-8292 <https://jira.percona.com/browse/PS-8292>`__.) 
-
-    
-    In MySQL 8.0.29, the default setting for supported DDL operations is `ALGORITHM=INSTANT`. You can explicitly specify `ALGORITHM=INSTANT` in DDL column operations.
-
-Improvements
-=================================================
-
-* :jirabug:`PS-8258`: **Percona Server for MySQL** can be built on the MacOS with RocksDB enabled.
-
-Bugs fixed
-=================================================
-
-* :jirabug:`PS-8291`: An unexpected MySQL 8.0.29 server exit when executing `ALTER TABLE ... DROP COLUMN ALGORITHM=INSTANT`. (Upstream :mysqlbug:`107613`)
-* :jirabug:`PS-8292`: MySQL 8.0.29 failed to perform crash recovery.
-* :jirabug:`PS-8303`: A MySQL 8.0.29 server exit on `ALTER TABLE` created an assertion failure: `dict0mem.h:2498:pos < n_def`.
-* :jirabug:`PS-8116`: Executing `ALTER TABLE IMPORT TABLESPACE` with a different data directory failed. (Thanks to Sami Ahlroos for reporting this issue)
-* :jirabug:`PS-8273`: A MyRocks exit when inserting into a table with a unique key and TTL setting.
-
-Packaging Notes
-====================================================
-
-Debian 9 is no longer supported.
-
-.. include:: ../_res/rn/useful-links.txt
diff --git a/doc/source/release-notes/Percona-Server-8.0.12-2rc1.rst b/doc/source/release-notes/Percona-Server-8.0.12-2rc1.rst
deleted file mode 100644
index 95be076341fe..000000000000
--- a/doc/source/release-notes/Percona-Server-8.0.12-2rc1.rst
+++ /dev/null
@@ -1,96 +0,0 @@
-.. _8.0.12-2rc1:
-
-================================================================================
-*Percona Server for MySQL* 8.0.12-2rc1
-================================================================================
-
-Following the `alpha release announced earlier
-<https://www.percona.com/blog/2018/09/27/announcement-alpha-build-of-percona-server-8-0/>`_,
-Percona announces the release candidate of |Percona Server| |release| on
-October 31, 2018. Download the latest version from the Percona web site or the
-Percona Software Repositories.
-
-This release is based on |MySQL| 8.0.12 and includes all bug fixes in it. It is
-a *Release Candidate* quality release and it is not intended for
-production. If you want a high quality, Generally Available release, use the
-current Stable version (the most recent stable release at the time of writing in
-the 5.7 series is 5.7.23-23).
-
-Percona provides completely open-source and free software.
-
-Installation
-================================================================================
-
-As this is a release candidate, installation is performed by enabling the
-testing repository and installing the software via your package manager.  For
-Debian based distributions, see `apt installation instructions
-<https://www.percona.com/doc/percona-server/8.0/installation/apt_repo.html>`_;
-for RPM based distributions. see `yum installation instructions
-<https://www.percona.com/doc/percona-server/8.0/installation/yum_repo.html>`_.
-Note that in both cases after installing the current percona-release package,
-you’ll need to enable the testing repository in order to install |Percona Server|
-for MySQL |release|.  For manual installations, you can download from the
-`testing repository directly through our website
-<https://www.percona.com/downloads/TESTING/Percona-Server-80-rc1/>`_.
-
-New Features
-================================================================================
-
-- :psbug:`4550`: Native Partitioning support for MyRocks storage engine
-- :psbug:`3911`: Native Partitioning support for TokuDB storage engine
-- :psbug:`4946`: Add an option to prevent implicit creation of column family in
-  MyRocks
-- :psbug:`4839`: Better default configuration for MyRocks and TokuDB
-- InnoDB changed page tracking has been rewritten to account for redo logging
-  changes in MySQL 8.0.11.  This fixes fast incremental backups for PS 8.0
-- :psbug:`4434`: TokuDB ROW_FORMAT clause has been removed, compression may be
-  set by using the session variable ``tokudb_row_format`` instead.
-
-Improvements
-================================================================================
-
-- Several packaging changes to bring Percona packages more in line with
-  upstream, including split repositories. As you\’ll note from our instructions
-  above we now ship a tool with our release packages to help manage this.
-
-Bugs Fixed
-================================================================================
-
-- :psbug:`4785`: Setting version_suffix to **NULL** could lead to
-  *handle_fatal_signal* (sig=11) in *Sys_var_version::global_value_ptr*
-- :psbug:`4788`: Setting *log_slow_verbosity* and enabling the *slow_query_log*
-  could lead to a server crash
-- :psbug:`4937`: Any index comment generated a new column family in MyRocks
-- :psbug:`1107`: Binlog could be corrupted when *tmpdir* got full
-- :psbug:`1549`: Server side prepared statements lead to a potential
-  off-by-second timestamp on slaves
-- :psbug:`4937`: ``rocksdb_update_cf_options`` was useless when specified in
-  my.cnf or on command line.
-- :psbug:`4705`: The server could crash on snapshot size check in RocksDB
-- :psbug:`4791`: SQL injection on slave due to non-quoting in binlogged
-  ``ROLLBACK TO SAVEPOINT``
-- :psbug:`4953`: *rocksdb.truncate_table3* was unstable
-  
-Other bugs fixed: 
-
-- :psbug:`4811`: 5.7 Merge and fixup for old DB-937 introduces possible
-  regression
-- :psbug:`4885`: ``Using ALTER ... ROW_FORMAT=TOKUDB_QUICKLZ`` lead to InnoDB:
-  Assertion failure: ``ha_innodb.cc:12198:m_form->s->row_type ==
-  m_create_info->row_type``
-- Numerous testsuite failures/crashes
-
-Upcoming Features
-================================================================================
-
-- `New encryption features
-  <https://www.percona.com/doc/percona-server/8.0/management/data_at_rest_encryption.html>`_
-  in |Percona Server| 5.7 will be ported forward to |Percona Server| 8.0
-- Adding back in `column compression with custom data dictionaries
-  <https://www.percona.com/doc/percona-server/8.0/flexibility/compressed_columns.html>`_
-  and `expanded fast index creation
-  <expanded_innodb_fast_index_creation>`_.
-
-
-
-.. |release| replace:: 8.0.12-2rc1
diff --git a/doc/source/release-notes/Percona-Server-8.0.13-3.rst b/doc/source/release-notes/Percona-Server-8.0.13-3.rst
deleted file mode 100644
index 986579dc911b..000000000000
--- a/doc/source/release-notes/Percona-Server-8.0.13-3.rst
+++ /dev/null
@@ -1,122 +0,0 @@
-.. _8.0.13-3:
-
-================================================================================
-*Percona Server for MySQL* 8.0.13-3
-================================================================================
-
-|Percona| announces the GA release of |Percona Server| |release| on |date|
-(downloads are available `here
-<https://www.percona.com/downloads/Percona-Server-8.0/>`__ and from the `Percona
-SoftwareRepositories
-<https://www.percona.com/doc/percona-server/8.0/installation.html#installing-from-binaries>`__).
-This release merges changes of |MySQL| 8.0.13, including all the bug fixes in
-it. |Percona Server| |release| is now the current GA release in the 8.0
-series. All of |Percona|’s software is open-source and free.
-
-Percona Server for MySQL 8.0 includes all the `features available in MySQL 8.0
-Community Edition
-<https://dev.mysql.com/doc/refman/8.0/en/mysql-nutshell.html>`__ in addition to
-enterprise-grade features developed by Percona.  For a list of
-highlighted features from both MySQL 8.0 and Percona Server for MySQL 8.0,
-please see the `GA release announcement
-<https://www.percona.com/blog/2018/12/21/announcing-general-availability-of-percona-server-for-mysql-8-0/>`__.
-
-.. note::
-
-   If you are upgrading from 5.7 to 8.0, please ensure that you read the
-   `upgrade guide
-   <https://www.percona.com/doc/percona-server/8.0/upgrading_guide.html>`__ and the
-   document `Changed in Percona Server for MySQL 8.0
-   <https://www.percona.com/doc/percona-server/8.0/changed_in_version.html>`__.
-
-Features Removed in Percona Server for MySQL 8.0
-================================================================================
-
-- Slow Query Log Rotation and Expiration: Not widely used, can be accomplished
-  using ``logrotate``
-- CSV engine mode for standard-compliant quote and comma parsing
-- Expanded program option modifiers
-- The ``ALL_O_DIRECT`` InnoDB flush method: it is not compatible with the
-  new redo logging implementation
-- ``XTRADB_RSEG`` table from ``INFORMATION_SCHEMA``
-- InnoDB memory size information from ``SHOW ENGINE INNODB STATUS;`` the
-  same information is available from Performance Schema memory summary
-  tables
-- Query cache enhancements: The query cache is no longer present in
-  MySQL 8.0
-
-Features Being Deprecated in Percona Server for MySQL 8.0
-================================================================================
-
-- |TokuDB| Storage Engine: |TokuDB| will be supported throughout the |Percona
-  Server| 8.0 release series, but will not be available in the next major
-  release. |Percona| encourages |TokuDB| users to explore the |MyRocks| Storage
-  Engine which provides similar benefits for the majority of workloads and has
-  better optimized support for modern hardware.
-
-Issues Resolved in |Percona Server| |release|
-================================================================================
-
-Improvements
---------------------------------------------------------------------------------
-
--  :psbug:`5014`: Update Percona Backup Locks feature to use the new ``BACKUP_ADMIN``
-   privilege in MySQL 8.0
--  :psbug:`4805`: Re-Implemented Compressed Columns with Dictionaries feature in PS 8.0
--  :psbug:`4790`: Improved accuracy of User Statistics feature
-
-Bugs Fixed Since 8.0.12-rc1
---------------------------------------------------------------------------------
-
--  Fixed a crash in ``mysqldump`` in the ``--innodb-optimize-keys``
-   functionality :psbug:`4972`
--  Fixed a crash that can occur when system tables are locked by the
-   user due to a ``lock_wait_timeout`` :psbug:`5134`
--  Fixed a crash that can occur when system tables are locked by the
-   user from a ``SELECT FOR UPDATE`` statement :psbug:`5027`
--  Fixed a bug that caused ``innodb_buffer_pool_size`` to be
-   uninitialized after a restart if it was set using ``SET PERSIST`` :psbug:`5069`
--  Fixed a crash in TokuDB that can occur when a temporary table
-   experiences an autoincrement rollover :psbug:`5056`
--  Fixed a bug where marking an index as invisible would cause a table
-   rebuild in TokuDB and also in MyRocks :psbug:`5031`
--  Fixed a bug where audit logs could get corrupted if the
-   ``audit_log_rotations`` was changed during runtime. :psbug:`4950`
--  Fixed a bug where ``LOCK INSTANCE FOR BACKUP`` and
-   ``STOP SLAVE SQL_THREAD`` would cause replication to be blocked and
-   unable to be restarted. :psbug:`4758` (Upstream :mysqlbug:`93649`)
-
-Other Bugs Fixed:
-
-:psbug:`5155`, :psbug:`5139`, :psbug:`5057`, :psbug:`5049`, :psbug:`4999`, :psbug:`4971`,
-:psbug:`4943`, :psbug:`4918`, :psbug:`4917`, :psbug:`4898`, and :psbug:`4744`.
-
-Known Issues
-================================================================================
-
-We have a few features and issues outstanding that should be resolved in the
-next release.
-
-Pending Feature Re-Implementations and Improvements
---------------------------------------------------------------------------------
-
--  :psbug:`4892`: Re-Implement Expanded Fast Index Creation feature.
--  :psbug:`5216`: Re-Implement Utility User feature.
--  :psbug:`5143`: Identify Percona features which can make use of dynamic privileges instead of ``SUPER``
-
-Notable Issues in Features
---------------------------------------------------------------------------------
-
--  :psbug:`5148`: Regression in Compressed Columns Feature when using ``innodb-force-recovery``
--  :psbug:`4996`: Regression in User Statistics feature where ``TOTAL_CONNECTIONS`` field report incorrect data
--  :psbug:`4933`: Regression in  Slow Query Logging Extensions feature where incorrect transaction idaccounting can cause an assert during certain DDLs.
--  :psbug:`5206`: TokuDB: A crash can occur in TokuDB when using Native Partioning and the optimizer has ``index_merge_union`` enabled. Workaround by using ``SET SESSION optimizer_switch="index_merge_union=off";``
--  :psbug:`5174`: MyRocks: Attempting to use unsupported features against MyRocks can lead to a crash rather than an error.
--  :psbug:`5024`: MyRocks: Queries can return the wrong results on tables with no primary key, non-unique ``CHAR``/``VARCHAR`` rows, and ``UTF8MB4`` charset.
--  :psbug:`5045`: MyRocks: Altering a column or table comment cause the table to be rebuilt
-
-Find the release notes for Percona Server for MySQL 8.0.13-3 in our online documentation. Report bugs in the Jira bug tracker.
-
-.. |release| replace:: 8.0.13-3
-.. |date| replace:: December 21, 2018
-		       
diff --git a/doc/source/release-notes/Percona-Server-8.0.13-4.rst b/doc/source/release-notes/Percona-Server-8.0.13-4.rst
deleted file mode 100644
index 109c6554f95f..000000000000
--- a/doc/source/release-notes/Percona-Server-8.0.13-4.rst
+++ /dev/null
@@ -1,68 +0,0 @@
-.. _8.0.13-4:
-
-================================================================================
-*Percona Server for MySQL* 8.0.13-4
-================================================================================
-
-|Percona| announces the release of |Percona Server| |release| on
-|date| (downloads are available `here
-<https://www.percona.com/downloads/Percona-Server-8.0/>`__ and from
-the `Percona Software Repositories
-<https://www.percona.com/doc/percona-server/8.0/installation.html#installing-from-binaries>`__).
-This release contains a fix for a critical bug that prevented |Percona
-Server| 5.7.24-26 from being upgraded to version 8.0.13-3 if there
-were more than around 1000 tables, or if the maximum allocated InnoDB
-table ID was around 1000. |Percona Server| |release| is now the
-current GA release in the 8.0 series. All of |Percona|’s software is
-open-source and free.
-
-Percona Server for MySQL 8.0 includes all the `features available in MySQL 8.0
-Community Edition
-<https://dev.mysql.com/doc/refman/8.0/en/mysql-nutshell.html>`__ in addition to
-enterprise-grade features developed by Percona.  For a list of
-highlighted features from both MySQL 8.0 and Percona Server for MySQL 8.0,
-please see the `GA release announcement
-<https://www.percona.com/blog/2018/12/21/announcing-general-availability-of-percona-server-for-mysql-8-0/>`__.
-
-.. note::
-
-   If you are upgrading from 5.7 to 8.0, please ensure that you read the
-   `upgrade guide
-   <https://www.percona.com/doc/percona-server/8.0/upgrading_guide.html>`__ and the
-   document `Changed in Percona Server for MySQL 8.0
-   <https://www.percona.com/doc/percona-server/8.0/changed_in_version.html>`__.
-
-
-Bugs Fixed
-================================================================================
-
-- It was not possible to upgrade from MySQL 5.7.24-26 to 8.0.13-3 if
-  there were more than around 1000 tables, or if the maximum allocated
-  InnoDB table ID was around 1000. Bug fixed
-  :psbug:`5245`.
-- ``SHOW BINLOG EVENTS FROM <bad offset>`` is not diagnosed inside
-  ``Format_description_log_events``. Bug fixed :psbug:`5126` (Upstream
-  :mysqlbug:`93544`).
-- There was a typo in `mysqld_safe.sh`: **trottling** was replaced with
-  **throttling**. Bug fixed :psbug:`240`. Thanks to Michael Coburn for the patch.
-- |Percona Server| 8.0 could crash with the "Assertion failure:
-  dict0dict.cc:7451:space_id != SPACE_UNKNOWN" exception during an
-  upgrade from |Percona Server| 5.7.23 to |Percona Server| 8.0.13-3
-  with ``--innodb_file_per_table=OFF``. Bug fixed :psbug:`5222`.
-- On Debian or Ubuntu, a conflict was reported on the
-  :file:`/usr/bin/innochecksum` file when attempting to install |Percona Server| 8
-  over the |MySQL| 8. Bug fixed :psbug:`5225`.
-- An out-of-bound read exception could occur on debug builds in the compressed
-  columns with dictionaries feature. Bug fixed :psbug:`5311`:.
-- The ``innodb_data_pending_reads`` server status variable contained an
-  incorrect value. Bug fixed :psbug:`5264`:. Thanks to Fangxin Lou for the patch.
-- A memory leak and needless allocation in compression dictionaries
-   could happen in ``mysqldump``. Bug fixed :psbug:`5307`.
-- A compression-related memory leak could happen in ``mysqlbinlog``. Bug
-  fixed :psbug:`5308`:.
-
-Other bugs fixed: :psbug:`4797`:, :psbug:`5209`, :psbug:`5268`,
-:psbug:`5270`:, :psbug:`5306`, :psbug:`5309`:
-
-.. |release| replace:: 8.0.13-4
-.. |date| replace:: January 17, 2019
diff --git a/doc/source/release-notes/Percona-Server-8.0.14.rst b/doc/source/release-notes/Percona-Server-8.0.14.rst
deleted file mode 100644
index 393c61f1b338..000000000000
--- a/doc/source/release-notes/Percona-Server-8.0.14.rst
+++ /dev/null
@@ -1,30 +0,0 @@
-.. _8.0.14:
-
-================================================================================
-*Percona Server for MySQL* 8.0.14
-================================================================================
-
-Due to a critical fix, |mysql-cs| 8.0.15 was released shortly (11 days later)
-after |mysql-cs| 8.0.14. |Percona| has skipped the release of |Percona Server|
-|release|. The next release of |Percona Server| is :ref:`8.0.15-5` which contains
-all bug fixes and contents of both |mysql-cs| 8.0.14 and |mysql-cs| 8.0.15.
-
-|Percona Server| 8.0 includes all the `features available in MySQL 8.0 Community
-Edition <https://dev.mysql.com/doc/refman/8.0/en/mysql-nutshell.html>`__ in
-addition to enterprise-grade features developed by Percona.  For a list of
-highlighted features from both MySQL 8.0 and Percona Server for MySQL 8.0,
-please see the `GA release announcement
-<https://www.percona.com/blog/2018/12/21/announcing-general-availability-of-percona-server-for-mysql-8-0/>`__.
-
-
-.. note::
-
-   If you are upgrading from 5.7 to 8.0, please ensure that you read the
-   `upgrade guide
-   <https://www.percona.com/doc/percona-server/8.0/upgrading_guide.html>`__ and
-   the document `Changed in Percona Server for MySQL 8.0
-   <https://www.percona.com/doc/percona-server/8.0/changed_in_version.html>`__.
-
-
-.. |release| replace:: 8.0.14
-.. |mysql-cs| replace:: MySQL Community Server
diff --git a/doc/source/release-notes/Percona-Server-8.0.15-5.rst b/doc/source/release-notes/Percona-Server-8.0.15-5.rst
deleted file mode 100644
index 7c1a851ef2e1..000000000000
--- a/doc/source/release-notes/Percona-Server-8.0.15-5.rst
+++ /dev/null
@@ -1,90 +0,0 @@
-.. _8.0.15-5:
-
-================================================================================
-*Percona Server for MySQL* 8.0.15-5
-================================================================================
-
-|Percona| announces the release of |Percona Server| |release| on |date|
-(downloads are available `here
-<https://www.percona.com/downloads/Percona-Server-8.0/>`__ and from the `Percona
-Software Repositories
-<https://www.percona.com/doc/percona-server/8.0/installation.html#installing-from-binaries>`__).
-
-This release includes fixes to bugs found in previous releases of |Percona
-Server| 8.0.
-
-.. admonition:: Incompatible changes
-
-   In previous releases, the audit log used to produce time stamps
-   inconsistent with the ISO 8601 standard. Release |release| of
-   |Percona Server| solves this problem. This change, however, may
-   break programs that rely on the old time stamp format.
-
-.. include:: ../.res/text/encrypt_binlog.removing.txt
-
-This release is based on |MySQL| 8.0.14 and 8.0.15. It includes all
-bug fixes in these releases. |Percona Server| :ref:`8.0.14` was skipped.
-
-|Percona Server| |release| is now the current GA release in the 8.0
-series. All of |Percona|’s software is open-source and free.
-
-Percona Server for MySQL 8.0 includes all the `features available in MySQL 8.0
-Community Edition
-<https://dev.mysql.com/doc/refman/8.0/en/mysql-nutshell.html>`__ in addition to
-enterprise-grade features developed by Percona.  For a list of highlighted
-features from both MySQL 8.0 and Percona Server for MySQL 8.0, please see the
-`GA release announcement
-<https://www.percona.com/blog/2018/12/21/announcing-general-availability-of-percona-server-for-mysql-8-0/>`__.
-
-.. note::
-
-   If you are upgrading from 5.7 to 8.0, please ensure that you read the
-   `upgrade guide
-   <https://www.percona.com/doc/percona-server/8.0/upgrading_guide.html>`__ and
-   the document `Changed in Percona Server for MySQL 8.0
-   <https://www.percona.com/doc/percona-server/8.0/changed_in_version.html>`__.
-
-Bugs Fixed
-================================================================================
-
-- The audit log produced time stamps inconsistent with the ISO8601 standard. Bug
-  fixed :psbug:`226`.
-- FLUSH commands written to the binary log could cause errors in case of
-  replication. Bug fixed :psbug:`1827` (upstream :mysqlbug:`88720`).
-- When `audit_plugin` was enabled, the server could use a lot of memory when
-  handling large queries.  Bug fixed :psbug:`5395`.
-- The page cleaner could sleep for long time when the system clock was adjusted
-  to an earlier point in time. Bug fixed :psbug:`5221` (upstream :mysqlbug:`93708`).
-- In some cases, the MyRocks storage engine could crash without triggering
-  the crash recovery. Bug fixed :psbug:`5366`.
-- In some cases, when it failed to read from a file, InnoDB did not inform the
-  name of the file in the related error message. Bug fixed :psbug:`2455`
-  (upstream :mysqlbug:`76020`).
-- The ``ACCESS_DENIED`` field of the ``information_schema.user_statistics``
-  table was not updated correctly. Bugs fixed :psbug:`3956`, :psbug:`4996`.
-- ``MyRocks`` could crash while running ``START TRANSACTION WITH
-  CONSISTENT SNAPSHOT`` if other transactions were in specific states. Bug fixed
-  :psbug:`4705`.
-- In some cases, the server using the the ``MyRocks`` storage engine could
-  crash when TTL (Time to Live) was defined on a table. Bug fixed :psbug:`4911`.
-- MyRocks incorrectly processed transactions in which multiple statements
-  had to be rolled back. Bug fixed :psbug:`5219`.
-- A stack buffer overrun could happen if the redo log encryption with
-  key rotation was enabled. Bug fixed :psbug:`5305`.
-- The TokuDB storage engine would assert on load when used with jemalloc 5.x. Bug fixed :psbug:`5406`.
-
-Other bugs fixed:
-:psbug:`4106`,
-:psbug:`4107`,
-:psbug:`4108`,
-:psbug:`4121`,
-:psbug:`4474`,
-:psbug:`4640`,
-:psbug:`5055`,
-:psbug:`5218`,
-:psbug:`5328`,
-:psbug:`5369`.
-
-
-.. |release| replace:: 8.0.15-5
-.. |date| replace:: March 15, 2019
diff --git a/doc/source/release-notes/Percona-Server-8.0.15-6.rst b/doc/source/release-notes/Percona-Server-8.0.15-6.rst
deleted file mode 100644
index d9fdf12f29e5..000000000000
--- a/doc/source/release-notes/Percona-Server-8.0.15-6.rst
+++ /dev/null
@@ -1,156 +0,0 @@
-.. _8.0.15-6:
-
-================================================================================
-*Percona Server for MySQL* 8.0.15-6
-================================================================================
-
-|Percona| announces the release of |Percona Server| |release| on |date|
-(downloads are available `here
-<https://www.percona.com/downloads/Percona-Server-8.0/>`__ and from the `Percona
-Software Repositories
-<https://www.percona.com/doc/percona-server/8.0/installation.html#installing-from-binaries>`__).
-
-This release includes fixes to bugs found in previous releases of |Percona
-Server| 8.0.
-
-|Percona Server| |release| is now the current GA release in the 8.0
-series. All of |Percona|’s software is open-source and free.
-
-Percona Server for MySQL 8.0 includes all the `features available in MySQL 8.0
-Community Edition
-<https://dev.mysql.com/doc/refman/8.0/en/mysql-nutshell.html>`__ in addition to
-enterprise-grade features developed by Percona.  For a list of highlighted
-features from both MySQL 8.0 and Percona Server for MySQL 8.0, please see the
-`GA release announcement
-<https://www.percona.com/blog/2018/12/21/announcing-general-availability-of-percona-server-for-mysql-8-0/>`__.
-
-.. note::
-
-   If you are upgrading from 5.7 to 8.0, please ensure that you read the
-   `upgrade guide
-   <https://www.percona.com/doc/percona-server/8.0/upgrading_guide.html>`__ and
-   the document `Changed in Percona Server for MySQL 8.0
-   <https://www.percona.com/doc/percona-server/8.0/changed_in_version.html>`__.
-
-New Features
-================================================================================
-
-- The server part of MyRocks cross-engine consistent physical backups has been
-  implemented by introducing :ref:`rocksdb_disable_file_deletions` and
-  :ref:`rocksdb_create_temporary_checkpoint` session variables. These
-  variables are intended to be used by backup tools. Prolonged use or
-  other misuse can have serious side effects to the server instance.
-
-- RocksDB WAL file information can now be seen in the
-  :ref:`performance_schema.log_status` :ref:`table <log_status>`.
-
-- New :ref:`Audit_log_buffer_size_overflow` status variable has been
-  implemented to track when an :ref:`audit_log_plugin` entry was either
-  dropped or written directly to the file due to its size being bigger
-  than :ref:`audit_log_buffer_size` variable.
-
-
-Bugs Fixed
-================================================================================
-
-- TokuDB and MyRocks native partitioning handler objects were allocated from a
-  wrong memory allocator. Memory was released only on shutdown and concurrent
-  access to global memory allocator caused memory corruptions and therefore
-  crashes. Bug fixed :psbug:`5508`.
-
-- using TokuDB or MyRocks native partitioning and ``index_merge`` could lead to
-  a server crash. Bugs fixed :psbug:`5206`, :psbug:`5562`.
-
-- upgrade from |Percona Server| 5.7.24 to :ref:`8.0.13-3` wasn't working with
-  encrypted undo tablespaces. Bug fixed :psbug:`5223`.
-
-- `keyring_vault_plugin` couldn't be initialized on *Ubuntu Cosmic 17.10*.
-  Bug fixed :psbug:`5453`.
-
-- rotated key encryption did not register ``encryption_key_id`` as a valid
-  table option. Bug fixed :psbug:`5482`.
-
-- :ref:`INFORMATION_SCHEMA.GLOBAL_TEMPORARY_TABLES` queries could crash if
-  online ``ALTER TABLE`` was running in parallel. Bug fixed :psbug:`5566`.
-
-- setting the :ref:`log_slow_verbosity` to include ``innodb`` value and
-  enabling the :ref:`slow_query_log` could lead to a server crash.
-  Bug fixed :psbug:`4933`.
-
-- :ref:`compression_dictionary` operations were not allowed under
-  :ref:`innodb-force-recovery`. Now they work correctly when
-  :ref:`innodb_force_recovery` is <= ``2``, and are forbidden when
-  :ref:`innodb_force_recovery` is >= ``3``.
-  Bug fixed :psbug:`5148`.
-
-- ``BLOB`` entries in the binary log could become corrupted
-  in case when a database with ``Blackhole`` tables served as an
-  intermediate binary log server in a replication chain. Bug fixed
-  :psbug:`5353`.
-
-- ``FLUSH CHANGED_PAGE_BITMAPS`` would leave gaps between the last written
-  bitmap LSN and the |InnoDB| checkpoint LSN. Bug fixed :psbug:`5446`.
-
-- :ref:`changed_page_tracking` was missing pages changed by the in-place DDL.
-  Bug fixed :psbug:`5447`.
-
-- ``innodb_system`` tablespace information was missing from the
-  :ref:`INFORMATION_SCHEMA.innodb_tablespaces` view.
-  Bug fixed :psbug:`5473`.
-
-- undo log tablespace encryption status is now available through
-  :ref:`INFORMATION_SCHEMA.innodb_tablespaces` view.
-  Bug fixed :psbug:`5485` (upstream :mysqlbug:`94665`).
-
-- enabling temporay tablespace encryption didn't mark the
-  ``innodb_temporary`` tablespace with the encryption flag. Bug fixed
-  :psbug:`5490`.
-
-- server would crash during bootstrap if :ref:`innodb_encrypt_tables`
-  was set to ``1``. Bug fixed :psbug:`5492`.
-
-- fixed intermittent shutdown crashes that were happening if :ref:`threadpool`
-  was enabled. Bug fixed :psbug:`5510`.
-
-- compression dictionary ``INFORMATION_SCHEMA`` views were missing when `datadir` was upgraded from 8.0.13 to 8.0.15. Bug fixed :psbug:`5529`.
-
-- :ref:`innodb_encrypt_tables` variable accepted ``FORCE`` option only
-  as a string. Bug fixed :psbug:`5538`.
-
-- ``ibd2sdi`` utility was missing in Debian/Ubuntu packages. Bug fixed
-  :psbug:`5549`.
-
-- Docker image is now ignoring password that is set in the configuration
-  file when first initializing. Bug fixed :psbug:`5573`.
-
-- long running ``ALTER TABLE ADD INDEX`` could cause a ``semaphore wait > 600``
-  assertion. Bug fixed :psbug:`3410` (upstream :mysqlbug:`82940`).
-
-- system keyring keys initialization wasn't thread safe. Bugs fixed
-  :psbug:`5554`.
-
-- :ref:`backup_locks` was blocking DML for RocksDB. Bug fixed :psbug:`5583`.
-
-- PerconaFT ``locktree`` library was re-licensed to Apache v2 license.
-  Bug fixed :psbug:`5501`.
-
-Other bugs fixed:
-:psbug:`5243`,
-:psbug:`5484`,
-:psbug:`5512`,
-:psbug:`5523`,
-:psbug:`5536`,
-:psbug:`5550`,
-:psbug:`5570`,
-:psbug:`5578`,
-:psbug:`5441`,
-:psbug:`5442`,
-:psbug:`5456`,
-:psbug:`5462`,
-:psbug:`5487`,
-:psbug:`5489`,
-:psbug:`5520`, and
-:psbug:`5560`.
-
-.. |release| replace:: 8.0.15-6
-.. |date| replace:: May 07, 2019
diff --git a/doc/source/release-notes/Percona-Server-8.0.16-7.rst b/doc/source/release-notes/Percona-Server-8.0.16-7.rst
deleted file mode 100644
index 303e6326e7c9..000000000000
--- a/doc/source/release-notes/Percona-Server-8.0.16-7.rst
+++ /dev/null
@@ -1,115 +0,0 @@
-.. _8.0.16-7:
-
-===============================================================================
-*Percona Server for MySQL* 8.0.16-7
-===============================================================================
-
-|Percona| announces the release of |Percona Server| |release| on |date|
-(downloads are available `here
-<https://www.percona.com/downloads/Percona-Server-8.0/>`__ and from the `Percona
-Software Repositories
-<https://www.percona.com/doc/percona-server/8.0/installation.html#installing-from-binaries>`__).
-This release includes fixes to bugs found in previous releases of |Percona
-Server| 8.0.
-|Percona Server| |release| is now the current GA release in the 8.0
-series. All of |Percona|’s software is open-source and free.
-
-Percona Server for MySQL 8.0 includes all the `features and bug fixes available in MySQL 8.0.16
-Community Edition
-<https://dev.mysql.com/doc/relnotes/mysql/8.0/en/news-8-0-16.html>`__ in addition to
-enterprise-grade features developed by Percona.
-
-Encryption Features General Availability (GA)
-===============================================================================
-
-- :ref:`encrypting-temporary-files`
-- :ref:`undo-tablespace-encryption`
-- :ref:`encrypting-system-tablespace`
-- :ref:`default_table_encryption` =OFF/ON
-- :refref:`table_encryption_privilege_check` =OFF/ON
-- :ref:`encrypting-redo-log` for master key encryption only
-- :ref:`merge-sort-encryption`
-- :ref:`encrypting-doublewrite-buffers`
-
-Bugs Fixed
-===============================================================================
-
-- Parallel doublewrite buffer writes must crash the server on an I/O error occurs. Bug fixed :psbug:`5678`.
-
-- After resetting the :ref:`innodb_temp_tablespace_encrypt` to ``OFF`` during runtime the subsequent file-per-table temporary tables continue to be encrypted. Bug fixed :psbug:`5734`.
-
-- Setting the encryption to ``ON`` for the system tablespace generates an encryption key and encrypts system temporary tablespace pages. Resetting the encryption to ``OFF``, all subsequent pages are written to the temporary tablespace without encryption. To allow any encrypted tables to be decrypted, the generated keys are not erased. Modifying the :ref:`innodb_temp_tablespace_encrypt` does not affect file-per-table temporary tables. This type of table is encrypted if ``ENCRYPTION`` ='Y' is set during table creation. Bug fixed :psbug:`5736`.
-
-- An instance started with the default values but setting the redo-log without specifying the keyring plugin parameters does not fail or throw an error. Bug fixed :psbug:`5476`.
-
-- The :ref:`rocksdb_large_prefix` allows index key prefixes up to 3072 bytes. The default value is changed to ``TRUE`` to match the behavior of the :ref:`innodb_large_prefix`. :psbug:`5655`.
-
-- On a server with a large number of tables, a shutdown may take a measurable length of time. Bug fixed :psbug:`5639`.
-
-- The changed page tracking uses the LOG flag during read operations. The redo log encryption may attempt to decrypt pages with a specific bit set and fail. This failure generates error messages. A NO_ENCRYPTION flag lets the read process safely disable decryption errors in this case. Bug fixed :psbug:`5541`.
-
-- If large pages are enabled on MySQL side, the maximum size for :ref:`innodb_buffer_pool_chunk_size` is effectively limited to 4GB. Bug fixed :psbug:`5517`. (Upstream `94747 <https://bugs.mysql.com/bug.php?id=94747>`__)
-
-- The TokuDB hot backup library continually dumps TRACE information to the server error log. The user cannot enable or disable the dump of this information. Bug fixed :psbug:`4850`.
-
-
-
-Other bugs fixed:
-:psbug:`5688`,
-:psbug:`5723`,
-:psbug:`5695`,
-:psbug:`5749`,
-:psbug:`5752`,
-:psbug:`5610`,
-:psbug:`5689`,
-:psbug:`5645`,
-:psbug:`5734`,
-:psbug:`5772`,
-:psbug:`5753`,
-:psbug:`5129`,
-:psbug:`5102`,
-:psbug:`5681`,
-:psbug:`5686`,
-:psbug:`5681`,
-:psbug:`5310`,
-:psbug:`5713`,
-:psbug:`5007`,
-:psbug:`5102`,
-:psbug:`5129`,
-:psbug:`5130`,
-:psbug:`5149`,
-:psbug:`5696`,
-:psbug:`3845`,
-:psbug:`5149`,
-:psbug:`5581`,
-:psbug:`5652`,
-:psbug:`5662`,
-:psbug:`5697`,
-:psbug:`5775`,
-:psbug:`5668`,
-:psbug:`5752`,
-:psbug:`5782`,
-:psbug:`5767`,
-:psbug:`5669`,
-:psbug:`5753`,
-:psbug:`5696`,
-:psbug:`5803`,
-:psbug:`5804`,
-:psbug:`5820`,
-:psbug:`5827`,
-:psbug:`5835`,
-:psbug:`5724`,
-:psbug:`5767`,
-:psbug:`5782`,
-:psbug:`5794`,
-:psbug:`5796`,
-:psbug:`5746` and,
-:psbug:`5748`.
-
-Known Issues
-==============================================================================
-
-- :psbug:`5865`: |Percona Server| |release| does not support encryption for the MyRocks storage engine. An attempt to move any table from InnoDB to `MyRocks <https://www.percona.com/doc/percona-server/LATEST/myrocks/limitations.html>`__ fails as MyRocks currently sees all InnoDB tables as being encrypted.
-
-.. |release| replace:: 8.0.16-7
-.. |date| replace:: August 15, 2019
diff --git a/doc/source/release-notes/Percona-Server-8.0.17-8.rst b/doc/source/release-notes/Percona-Server-8.0.17-8.rst
deleted file mode 100644
index 1a55183a43e4..000000000000
--- a/doc/source/release-notes/Percona-Server-8.0.17-8.rst
+++ /dev/null
@@ -1,85 +0,0 @@
-.. _8.0.17-8:
-
-================================================================================
-*Percona Server for MySQL* 8.0.17-8
-================================================================================
-
-|Percona| announces the release of |Percona Server| |release| on |date|
-(downloads are available `here
-<https://www.percona.com/downloads/Percona-Server-8.0/>`__ and from the
-`Percona Software Repositories
-<https://www.percona.com/doc/percona-server/8.0/installation.html#installing-from-binaries>`__).
-
-This release includes fixes to bugs found in previous releases of |Percona
-Server| 8.0.
-
-|Percona Server| |release| is now the current GA release in the 8.0 series. All
-of |Percona|’s software is open-source and free.
-
-Percona Server for MySQL 8.0 includes all the `features available in MySQL
-8.0.17 Community Edition
-<https://dev.mysql.com/doc/relnotes/mysql/8.0/en/news-8-0-17.html>`__ in
-addition to enterprise-grade features developed by Percona.
-
-New Features
-================================================================================
-
-|Percona Server| has implemented the ability to have a |MySQL|
-:ref:`psaas_utility_user` who has system access to do administrative tasks but limited
-access to user schemas. The user is invisible to other users. This feature is
-especially useful to those who are operating |MySQL| as a Service. This feature
-has the same functionality as the utility user in earlier versions and has been
-delay-ported to version 8.0.
-
-|Percona Server| has implemented `data masking <https://www.percona.com/doc/percona-server/8.0/security/data-masking.html>`__ . 
-
-Bugs Fixed
-================================================================================
-
-- Changed the default of :ref:`innodb_empty_free_list_algorithm` to
-  ``backoff``. Bugs fixed :psbug:`5881`
-
-- When the Adaptive Hash Index (AHI) was enabled or disabled, there was an AHI
-  overhead during DDL operations. Bugs fixed :psbug:`5747`.
-
-- An upgrade to :ref:`8.0.16-7` with encrypted tablespace fails on
-  :ref:`innodb_dynamic_metadata`. Bugs fixed :psbug:`5874`.
-
-- The ``rocksdb.ttl_primary`` test case sometimes fails. Bugs fixed
-  :psbug:`5722` (Louis Hust)
-
-- The ``rocksdb.ns_snapshot_read_committed`` test case sometimes fails. Bugs
-  fixed :psbug:`5798` (Louis Hust).
-
-- During a binlogging replication event, if the master crashes after the
-  multi-threaded slave has begun copying to the slave's relay log and before the
-  process has completed, a ``STOP SLAVE`` on the slave takes longer than expected.
-  Bugs fixed :psbug:`5824`.
-
-- The purpose of the `sql_require_primary_key
-  <https://dev.mysql.com/doc/refman/8.0/en/server-system-variables.html#sysvar_sql_require_primary_key>`__
-  option is to avoid replication performance issues. Temporary tables are not
-  replicated. The option cannot be used with temporary tables. Bugs fixed
-  :psbug:`5931`.
-
-- When using ``skip-innodb_doublewrite`` in my.cnf, a parallel doublewrite
-  buffer is still created. Bugs fixed :psbug:`3411`.
-
-- The metadata for every InnoDB table contains encryption information, either a
-  'Y' or an 'N' value based on the ENCRYPTION clause or the
-  :ref:`default_table_encryption` value. You are unable to switch the storage
-  engine from InnoDB to MyRocks because MyRocks does not support the ENCRYPTION
-  clause. Bugs fixed :psbug:`5865`.
-
-- MyRocks does not allow index condition pushdown optimization for specific data
-  types, such as ``varchar``.  Bugs fixed :psbug:`5024`.
-
-Other bugs fixed: :psbug:`5880`, :psbug:`5838`, :psbug:`5682`,
-:psbug:`5979`, :psbug:`5793`, :psbug:`6020`, :psbug:`5327`,
-:psbug:`5839`, :psbug:`5933`, :psbug:`5939`, :psbug:`5659`, :psbug:`5924`,
-:psbug:`5926`, :psbug:`5925`, :psbug:`5875`, :psbug:`5533`,
-:psbug:`5867`, :psbug:`5864`, :psbug:`5760`, :psbug:`5909`, :psbug:`5985`,
-:psbug:`5941`, :psbug:`5954`, :psbug:`5790`, and :psbug:`5593`.
-
-.. |release| replace:: 8.0.17-8
-.. |date| replace:: October 30, 2019
diff --git a/doc/source/release-notes/Percona-Server-8.0.18-9.rst b/doc/source/release-notes/Percona-Server-8.0.18-9.rst
deleted file mode 100644
index e9aa798b2612..000000000000
--- a/doc/source/release-notes/Percona-Server-8.0.18-9.rst
+++ /dev/null
@@ -1,65 +0,0 @@
-.. _8.0.18-9:
-
-================================================================================
-*Percona Server for MySQL* 8.0.18-9
-================================================================================
-
-|Percona| announces the release of |Percona Server| |release| on |date| (downloads are available `here <https://www.percona.com/downloads/Percona-Server-8.0/>`__ and from the `Percona Software Repositories <https://www.percona.com/doc/percona-server/8.0/installation.html#installing-from-binaries>`__).
-
-This release includes fixes to bugs found in previous releases of |Percona
-Server| 8.0.
-
-|Percona Server| |release| is now the current GA release in the 8.0 series. All
-of |Percona|’s software is open-source and free.
-
-Percona Server for MySQL 8.0 includes all the `features available in MySQL
-8.0.18 Community Edition
-<https://dev.mysql.com/doc/relnotes/mysql/8.0/en/news-8-0-18.html>`__ in
-addition to enterprise-grade features developed by Percona.
-
-Bugs Fixed
-================================================================================
-
-- Setting the ``none`` value for :ref:`slow_query_log_use_global_control`
-  generates an error. Bugs fixed :psbug:`5813`.
-
-- If `pam_krb5
-  <https://docs.oracle.com/cd/E88353_01/html/E37853/pam-krb5-7.html>`__ allows the
-  user to change their password, and the password expired, a new password may
-  cause a server exit. Bug fixed :psbug:`6023`.
-
-- An incorrect assertion was triggered if any temporary tables should be logged
-  to binlog. This event may cause a server exit. Bug fixed :psbug:`5181`.
-
-- The Handler failed to trigger on Error 1049, SQLSTATE 42000, or plain
-  sqlexception. Bug fixed :psbug:`6094`. (Upstream :mysqlbug:`97682`)
-
-- When executing ``SHOW GLOBAL STATUS``, the variables may return incorrect
-  values. Bug fixed :psbug:`5966`.
-
-- The memory storage engine detected an incorrect ``full`` condition even 
-  though the space contained reusable memory chunks released by deleted
-  records and the space could be reused. Bug fixed :psbug:`1469`.
-
-Other bugs fixed:
-
-:psbug:`6051`,
-:psbug:`5876`,
-:psbug:`5996`,
-:psbug:`6021`,
-:psbug:`6052`,
-:psbug:`4775`,
-:psbug:`5836` (Upstream :mysqlbug:`96449`),
-:psbug:`6123`,
-:psbug:`5819`,
-:psbug:`5836`,
-:psbug:`6054`,
-:psbug:`6056`,
-:psbug:`6058`,
-:psbug:`6078`,
-:psbug:`6057`,
-:psbug:`6111`, and
-:psbug:`6073`.
-
-.. |release| replace:: 8.0.18-9
-.. |date| replace:: December 11, 2019
diff --git a/doc/source/release-notes/Percona-Server-8.0.19-10.rst b/doc/source/release-notes/Percona-Server-8.0.19-10.rst
deleted file mode 100644
index 12dad0ce6524..000000000000
--- a/doc/source/release-notes/Percona-Server-8.0.19-10.rst
+++ /dev/null
@@ -1,66 +0,0 @@
-.. _8.0.19-10:
-
-================================================================================
-*Percona Server for MySQL* 8.0.19-10
-================================================================================
-
-:Date: March 23, 2020
-
-:Installation: `Installing Percona Server for MySQL <https://www.percona.com/doc/percona-server/8.0/installation.html>`_
-
-`Percona Server for MySQL <https://www.percona.com/software/mysql-database/percona-server>`_ 8.0.19-10
-includes all the features and bug fixes available in
-`MySQL 8.0.19 Community Edition <https://dev.mysql.com/doc/relnotes/mysql/8.0/en/news-8-0-19.html>`_
-in addition to enterprise-grade features developed by Percona.
-
-New Features
-================================================================================
-
-* :jirabug:`PS-5729`: Added server's UUID to Percona system keys.
-* :jirabug:`PS-5917`: Added Simplified LDAP authentication plugin.
-* :jirabug:`PS-4464`: Exposed the last global transaction identifier (GTID) executed for a CONSISTENT SNAPSHOT.
-
-
-
-Improvements
-================================================================================
-
-* :jirabug:`PS-6775`: Removed the KEYRING_ON option from :ref:`default_table_encryption`.
-* :jirabug:`PS-6733`: Added binary search to the Data masking plugin.
-
-
-
-Bugs Fixed
-================================================================================
-
-* :jirabug:`PS-6811`: Service failed to start asserting ACL_PROXY_USER::check_validity if --skip-name-resolve=1 and there is a Proxy user. (Upstream :mysqlbug:`98908`)
-* :jirabug:`PS-6112`: Inconsistent Binlog_snapshot_gtid when mysqldump was used with --single-transaction.
-* :jirabug:`PS-5923`: "SELECT ... INTO var_name FOR UPDATE" was not working in MySQL 8.0. (Upstream :mysqlbug:`96677`)
-* :jirabug:`PS-6150`: The execution of SHOW ENGINE INNODB STATUS to show locked mutexes could cause a server exit.
-* :jirabug:`PS-5379`: Slow startup after an upgrade from MySQL 5.7 to MySQL 8. (Upstream :mysqlbug:`96340`)
-* :jirabug:`PS-6750`: The installation of client packages could cause a file conflict in Red Hat Enterprise Linux 8.
-* :jirabug:`PS-5675`: Concurrent INSERT ... ON DUPLICATE KEY UPDATE statements could cause a failure with a unique index violation. (Upstream :mysqlbug:`96578`)
-* :jirabug:`PS-6857`: New package naming broke dbdeployer.
-* :jirabug:`PS-6767`: The execution of a stored function in a WHERE clause was skipped. (Upstream :mysqlbug:`98160`)
-* :jirabug:`PS-5421`: MyRocks: Corrected documentation for :ref:`rocksdb_db_write_buffer_size`.
-* :jirabug:`PS-6761`: MacOS error in threadpool_unix.cc: there was no matching member function for call to 'compare_exchange_weak'.
-* :jirabug:`PS-6900`: The test big-test required re-recording after explicit_encryption was re-added.
-* :jirabug:`PS-6897`: The main.udf_myisam test and main.transactional_acl_tables test failed on trunk.
-* :jirabug:`PS-6106`: ALTER TABLE without ENCRYPTION clause caused tables to be encrypted.
-* :jirabug:`PS-6093`: The execution of SHOW ENGINE INNODB STATUS to show locked mutexes with simultaneous access to a compressed table could cause a server exit.
-* :jirabug:`PS-5552`: Assertion 'm_idx >= 0' failed in plan_idx QEP_share d::idx() const. (Upstream :mysqlbug:`98258`)
-* :jirabug:`PS-6899`: The tests, main.events_bugs and main.events_1, failed because 2020-01-01 was considered a future time. (Upstream :mysqlbug:`98860`)
-* :jirabug:`PS-6881`: Documented that mysql 8.0 does not require mysql_upgrade.
-* :jirabug:`PS-6796`: The test, percona_changed_page_bmp_shutdown_thread, was unstable.
-* :jirabug:`PS-6773`: A conditional jump or move depended on uninitialized value(s) in sha256_password_authenticate. (Upstream :mysqlbug:`98223`)
-* :jirabug:`PS-6125`: MyRocks: To set :ref:`rocksdb_update_cf_options` with a nonexistent column family created a partially-defined column family which could cause a server exit.
-* :jirabug:`PS-6037`: When Extra Packages Enterprise Linux (EPEL) 8 repo was enabled on CentOS/RHEL 8, jemalloc v5 was installed.
-* :jirabug:`PS-5956`: Root session could kill :ref:`psaas_utility_user` session.
-* :jirabug:`PS-5952`: :ref:`psaas_utility_user` was visible in performance_schema.threads.
-* :jirabug:`PS-5843`: A memory leak could occur after "group_replication.gr_majority_loss_restart". (Upstream :mysqlbug:`96471`)
-* :jirabug:`PS-5642`: The page tracker thread did not exit if the startup failed.
-* :jirabug:`PS-5325`: A conditional jump or move depended on uninitialized value on innodb_zip.wl5522_zip or innodb.alter_missing_tablespace.
-* :jirabug:`PS-4678`: MyRocks: Documented the generated columns limitation.
-* :jirabug:`PS-4649`: TokuDB: Documented PerconaFT (fractal tree indexing).
-
-
diff --git a/doc/source/release-notes/Percona-Server-8.0.20-11.rst b/doc/source/release-notes/Percona-Server-8.0.20-11.rst
deleted file mode 100644
index beff5f023df3..000000000000
--- a/doc/source/release-notes/Percona-Server-8.0.20-11.rst
+++ /dev/null
@@ -1,72 +0,0 @@
-.. _8.0.20-11:
-
-================================================================================
-*Percona Server for MySQL* 8.0.20-11
-================================================================================
-
-:Date: July 21, 2020
-:Installation: `Installing Percona Server for MySQL <https://www.percona.com/doc/percona-server/8.0/installation.html>`_
-
-`Percona Server for MySQL <https://www.percona.com/software/mysql-database/percona-server>`_ 8.0.20-11
-includes all the features and bug fixes available in
-`MySQL 8.0.20 Community Edition <https://dev.mysql.com/doc/relnotes/mysql/8.0/en/news-8-0-20.html>`_
-in addition to enterprise-grade features developed by Percona.
-
-As of 8.0.20-11, the Percona Parallel Doublewrite buffer implementation has been removed and has been replaced with the Oracle MySQL implementation.
-
-New Features
-================================================================================
-
-* :jirabug:`PS-7128`: Add RocksDB variables: :ref:`rocksdb_max_background_compactions`, :ref:`rocksdb_max_background_flushes`, and :ref:`rocksdb_max_bottom_pri_background_compactions`
-* :jirabug:`PS-7039`: Add RocksDB variable: :ref:`rocksdb_validate_tables`
-* :jirabug:`PS-6951`: Add RocksDB variables: :ref:`rocksdb_delete_cf`, :ref:`rocksdb_enable_iterate_bounds`, and :ref:`rocksdb_enable_remove_orphaned_dropped_cfs`
-* :jirabug:`PS-6926`: Add RocksDB variables: :ref:`rocksdb_table_stats_recalc_threshold_pct`, :ref:`rocksdb_table_stats_recalc_threshold_count`, :ref:`rocksdb_table_stats_background_thread_nice_value`, :ref:`rocksdb_table_stats_max_num_rows_scanned`, :ref:`rocksdb_table_stats_use_table_scan`.
-* :jirabug:`PS-6910`: Add RocksDB variable: :ref:`rocksdb_stats_level`.
-* :jirabug:`PS-6902`: Add RocksDB variable: :ref:`rocksdb_enable_insert_with_update_caching`.
-* :jirabug:`PS-6901`: Add RocksDB variable: :ref:`rocksdb_read_free_rpl`.
-* :jirabug:`PS-6891`: Add RocksDB variable: :ref:`rocksdb_master_skip_tx_api`.
-* :jirabug:`PS-6890`: Add RocksDB variable: :ref:`rocksdb_blind_delete_primary_key`.
-* :jirabug:`PS-6886`: Add RocksDB variable: :ref:`rocksdb_cache_dump`.
-* :jirabug:`PS-6885`: Add RocksDB variable: :ref:`rocksdb_rollback_on_timeout`.
-
-
-
-Improvements
-================================================================================
-
-* :jirabug:`PS-6994`: Implement rocksdb_validate_tables functionality in Percona Server 8.X
-* :jirabug:`PS-6984`: Update the zstd submodule to v1.4.4.
-* :jirabug:`PS-5764`: Introduce SEQUENCE_TABLE() table-level SQL function
-
-
-
-Bugs Fixed
-================================================================================
-
-* :jirabug:`PS-7019`: Correct query results for LEFT JOIN with GROUP BY (Upstream :mysqlbug:`99398`)
-* :jirabug:`PS-6979`: Modify the processing to call clean up functions to remove CREATE USER statement from the processlist after the statement has completed (Upstream :mysqlbug:`99200`)
-* :jirabug:`PS-6860`: Merge innodb_buffer_pool_pages_LRU_flushed into buf_get_total_stat()
-* :jirabug:`PS-7038`: Set innodb-parallel-read_threads=1 to prevent kill process from hanging (Thanks to user wavelet123 for reporting this issue)
-* :jirabug:`PS-6945`: Correct tokubackup plugin process exported API to allow large file backups. (Thanks to user prohaska7 for reporting this issue)
-* :jirabug:`PS-7000`: Fix newer collations for proper space padding in MyRocks
-* :jirabug:`PS-6991`: Modify package to include missing development files (Thanks to user larrabee for reporting this issue)
-* :jirabug:`PS-6946`: Correct tokubackup processing to free memory use from the address and thread sanitizers (Thanks to user prohaska7 for reporting this issue)
-* :jirabug:`PS-5893`: Add support for running multiple instances with systemD on Debian. (Thanks to user sasha for reporting this issue)
-* :jirabug:`PS-5620`: Modify Docker image to support supplying custom TLS certificates (Thanks to user agarner for reporting this issue)
-* :jirabug:`PS-7168`: Determine if file per tablespace using table flags to prevent assertion
-* :jirabug:`PS-7161`: Fixed 'CreateTempFile' gunit test to support both 'HAVE_O_TMPFILE'-style
-* :jirabug:`PS-7142`: Set 'KEYRING_VAULT_PLUGIN_OPT' value when required
-* :jirabug:`PS-7138`: Correct file reference for ps-admin broken in tar.gz package
-* :jirabug:`PS-7127`: Provide mechanism to grant dynamic privilege to the utility user.
-* :jirabug:`PS-7118`: Add ability to set LOWER_CASE_TABLE_NAMES option before initializing data directory
-* :jirabug:`PS-7116`: Port MyRocks fix of Index Condition Pushdown (ICP)
-* :jirabug:`PS-7075`: Provide binary tarball with shared libs and glibc suffix
-* :jirabug:`PS-6974`: Correct instability in the rocksdb.drop_cf_* tests
-* :jirabug:`PS-6969`: Correct instability in the rocksdb.index_stats_large_table
-* :jirabug:`PS-6105`: Modify innodb.mysqld_core_dump_without_buffer_pool_dynamic test to move assertion to correct location
-* :jirabug:`PS-5735`: Correct package to install the charsets on CentOS 7
-* :jirabug:`PS-4757`: Remove CHECK_IF_CURL_DEPENDS_ON_RTMP to build keyring_vault for unconditional test
-* :jirabug:`PS-7131`: Improve resume_encryption_cond conditional variable handling to avoid missed signals
-* :jirabug:`PS-7100`: Fix rocksdb_read_free_rpl test to properly count rows corresponding to broken index entries
-* :jirabug:`PS-7082`: Correct link displayed on \help client command
-* :jirabug:`PS-7169`: Set rocksdb_validate_tables to disabled RocksDB while upgrading the server from 5.7 to 8.0.20
\ No newline at end of file
diff --git a/doc/source/release-notes/Percona-Server-8.0.21-12.rst b/doc/source/release-notes/Percona-Server-8.0.21-12.rst
deleted file mode 100644
index 70b7631e3ddc..000000000000
--- a/doc/source/release-notes/Percona-Server-8.0.21-12.rst
+++ /dev/null
@@ -1,73 +0,0 @@
-.. _8.0.21-12:
-
-================================================================================
-*Percona Server for MySQL* 8.0.21-12
-================================================================================
-
-:Date: October 13, 2020
-:Installation: `Installing Percona Server for MySQL <https://www.percona.com/doc/percona-server/8.0/installation.html>`_
-
-`Percona Server for MySQL <https://www.percona.com/software/mysql-database/percona-server>`_ 8.0.21-12
-includes all the features and bug fixes available in
-`MySQL 8.0.21 Community Edition <https://dev.mysql.com/doc/relnotes/mysql/8.0/en/news-8-0-21.html>`_
-in addition to enterprise-grade features developed by Percona.
-
-This release fixes the security vulnerability `CVE-2020-26542 <https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-26542>`_.
-
-Improvements
-================================================================================
-
-* :jirabug:`PS-7132`: Make default value of rocksdb_wal_recovery_mode compatible with InnoDB
-* :jirabug:`PS-7245`: Block enable/disable redo log with lock tables for backup
-* :jirabug:`PS-5730`: Change SELECT rotate_system_key to ALTER INSTANCE for percona system key rotation.
-* :jirabug:`PS-7297`: Modify MTR test to prevent proxy_protocol_admin_port test failure on 8.0.21
-* :jirabug:`PS-7114`: Enhance crash artifacts (core dumps and stack traces) to provide additional information to the operator
-* :jirabug:`PS-5635`: Introduce crypt_schema 2 for better error checking in encryption threads.
-
-
-
-Bugs Fixed
-================================================================================
-
-* :jirabug:`PS-7203`: Fix audit plugin memory leak on replicas when opening tables
-* :jirabug:`PS-6067`: Provide a fix for upstream bug #97001 in Percona Server (Upstream :mysqlbug:`97001`)
-* :jirabug:`PS-7325`: Modify SELECT to correct situation when data is missing from MyRocks table when GROUP BY is used
-* :jirabug:`PS-7275`: Add variable Innodb_checkpoint_max_age
-* :jirabug:`PS-7232`: Modified Multithreaded Replica to correct the exhausted slave_transaction_retries when replica has `slave_preserve_commit_order` enabled (Upstream :mysqlbug:`99440`)
-* :jirabug:`PS-7231`: Modify `Slave_transaction::retry_transaction()` to call `mysql_errno()` only when `thd->is_error()` is true
-* :jirabug:`PS-7221`: Modify get_int_sort_key_for_item_inline to return UTC string (Upstream :mysqlbug:`100402`)
-* :jirabug:`PS-7143`: Suppress deadlock check for ACL Cache MDL lock to prevent server freeze
-* :jirabug:`PS-7076`: Modify to not update Cardinality after setting tokudb_cardinality_scale_percent
-* :jirabug:`PS-7025`: Fix reading ahead of insert buffer pages by dispatching of buffered AIO transfers (Upstream :mysqlbug:`100086`)
-* :jirabug:`PS-7010`: Modify to Lock buffer blocks before sanity check in btr_cur_latch_leaves
-* :jirabug:`PS-6995`: Introduce a new optimizer switch to allow the user to reduce the cost of a range scan to determine best execution plan for Primary Key lookup
-* :jirabug:`PS-7279`: Modify to notify when BuildID: Not Available in case the server has been compiled with --build-id=none
-* :jirabug:`PS-7220`: Fix activity counter update in purge coordinator and workers
-* :jirabug:`PS-7169`: Set rocksdb_validate_tables to disabled RocksDB while upgrading the server from 5.7 to 8.0.20
-* :jirabug:`PS-5741`: Correct format for use of memset_s in keyring_vault
-* :jirabug:`PS-5323`: Align Keyring encryption with Master Key encryption
-* :jirabug:`PS-7363`: Modify to release locks on failure to prevent deadlock with LTFB + DROP UNDO TABLESPACE
-* :jirabug:`PS-7360`: Modify clang-4.0 compilation to correct failure from '-Winconsistent-missing-destructor-override'
-* :jirabug:`PS-7359`: Stabilize innodb.check_ibd_filesize_16k MTR test
-* :jirabug:`PS-7353`: Modify LDAP connection to server to be static to prevent connection failures which will lock mysqld
-* :jirabug:`PS-7352`: Correct typo in authentication_ldap_simple_ca_path to correct crash of mysqld
-* :jirabug:`PS-7340`: Add validation of default_table_encryption to confirm keyring plugin is loaded before changing modes
-* :jirabug:`PS-7338`: Set set crypt_data based on encryption status of destination table
-* :jirabug:`PS-7328`: Block create/alter/drop/undo truncation while backup lock is available and hold lock until operation is completed
-* :jirabug:`PS-7322`: Modify the right mask length calculation to handle up to string length for Data Masking
-* :jirabug:`PS-7321`: Correct Random Number Generator to create only 15 or 16 digit number in Data Masking
-* :jirabug:`PS-7309`: Modify gen_range() to support negative numbers in Data Masking
-* :jirabug:`PS-7308`: Modify limit gen_dictionary_load() to load files only from the secure-file-priv dir when secure-file-priv dir is set in Data Masking
-* :jirabug:`PS-7307`: Modify Data masking UDFs to display output using Latin1 character set
-* :jirabug:`PS-7296`: Fix online log tracking initialization to properly process existing bitmap files
-* :jirabug:`PS-7289`: Restrict innodb encryption threads to 255 and add min/max values
-* :jirabug:`PS-7270`: Fix admin_port to accept non-proxied connections when proxy_protocol_networks='*'
-* :jirabug:`PS-7234`: Modify PS minimal tarballs to remove COPYING.AGPLv3
-* :jirabug:`PS-7226`: Modify LDAP Plugin to enhance logging and test cases
-* :jirabug:`PS-7191`: Correct documentation for PS variable default_table_encryption
-* :jirabug:`PS-7147`: Modified Relay_log_info::cannot_safely_rollback() to handle null pointer
-* :jirabug:`PS-7140`: Correct processing to apply crypt redo logs
-* :jirabug:`PS-7120`: Handle doublewrite buffer encryption for keyring key tablespaces
-* :jirabug:`PS-7119`: Correct Tests of encryption.innodb_encryption_aborted_rotation* to prevent failure
-* :jirabug:`PS-6987`: Modify to allow value of default_table_encryption to be changed only when encryption_threads are off
-* :jirabug:`PS-7284`: Fix failing test innodb.percona_changed_page_bmp_requests_debug
diff --git a/doc/source/release-notes/Percona-Server-8.0.22-13.rst b/doc/source/release-notes/Percona-Server-8.0.22-13.rst
deleted file mode 100644
index d90c2ee18a87..000000000000
--- a/doc/source/release-notes/Percona-Server-8.0.22-13.rst
+++ /dev/null
@@ -1,39 +0,0 @@
-.. _8.0.22-13:
-
-================================================================================
-*Percona Server for MySQL* 8.0.22-13
-================================================================================
-
-:Date: December 14, 2020
-:Installation: `Installing Percona Server for MySQL <https://www.percona.com/doc/percona-server/8.0/installation.html>`_
-
-`Percona Server for MySQL <https://www.percona.com/software/mysql-database/percona-server>`_ 8.0.22-13
-includes all the features and bug fixes available in
-`MySQL 8.0.22 Community Edition <https://dev.mysql.com/doc/relnotes/mysql/8.0/en/news-8-0-22.html>`_
-in addition to enterprise-grade features developed by Percona.
-
-New Features
-================================================================================
-
-* :jirabug:`PS-7162`: Implement user-defined functions for Point-in-time Recovery in PXC operator
-
-
-
-Improvements
-================================================================================
-
-* :jirabug:`PS-7348`: Create a set of C++ classes/macros that would simplify the creation of new user-defined functions
-
-
-
-Bugs Fixed
-================================================================================
-
-* :jirabug:`PS-7346`: Correct the buffer calculation for the audit plugin used when large queries are executed(PS-5395).
-* :jirabug:`PS-7300`: Modify Session temporary tablespace truncation on connection disconnect to reduce high CPU usage (Upstream :mysqlbug:`98869`)
-* :jirabug:`PS-7304`: Correct package to include coredumper.a as a dependency of libperconaserverclient20-dev (Thanks to user Martin for reporting this issue)
-* :jirabug:`PS-7236`: Correct grouping by GROUP BY processing with timezone (Thanks to user larrabee for reporting this issue) (Upstream :mysqlbug:`101105`)
-* :jirabug:`PS-7286`: Modify to check for boundaries for encryption_key_id
-* :jirabug:`PS-7317`: Add explicit_default_counter=10000 to innodb.table_encrypt_* MTR tests
-
-
diff --git a/doc/source/release-notes/Percona-Server-8.0.23-14.rst b/doc/source/release-notes/Percona-Server-8.0.23-14.rst
deleted file mode 100644
index 709405756c47..000000000000
--- a/doc/source/release-notes/Percona-Server-8.0.23-14.rst
+++ /dev/null
@@ -1,63 +0,0 @@
-.. _8.0.23-14:
-
-================================================================================
-*Percona Server for MySQL* 8.0.23-14
-================================================================================
-
-:Date: May 12, 2021
-:Installation: `Installing Percona Server for MySQL <https://www.percona.com/doc/percona-server/8.0/installation.html>`_
-
-`Percona Server for MySQL <https://www.percona.com/software/mysql-database/percona-server>`_ 8.0.23-14
-includes all the features and bug fixes available in
-`MySQL 8.0.23 Community Edition <https://dev.mysql.com/doc/relnotes/mysql/8.0/en/news-8-0-23.html>`_
-in addition to enterprise-grade features developed by Percona.
-
-New Features
-================================================================================
-
-* :jirabug:`PS-7364`: The :ref:`net_buffer_length` status variable shows the buffer size of the current connection. Specify `SHOW GLOBAL` to see cumulative buffer size for all connections. For more information, see :ref:`adaptive_network_buffers`.
-* :jirabug:`PS-5364`: Update the keyring_vault plugin to support KV Secrets Engine Version 2 (kv-v2) (Thanks to Andrey Prokofyev for reporting this issue)
-* :jirabug:`PS-4894`: Users can add calculated/virtual columns + index for the MyRocks storage engine.
-* :jirabug:`PS-7125`: Users can reconfigure the TLS certificate at runtime and reload the certificate to the X Plugin (Upstream :mysqlbug:`99895`)
-* :jirabug:`PS-7442`: Add documentation for the MyRocks Information Schema Tables `ROCKSDB_ACTIVE_COMPACTION_STATS` and `ROCKSDB_COMPACTION_HISTORY`.
-* :jirabug:`PS-7441`: Add documentation for the RocksDB variable :ref:`rocksdb_max_compaction_history` and deprecated the :ref:`strict_collation_check` variable.
-* :jirabug:`PS-7049`: Update the SELinux profile and the AppArmor Policy, making these security features easier to implement for organizations.
-
-
-
-Improvements
-================================================================================
-
-* :jirabug:`PS-5846`: Add support for the `default value clause <https://dev.mysql.com/doc/refman/8.0/en/data-type-defaults.html>`__ for the MyRocks storage engine. (Thanks to user denji for reporting this issue)
-* :jirabug:`PS-6780`: Optimize support for collations other than `latin1/utf8` in MyRocks. This support allows MyRocks to reconstruct and return data directly from an index read.
-
-
-
-Bugs Fixed
-================================================================================
-
-* :jirabug:`PS-1956`: Update specific data types to 64-bit to make slow query logs more efficient.
-* :jirabug:`PS-7593`: If a transaction has executed, changing the tx-isolation level in a session is not honored and may cause service failure.
-* :jirabug:`PS-7578`: Fix the replication failure on Update when a replica server has a primary key and the source server does not.
-* :jirabug:`PS-7498`: Prevent the replication coordinator thread from being stuck due to the MASTER_DELAY while handling the partial relay log transactions. (Upstream :mysqlbug:`102647`)
-* :jirabug:`PS-7474`: ROCKSDB: Row not retrieved when using character sets that do not support Secondary Key index-only scans.
-* :jirabug:`PS-7618`: Added the libmysqlclient.so.21(libmysqlclient_21)(64bit) to the PS80 Repository(Thanks to user Mark Frost for reporting this issue).
-* :jirabug:`PS-7098`: MyRocks: ICP fails with character sets that do not support Secondary Key index-only scans, for example, utf8mb4. (Thanks to user denis for reporting this issue)
-* :jirabug:`PS-4497`: Incorrect option error message for mysqlbinlog.
-* :jirabug:`PS-7617`: In the Grant tables, the Timestamp column displays when the last change occurred to a user. In specific tables, the Timestamp column may be set to NULL. 
-* :jirabug:`PS-7566`: Correct version matching in RPM spec changelog for PS packages
-* :jirabug:`PS-7499`: Improve the error log when MyRocks fails with rocksdb_validate_tables=1
-* :jirabug:`PS-7495`: Block Tablespace DDL with LOCK TABLES FOR BACKUP (Upstream :mysqlbug:`102175`)
-* :jirabug:`PS-7291`: Run a variable value check when setting it with 'set persist_only'
-* :jirabug:`PS-7492`: Update slow log formatting for tmp tables related stats
-
-
-Known Issues 
-===============================================================================
-
-* :jirabug:`PS-7683`: If you are upgrading MyRocks from 8.0.22 to 8.0.23, you must run the following commands to add the ROCKSDB_COMPACTION_HISTORY and ROCKSDB_COMPACTION_STATS tables:
-
-    .. sourcecode:: mysql
-
-       INSTALL PLUGIN ROCKSDB_COMPACTION_HISTORY SONAME 'ha_rocksdb.so';
-       INSTALL PLUGIN ROCKSDB_COMPACTION_STATS SONAME 'ha_rocksdb.so';
\ No newline at end of file
diff --git a/doc/source/release-notes/Percona-Server-8.0.25-15.rst b/doc/source/release-notes/Percona-Server-8.0.25-15.rst
deleted file mode 100644
index a95e0154555b..000000000000
--- a/doc/source/release-notes/Percona-Server-8.0.25-15.rst
+++ /dev/null
@@ -1,61 +0,0 @@
-.. _8.0.25-15:
-
-================================================================================
-*Percona Server for MySQL* 8.0.25-15
-================================================================================
-
-:Date: July 13, 2021
-:Installation: `Installing Percona Server for MySQL <https://www.percona.com/doc/percona-server/8.0/installation.html>`_
-
-`Percona Server for MySQL <https://www.percona.com/software/mysql-database/percona-server>`_ 8.0.25-15
-includes all the features and bug fixes available in the
-`MySQL 8.0.24 Community Edition <https://dev.mysql.com/doc/relnotes/mysql/8.0/en/news-8-0-24.html>`__ and
-the
-`MySQL 8.0.25 Community Edition <https://dev.mysql.com/doc/relnotes/mysql/8.0/en/news-8-0-25.html>`_
-in addition to enterprise-grade features developed by Percona.
-
-.. note::
-
-    The TokuDB Storage Engine was `declared as deprecated <https://www.percona.com/doc/percona-server/8.0/release-notes/Percona-Server-8.0.13-3.html>`__ in Percona Server for MySQL 8.0 and will be disabled in upcoming 8.0 versions. 
-    
-    We recommend migrating to the MyRocks Storage Engine. 
-
-    For more information, see the Percona blog post: `Heads-Up: TokuDB Support Changes and Future Removal from Percona Server for MySQL 8.0 <https://www.percona.com/blog/2021/05/21/tokudb-support-changes-and-future-removal-from-percona-server-for-mysql-8-0/>`__.
-
-
-New Features
-================================================================================
-
-* :jirabug:`PS-7182`: Create functionality to expose defined data from procfs for agentless environment
-* :jirabug:`PS-7671`: Add rocksdb_allow_unsafe_alter to enable crash unsafe INPLACE ADD|DROP partition
-* :jirabug:`PS-7327`: INPLACE ADD|DROP partitions in MyRocks
-
-
-
-Improvements
-================================================================================
-
-* :jirabug:`PS-7366`: Add jemalloc memory allocation profiling on PS 8.0
-
-
-
-Bugs Fixed
-================================================================================
-
-* :jirabug:`PS-7722`: Multiple-Column Index using Column Prefix Key Parts fails with Index Condition Pushdown in MyRocks
-* :jirabug:`PS-7665`: The ``performance_schema.metadata_locks m_column_name_length`` is uninitialized for MDL_key::FOREIGN_KEY (Upstream :mysqlbug:`103532`)
-* :jirabug:`PS-7695`: The ``Boost`` download is no longer available. Using the -DDOWNLOAD_BOOST option with CMake (Thanks to user Benjamin Kuen for reporting this issue).
-* :jirabug:`PS-6802`: Configure fails with make-4.3 with CMake Error at storage/rocksdb/CMakeLists.txt:152 (STRING) (Thanks to user Thomas Deutschmann for reporting this issue).
-* :jirabug:`PS-7648`: Optimizer switch "favor_range_scan" is not documented
-* :jirabug:`PS-7595`: Same version upgrade from PS->PXC needs mysql_upgrade
-* :jirabug:`PS-7657`: A server exit caused with an update query on a partition table with a compressed column
-* :jirabug:`PS-7557`: Mysql server version 8.0.22-13 executing the Data Masking plugin causes a server exit (Thanks to user Alfonso Luciano for reporting this issue).
-* :jirabug:`PS-1116`: LP #1719506: Audit plugin reports "command_class=error" for server-side prepared statements.
-
-
-Known issues
-==========================================================================
-
-* :jirabug:`PS-7787`: Default values for the `procfs_files_spec` contains entries blocks by SELinux. 
-* :jirabug:`PS-7788`: Wildcard globbing in `procfs_files_spec` does not work.
-* :jirabug:`PS-7790`: ProcFS access boundary to `/proc` and `/sys` can be bypassed with `..`.
diff --git a/doc/source/release-notes/Percona-Server-8.0.26-16.rst b/doc/source/release-notes/Percona-Server-8.0.26-16.rst
deleted file mode 100644
index 6d2310b9c834..000000000000
--- a/doc/source/release-notes/Percona-Server-8.0.26-16.rst
+++ /dev/null
@@ -1,80 +0,0 @@
-.. _8.0.26-16:
-
-================================================================================
-*Percona Server for MySQL* 8.0.26-16
-================================================================================
-
-:Date: October 20, 2021
-:Installation: `Installing Percona Server for MySQL <https://www.percona.com/doc/percona-server/8.0/installation.html>`_
-
-`Percona Server for MySQL <https://www.percona.com/software/mysql-database/percona-server>`_ 8.0.26-16
-includes all the features and bug fixes available in the
-`MySQL 8.0.26 Community Edition <https://dev.mysql.com/doc/relnotes/mysql/8.0/en/news-8-0-26.html>`__.
-in addition to enterprise-grade features developed by Percona.
-
-Percona Server for MySQL® is a free, fully compatible, enhanced and open
-source drop-in replacement for any MySQL database. It provides superior
-performance, scalability and instrumentation.
-
-Percona Server for MySQL is trusted by thousands of enterprises to provide
-better performance and concurrency for their most demanding workloads, and
-delivers greater value to MySQL server users with optimized performance,
-greater performance scalability and availability, enhanced backups and
-increased visibility. `Commercial support contracts are available
-<https://www.percona.com/services/support/mysql-support>`__.
-
-Release Highlights
-=================================================
-
-We have integrated a ZenFS RocksDB plugin to Percona Server for MySQL. This
-plugin places files on a raw zoned block device (ZBD) using the MyRocks File
-System interface. For more information, see :ref:`zenfs`.
-
-The following list are some of the bug fixes for MySQL 8.0.26, provided by Oracle, and included in Percona Server for MySQL:
-
-* :mysqlbug:`104575`: In the PERFORMANCE_SCHEMA.Threads table, the ``srv_purge_thread`` and ``srv_worker_thread`` values are duplicated.
-* :mysqlbug:`104387`: When using REGEX comparison, a CHARACTER_SET_MISMATCH error is thrown.
-* :mysqlbug:`104576`: Accessing the second index in a partition table with many columns can create a high CPU load.
-
-Find the full list of bug fixes and changes in `MySQL 8.0.26 Release Notes <https://dev.mysql.com/doc/relnotes/mysql/8.0/en/news-8-0-26.html>`__.
-
-New Features
-=================================================
-
-* :jirabug:`PS-7757`: Integrate ZenFS RocksDB plugin into Percona Server
-* :jirabug:`PS-7777`: Document RocksDB variable ``rocksdb_manual_compaction_bottommost_level``.
-* :jirabug:`PS-7765`: Document RocksDB variable ``rocksdb_fault_injection_options``
-
-Deprecated Features
-=================================================
-
-The TokuDB Storage Engine was declared deprecated for Percona Server for MySQL. Starting with Percona Server 8.0.26-16, the plugins are available in the binary builds and packages but are disabled. The plugins will be removed from the binary builds and packages in a future version.
-
-New options have been added to enable the plugins if they are needed to migrate the data to another storage engine.
-
-The instructions on how to enable the plugins and more information are available at the beginning of each TokuDB topic.
-
-
-Improvements
-===============================================
-
-* :jirabug:`PS-7526`: Fix the unexpected quoting and dropping of comments in DROP TABLE commands
-* :jirabug:`PS-7706`: Add options to explicitly enable TokuDB and TokuDB Backup that are ``FALSE`` by default.
-
-
-Bugs Fixed
-===============================================
-
-* :jirabug:`PS-1344`: LP #1160436: Fix if the ``log_slow_statement`` is called unconditionally
-* :jirabug:`PS-1346`: LP #1163232: Fix an anomaly with the ``opt_log_slow_slave_statements``.
-* :jirabug:`PS-7500`: Fix the ``SELECT COUNT(*)`` is slow in MyRocks.
-* :jirabug:`PS-7742`: Fix when enabling binary log encryption breaks the basic replication setup on Percona Server for MySQL.
-* :jirabug:`PS-7746`: Fix for a possible double call to `free_share()` in ha_innobase::open()
-* :jirabug:`PS-7778`: Fix for denied commands when triggers with ``DEFINER`` are used.
-* :jirabug:`PS-1955`: LP #1088529: Update the ``log_slow_verbosity`` help text to add the missing the "minimal", "standard", and "full" options
-* :jirabug:`PS-2433`: LP #1234346: Include a timestamp in the slow query log file when initializing a new file
-* :jirabug:`PS-7790`: Fix that disallows certain roles the ability to bypass the ProcFS access boundary with `..` instead of ``/proc`` or ``/sys``.
-* :jirabug:`PS-7784`: Fix that reset the status variables ``procfs_access_violations`` and ``procfs_queries``
-* :jirabug:`PS-7785`: Fix that reset the default value for ``procfs_files_spec`` which had the same value.
-* :jirabug:`PS-7788`: Fix improves wildcard globbing in ``proc_files_spec``.
-* :jirabug:`PS-7917`: Fix for installing the TokuDB storage engine with ps-admin.
diff --git a/doc/source/release-notes/Percona-Server-8.0.26-17.rst b/doc/source/release-notes/Percona-Server-8.0.26-17.rst
deleted file mode 100644
index f397ca3d5592..000000000000
--- a/doc/source/release-notes/Percona-Server-8.0.26-17.rst
+++ /dev/null
@@ -1,73 +0,0 @@
-.. _8.0.26-17:
-
-================================================================================
-*Percona Server for MySQL* 8.0.26-17
-================================================================================
-
-:Date: January 26, 2022
-:Installation: `Installing Percona Server for MySQL <https://www.percona.com/doc/percona-server/8.0/installation.html>`_
-
-`Percona Server for MySQL <https://www.percona.com/software/mysql-database/percona-server>`_ 8.0.26-17
-includes all the features and bug fixes available in the
-`MySQL 8.0.26 Community Edition <https://dev.mysql.com/doc/relnotes/mysql/8.0/en/news-8-0-26.html>`__.
-in addition to enterprise-grade features developed by Percona.
-
-*Percona Server for MySQL* 8.0.26-17 is now the current GA release in the 8.0 series.
-
-Percona Server for MySQL® is a free, fully-compatible, enhanced, and open
-source drop-in replacement for any MySQL database. It provides superior
-performance, scalability, and instrumentation.
-
-Percona Server for MySQL is trusted by thousands of enterprises to provide
-better performance and concurrency for their most demanding workloads. It
-delivers a greater value to MySQL server users with optimized performance,
-greater performance scalability, and availability, enhanced backups and
-increased visibility. `Commercial support contracts are available
-<https://www.percona.com/services/support/mysql-support>`__.
-
-Release Highlights
-=================================================
-
-Percona integrates a ZenFS RocksDB plugin to Percona Server for MySQL. This
-plugin places files on a raw zoned block device (ZBD) using the MyRocks File
-System interface. Percona provides a binary release for `Debian 11.1 <https://www.debian.org/releases/bullseye/debian-installer/index>`__. `Other Linux distributions <https://zonedstorage.io/docs/distributions/linux/>`__ are adding support for ZenFS, but Percona does not offer installation packages for those distributions yet. The ``libzbd`` package is now linked statically to the RocksDB storage engine.
-
-The following dependency libraries are updated to newer versions:
-
-* ZenFS v1.0.0
-* libzbd v2.0.1
-
-For more information, see :ref:`zenfs`.
-
-The following list has a number of the bug fixes for MySQL 8.0.26, provided by Oracle, and included in Percona Server for MySQL:
-
-* :mysqlbug:`104575`: Fix for when, in the PERFORMANCE_SCHEMA.Threads table, the ``srv_purge_thread`` and ``srv_worker_thread`` values are duplicated.
-* :mysqlbug:`104387`: Fix for when using a REGEX comparison, a CHARACTER_SET_MISMATCH error is thrown.
-* :mysqlbug:`104576`: Fix for a high CPU load being created when accessing the second index in a partition table with many columns.
-
-Find the full list of bug fixes and changes in `MySQL 8.0.26 Release Notes <https://dev.mysql.com/doc/relnotes/mysql/8.0/en/news-8-0-26.html>`__.
-
-
-Deprecated Features
-=================================================
-
-The TokuDB Storage Engine was declared deprecated for Percona Server for MySQL. Starting with Percona Server 8.0.26-16, the plugins are available in binary builds and packages but are disabled. The plugins will be removed from the binary builds and packages in a future version.
-
-New options have been added to enable the plugins if they are needed to migrate the data to another storage engine.
-
-The instructions on enabling the plugins and more information are available at the beginning of each TokuDB topic in the Percona Server fo MySQL documenation.
-
-Bugs Fixed
-==================================================
-
-* The ``libzbd`` user library is statically linked into ``ha_rocksdb.so``. This linking allows the creation of a single binary package and requires the 5.9 kernel and higher.
-
-* Fix for ZenFS issues with ``sysbench`` using either Debian 11 or the latest ``libzbd`` user library.
-
-* Fix a sporadic [aborting on BG write error] assertion in rocksdb.bloomfilter3.
-
-* Fix when the ``WITH_ZENFS_UTILITY`` CMake option is set to ``ON``. Added logic to the RocksDB *CMakeLists.txt* to ensure the ``libgflags`` library is installed on the system.
-
-* Fix for the tests that rely on the ``du`` system utility. The ``du`` utility results must be converted to computations based on the ``zenfs`` list output.
-
-* Fix for the zenfs ``mkfs`` to allow the command to accept a pre-existing aux_path. 
diff --git a/doc/source/release-notes/Percona-Server-8.0.27-18.rst b/doc/source/release-notes/Percona-Server-8.0.27-18.rst
deleted file mode 100644
index 2e241efd860c..000000000000
--- a/doc/source/release-notes/Percona-Server-8.0.27-18.rst
+++ /dev/null
@@ -1,93 +0,0 @@
-.. _8.0.27-18:
-
-================================================================================
-*Percona Server for MySQL* 8.0.27-18
-================================================================================
-
-:Date: March 2, 2022
-:Installation: `Installing Percona Server for MySQL <https://www.percona.com/doc/percona-server/8.0/installation.html>`_
-
-`Percona Server for MySQL <https://www.percona.com/software/mysql-database/percona-server>`_ 8.0.27-18
-includes all the features and bug fixes available in the
-`MySQL 8.0.27 Community Edition <https://dev.mysql.com/doc/relnotes/mysql/8.0/en/news-8-0-27.html>`__.
-in addition to enterprise-grade features developed by Percona.
-
-*Percona Server for MySQL* is a free, fully compatible, enhanced and open
-source drop-in replacement for any *MySQL* database. It provides superior
-performance, scalability, and instrumentation.
-
-*Percona Server for MySQL* is trusted by thousands of enterprises to provide
-better performance and concurrency for their most demanding workloads, and
-delivers greater value to *MySQL* server users with optimized performance,
-greater performance scalability and availability, enhanced backups and
-increased visibility. `Commercial support contracts are available
-<https://www.percona.com/services/support/mysql-support>`__.
-
-.. contents::
-   :local:
-
-
-Release Highlights
-=================================================
-
-The following lists a number of the bug fixes for *MySQL* 8.0.27, provided by Oracle, and included in Percona Server for MySQL:
-
-* The ``default_authentication_plugin`` is deprecated. Support for this plugin may be removed in future versions. Use the ``authentication_policy`` variable.
-* The ``binary`` operator is deprecated. Support for this operator may be removed in future versions. Use ``CAST(... AS BINARY)``.
-* Fix for when a parent table initiates a cascading ``SET NULL`` operation on the child table, the virtual column can be set to NULL instead of the value derived from the parent table.
-
-
-Find the full list of bug fixes and changes in the `MySQL 8.0.27 Release Notes <https://dev.mysql.com/doc/relnotes/mysql/8.0/en/news-8-0-27.html>`__.
-
-
-New Features
-================================================================================
-
-* :jirabug:`PS-7960`: Documented the ``rocksdb_partial_index_sort_max_mem`` variable, the ``rocksdb_bulk_load_partial_index`` variable, and the ``rocksdb_cancel_manual_compactions`` variable.
-* :jirabug:`PS-2346`: LP #720547: Implemented an option to allow queries with specific error codes to add entries to the Slow Query Log.
-
-
-Improvements
-================================================================================
-
-* :jirabug:`PS-7955`: Enabled ZenFS functionality on standard Percona Server packages on Debian 11 and Ubuntu 20.04.
-* :jirabug:`PS-7931`: Implemented a :ref:`slowlog_rotation` in Percona Server for MySQL 8.0.
-* :jirabug:`PS-6730`: The 'Last_errno:' field in the Slow Query Log contains only error information.
-* :jirabug:`PS-8076`: Added a deprecation warning when using :ref:`changed_page_tracking`. 
-
-Bugs Fixed
-================================================================================
-
-* :jirabug:`PS-7883`: An ``ALTER`` query caused a server exit when ``--rocksdb_write_disable_wal`` was enabled.
-* :jirabug:`PS-8007`: *Percona Server for MySQL* can fail to start if the server starts before the network mounts the datadir or a local mount of the datadir.
-* :jirabug:`PS-7977`: The AppArmor profile is broken after an 8.0.22-13 to 8.0.23-14 upgrade. (Thanks to Alex Kompel for reporting this issue)
-* :jirabug:`PS-7958`: A ``SELECT`` statement using a Full-Text Search index with a special character caused a server exit.
-* :jirabug:`PS-7940`: The initialization of a virtual column template if a child table had a virtual column caused a restart loop. This initialization prevented a server exit when there was an ``ON DELETE CASCADE`` statement in the parent table and the child table had virtual columns. (Upstream :mysqlbug:`105290`)
-* :jirabug:`PS-5654`: On a view, the query digest for each SELECT statement is now based on the SELECT statement and not the view definition, which was the case for earlier versions (Upstream :mysqlbug:`89559`)
-* :jirabug:`PS-7975`: Fix to allow test main.mtr_unit_tests to complete successfully (Thanks to Thomas Deutschmann for reporting this issue)
-* :jirabug:`PS-7873`: Fix for when the log_status table reported an incorrect executed_gtid (Thanks to zhujzhuo for reporting this issue) (Upstream :mysqlbug:`102175`)
-* :jirabug:`PS-5168` Fix for when the Slow Query Log reports ``tmp_table_size:0``.
-* Normalized the ``zenfs`` utility backup and restore requirements for the ``--path`` command line option, the ``--backup_path`` command-lne option, and the ``restore_path`` command-line option. For more information, see :ref:`zenfs`.
-
-Packaging Notes
-======================
-
-* Red Hat Enterprise Linux 6 (and derivative Linux distributions) are no longer supported.
-
-Known issues
-==========================
-
-The RPM packages for Red Hat Enterprise Linux 7 (and compatible derivatives) do not support TLSv1.3, as it requires OpenSSL 1.1.1, which is currently not available on this platform. 
-
-
-Contact Us
-=======================
-
-The `Documentation Contribution Guide <https://github.com/percona/percona-server/blob/8.0/doc/source/contributing.md>`__ describes the methods available to contribute to the Percona Server for MySQL documentation.
-
-For free technical help, visit the Percona `Community Forum <https://forums.percona.com/c/mysql-mariadb/percona-server-for-mysql-8-0/20>`__.
-
-To report bugs or submit feature requests, open a `JIRA <https://jira.percona.com/projects/PS/issues>`__ ticket.
-
-For paid `support <https://www.percona.com/services/support>`__ and `managed services <https://www.percona.com/services/managed-services>`__ or `consulting services <https://www.percona.com/services/consulting>`__, contact `Percona Sales <https://www.percona.com/about-percona/contact>`__.
-
diff --git a/doc/source/release-notes/Percona-Server-8.0.28-19.rst b/doc/source/release-notes/Percona-Server-8.0.28-19.rst
deleted file mode 100644
index ac306e4ceda8..000000000000
--- a/doc/source/release-notes/Percona-Server-8.0.28-19.rst
+++ /dev/null
@@ -1,40 +0,0 @@
-.. _8.0.28-19:
-
-================================================================================
-*Percona Server for MySQL* 8.0.28-19 (2022-05-12)
-================================================================================
-
-`Percona Server for MySQL <https://www.percona.com/software/mysql-database/percona-server>`_ 8.0.28-19
-includes all the features and bug fixes available in the
-`MySQL 8.0.28 Community Edition <https://dev.mysql.com/doc/relnotes/mysql/8.0/en/news-8-0-28.html>`__
-in addition to enterprise-grade features developed by Percona.
-
-.. include:: ../_res/rn/ps-mysql-blurb.txt
-
-.. contents::
-   :local:
-
-.. include:: ../_res/rn/8.0.28-19-highlights.txt
-
-.. include:: ../_res/rn/8.0.28-19-deprecated.txt
-
-Improvement
-=================================================
-
-* :jirabug:`PS-7871`: Using the ``SET_VAR`` syntax, MyRocks variables can be set dynamically.
-* :jirabug:`PS-8064`: The ability to change log file locations dynamically is restricted.
-
-Bugs fixed
-=================================================
-
-* :jirabug:`PS-7999`: The ``FEDERATED`` storage engine would not reconnect when a ``wait_timeout`` was exceeded. (Thanks to Sami Ahlroos for reporting this issue) (Upstream :mysqlbug:`105878`)
-* :jirabug:`PS-7856`: Fixed for a sever exit caused by an update query on a partition tables.
-* :jirabug:`PS-8032`: An Inplace index build with ``lock=exclusive`` did not generate an ``MLOG_ADD_INDEX`` redo.
-* :jirabug:`PS-8050`: An upgrade from *Percona Server for MySQL* 5.7 to *MySQL* 8.0.26, caused a server exit with an assertion failure.
-
-
-
-
-
-
-.. include:: ../_res/rn/useful-links.txt
\ No newline at end of file
diff --git a/doc/source/release-notes/Percona-Server-8.0.28-20.rst b/doc/source/release-notes/Percona-Server-8.0.28-20.rst
deleted file mode 100644
index 2d614864cbe3..000000000000
--- a/doc/source/release-notes/Percona-Server-8.0.28-20.rst
+++ /dev/null
@@ -1,65 +0,0 @@
-.. _8.0.28-20:
-
-================================================================================
-*Percona Server for MySQL* 8.0.28-20 (2022-06-20)
-================================================================================
-
-`Percona Server for MySQL <https://www.percona.com/software/mysql-database/percona-server>`_ 8.0.28-20
-includes all the features and bug fixes available in the
-`MySQL 8.0.28 Community Edition <https://dev.mysql.com/doc/relnotes/mysql/8.0/en/news-8-0-28.html>`__
-in addition to enterprise-grade features developed by Percona.
-
-.. include:: ../_res/rn/ps-mysql-blurb.txt
-
-.. contents::
-   :local:
-
-Release Highlights
-=================================================
-
-New features and improvements introduced in *Percona Server for MySQL* 8.0.28-20:
-
-* Percona Server for MySQL implements `encryption functions and variables <https://www.percona.com/doc/percona-server/8.0/security/encryption-functions.html>`_ to manage the encryption range. The functions may take an algorithm argument. Encryption converts plaintext into ciphertext using a key and an encryption algorithm. You can also use the user-defined functions with the PEM format keys generated externally by the OpenSSL utility.
-
-* Percona Server for MySQL adds support for the `Amazon Key Management Service (AWS KMS) component <https://www.percona.com/doc/percona-server/8.0/security/using-amz-kms.html>`__.
-
-* ZenFS file system plugin for RocksDB is updated to version 2.1.0.
-
-* Memory leak and error detectors (Valgrind or AddressSanitizer) provide detailed stack traces from dynamic libraries (plugins and components). The detailed stack traces make it easier to identify and fix the issues.
-
-Other improvements and bug fixes introduced by Oracle for *MySQL* 8.0.28 and included in Percona Server for MySQL are the following:
-
-* The ``ASCII`` shortcut for ``CHARACTER SET latin1`` and ``UNICODE`` shortcut for ``CHARACTER SET ucs2`` are deprecated and raise a warning to use ``CHARACTER SET`` instead. The shortcuts will be removed in a future version.
-* A stored function and a loadable function with the same name can share the same namespace. Add the schema name when invoking a stored function in the shared namespace. The server generates a warning when function names collide.
-* InnoDB supports ``ALTER TABLE ... RENAME COLUMN`` operations when using ``ALGORITHM=INSTANT``. 
-* The limit for ``innodb_open_files`` now includes temporary tablespace files. The temporary tablespace files were not counted in the ``innodb_open_files`` in previous versions.
-
-Find the full list of bug fixes and changes in the `MySQL 8.0.28 Release Notes <https://dev.mysql.com/doc/relnotes/mysql/8.0/en/news-8-0-28.html>`__.
-
-New Features
-=================================================
-
-* :jirabug:`PS-7044`: Implements support for `encryption user-defined functions (UDFs) for OpenSSL <https://www.percona.com/doc/percona-server/8.0/security/encryption-functions.html>`__.
-* :jirabug:`PS-7672`: Implements support for the `Amazon Key Management Service component in Percona Server for MySQL <https://www.percona.com/doc/percona-server/8.0/security/using-amz-kms.html>`__.
-* :jirabug:`PS-7748`: Implements the ability to log error messages to a memory buffer.
-
-Improvements
-=================================================
-
-* :jirabug:`PS-8103`: Memory leak and error detectors (Valgrind or AddressSanitizer) provide detailed stack traces from dynamic libraries (plugins and components). The detailed stack traces make it easier to identify and fix the issues.
-* ZenFS file system plugin for RocksDB is updated to version 2.1.0.
-
-Bugs fixed
-=================================================
-
-* :jirabug:`PS-6029`: Data masking ``gen_rnd_us_phone()`` function had a different format compared to MySQL upstream version.
-* :jirabug:`PS-8136`: ``LOCK TABLES FOR BACKUP`` did not prevent InnoDB key rotation. Due to this behavior, Percona Xtrabackup couldn't fetch the key in case the key was rotated after starting the backup.
-* :jirabug:`PS-8143`: Fixed the memory leak in ``File_query_log::set_rotated_name()``. 
-* :jirabug:`PS-7894`: When a query to the MyRocks table was interrupted due to the ``MAX_EXECUTION time`` option, an incorrect error message was received. (Thanks to user hagrid-the-developer for reporting this issue.)
-* :jirabug:`PS-8158`: There was access to possibly not initialized memory. (Thanks to Rinat Ibragimov for reporting this issue.)
-* :jirabug:`PS-5008`: Fixed the memory leak in ``sync_latch_meta_init()`` after mysqld shutdown.
-* **zenfs** utility failed when a user tried to restore a single file into a specified ZenFS path.
-* RocksDB in ZenFS mode ignored OPTIONS-<NNN> files after the restart.
-* RocksDB in ZenFS mode always created PersistentCache on the POSIX file system instead of creating it on ZenFS.
-
-.. include:: ../_res/rn/useful-links.txt
diff --git a/doc/source/release-notes/release-notes_index.rst b/doc/source/release-notes/release-notes_index.rst
deleted file mode 100644
index 0f670716d9c0..000000000000
--- a/doc/source/release-notes/release-notes_index.rst
+++ /dev/null
@@ -1,52 +0,0 @@
-
-.. _release_notes_index: 
-
-=============================================
-*Percona Server for MySQL* 8.0 Release notes
-=============================================
-
-.. toctree::
-   :maxdepth: 1
-
-   8.0.29-21
-   
-   Percona-Server-8.0.28-20
-
-   Percona-Server-8.0.28-19
-    
-   Percona Server for MySQL 8.0.27-18 (2022-03-02) <Percona-Server-8.0.27-18.rst>
-
-   Percona Server for MySQL 8.0.26-17 (2022-01-26) <Percona-Server-8.0.26-17.rst>
-
-   Percona Server for MySQL 8.0.26-16 (2021-10-20) <Percona-Server-8.0.26-16.rst>
-
-   Percona Server for MySQL 8.0.25-15 (2020-07-13) <Percona-Server-8.0.25-15.rst>
-
-   Percona Server for MySQL 8.0.23-14 (2021-05-12) <Percona-Server-8.0.23-14.rst>
-
-   Percona Server for MySQL 8.0.22-13 (2020-12-14) <Percona-Server-8.0.22-13.rst>
-
-   Percona Server for MySQL 8.0.21-12 (2020-10-13) <Percona-Server-8.0.21-12.rst>
-
-   Percona Server for MySQL 8.0.20-11 (2020-07-21) <Percona-Server-8.0.20-11.rst>
-
-   Percona Server for MySQL 8.0.19-10 (2020-03-23) <Percona-Server-8.0.19-10.rst>
-
-   Percona Server for MySQL 8.0.18-9 (2019-12-11) <Percona-Server-8.0.18-9.rst>
-
-   Percona Server for MySQL 8.0.17-8 (2019-10-30) <Percona-Server-8.0.17-8.rst>
-
-   Percona Server for MySQL 8.0.16-7 (2019-08-15) <Percona-Server-8.0.16-7.rst>
-
-   Percona Server for MySQL 8.0.15-6 (2019-05-07) <Percona-Server-8.0.15-6.rst>
-
-   Percona Server for MySQL 8.0.15-5 (2019-03-15) <Percona-Server-8.0.15-5.rst>
-
-   Percona Server for MySQL 8.0.14 <Percona-Server-8.0.14.rst>
-
-   Percona Server for MySQL 8.0.13-4 (2019-01-17) <Percona-Server-8.0.13-4.rst>
-
-   Percona Server for MySQL 8.0.13-3 (2018-12-21) <Percona-Server-8.0.13-3.rst>
-
-   Percona Server for MySQL 8.0.12-2rc1 (2018-10-31) <Percona-Server-8.0.12-2rc1.rst>
-
diff --git a/doc/source/reliability/innodb_corrupt_table_action.rst b/doc/source/reliability/innodb_corrupt_table_action.rst
deleted file mode 100644
index 3fba89d74880..000000000000
--- a/doc/source/reliability/innodb_corrupt_table_action.rst
+++ /dev/null
@@ -1,71 +0,0 @@
-.. _innodb_corrupt_table_action_page:
-
-=========================
- Handle Corrupted Tables
-=========================
-
-When a server subsystem tries to access a corrupted table,
-the server may crash.
-If this outcome is not desirable when a corrupted table is encountered,
-set the new system :ref:`innodb_corrupt_table_action` variable
-to a value which allows the ongoing operation to continue
-without crashing the server.
-
-The server error log registers attempts to access corrupted table pages.
-
-.. rubric:: Interacting with the :ref:`innodb_force_recovery` variable
-
-The :ref:`innodb_corrupt_table_action` variable
-may work in conjunction with the :ref:`innodb_force_recovery` variable
-which considerably reduces
-the effect of *InnoDB* subsystems
-running in the background.
-
-If the :ref:`innodb_force_recovery` option is <4, corrupted pages are lost and the server may continue to run due to the :ref:`innodb_corrupt_table_action` variable having a non-default value.
-
-For more information about the :ref:`innodb_force_recovery` variable,
-see `Forcing InnoDB Recovery
-<https://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html>`_
-from the MySQL Reference Manual.
-
-This feature adds a new system variable.
-
-Version Specific Information
-============================
-
-  * :ref:`8.0.12-1`: The feature was ported from *Percona Server for MySQL* 5.7.
-
-System Variables
-================
-
-.. _innodb_corrupt_table_action:
-
-.. rubric:: ``innodb_corrupt_table_action``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - Yes
-   * - Config file
-     - Yes
-   * - Scope
-     - Global
-   * - Dynamic
-     - Yes
-   * - Data type
-     - ULONG
-   * - Default
-     - ``assert``
-   * - Range
-     - ``assert``, ``warn``, ``salvage``
-
-* With the default value, ``assert``, *XtraDB* will intentionally crash the server with an assertion failure as it would normally do when detecting corrupted data in a single-table tablespace.
-
-* If the ``warn`` value is used it will pass corruption of the table as ``corrupt table`` instead of crashing itself. For this to work :ref:`innodb_file_per_table` should be enabled. All file I/O for the datafile after detected as corrupt is disabled, except for the deletion. 
-
-* When the option value is ``salvage``, *XtraDB* allows read access to a corrupted tablespace, but ignores corrupted pages". You must enable :ref:`innodb_file_per_table`. 
-
-
diff --git a/doc/source/reliability/log_connection_error.rst b/doc/source/reliability/log_connection_error.rst
deleted file mode 100644
index b94341a20446..000000000000
--- a/doc/source/reliability/log_connection_error.rst
+++ /dev/null
@@ -1,13 +0,0 @@
-.. _log_connection_error:
-
-==============================
- Too Many Connections Warning
-==============================
-
-This feature issues the warning ``Too many connections`` to the log, if :ref:`log_error_verbosity` is set to ``2`` or higher. 
-
-Version-Specific Information
-============================
-
-  * `8.0.12-1`: The feature was ported from *Percona Server for MySQL* 5.7.
-
diff --git a/doc/source/scalability/innodb_io.rst b/doc/source/scalability/innodb_io.rst
deleted file mode 100644
index 12a94ec6215d..000000000000
--- a/doc/source/scalability/innodb_io.rst
+++ /dev/null
@@ -1,94 +0,0 @@
-.. _innodb_io_page:
-
-===================================
- Improved InnoDB I/O Scalability
-===================================
-
-Because *InnoDB* is a complex storage engine it must be configured properly in
-order to perform at its best. Some points are not configurable in standard
-*InnoDB*. The goal of this feature is to provide a more exhaustive set of
-options for *XtraDB*.
-
-Version Specific Information
-================================================================================
-
-  * `8.0.12-1`: The feature was ported from *Percona Server for MySQL* 5.7.
-
-System Variables
-================================================================================
-
-.. _innodb_flush_method:
-
-.. rubric:: ``innodb_flush_method``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - Yes
-   * - Config file
-     - Yes
-   * - Scope
-     - Global
-   * - Dynamic
-     - No
-   * - Data type
-     - Enumeration
-   * - Default
-     - NULL
-   * - Allowed values
-     - ``fsync``, ``O_DSYNC``, ``O_DIRECT``, ``O_DIRECT_NO_FSYNC``, ``littlesync``, ``nosync``
-
-The following values are allowed:
-
-  * ``fdatasync``:
-    use ``fsync()`` to flush data, log, and parallel doublewrite files.
-
-  * ``O_SYNC``:
-    use ``O_SYNC`` to open and flush the log and parallel doublewrite files; use ``fsync()`` to flush the data files. Do not use ``fsync()`` to flush the parallel doublewrite file.
-
-  * ``O_DIRECT``:
-    use O_DIRECT to open the data files and ``fsync()`` system call to flush data, log, and parallel doublewrite files.
-
-  * ``O_DIRECT_NO_FSYNC``:
-    use O_DIRECT to open the data files and parallel doublewrite files, but does not use the ``fsync()`` system call to flush the data files, log files, and parallel doublewrite files. Do not use this option for the *XFS* file system.
-
-  * ``ALL_O_DIRECT``: 
-    use O_DIRECT to open data files, log files, and parallel doublewrite files
-    and use ``fsync()`` to flush the data files but not the log files or 
-    parallel doublewrite files. This option is recommended when *InnoDB* log files are big (more than 8GB), otherwise, there may be performance degradation. **Note**: When using this option on *ext4* filesystem variable :ref:`innodb_log_block_size` should be set to 4096 (default log-block-size in *ext4*) in order to avoid the ``unaligned AIO/DIO`` warnings.
-
-
-Starting from *Percona Server for MySQL* 8.0.20-11, the `innodb_flush_method <https://dev.mysql.com/doc/refman/8.0/en/innodb-parameters.html#sysvar_innodb_flush_method>`__ affects doublewrite buffers exactly the same as in *MySQL* 8.0.20. 
- 
-Status Variables
-================================================================================
-
-The following information has been added to ``SHOW ENGINE INNODB STATUS`` to confirm the checkpointing activity: 
-
-.. code-block:: mysql
-
-   The max checkpoint age
-   The current checkpoint age target
-   The current age of the oldest page modification which has not been flushed to disk yet.
-   The current age of the last checkpoint
-   ...
-   ---
-   LOG
-   ---
-   Log sequence number 0 1059494372
-   Log flushed up to   0 1059494372
-   Last checkpoint at  0 1055251010
-   Max checkpoint age  162361775
-   Checkpoint age target 104630090
-   Modified age        4092465
-   Checkpoint age      4243362
-   0 pending log writes, 0 pending chkp writes
-   ...
-
-.. note:: 
-
-        Implemented in *Percona Server for MySQL* 8.0.13-4, ``max checkpoint age`` has been
-        removed because the information is identical to ``log capacity``.  
diff --git a/doc/source/security/apparmor.rst b/doc/source/security/apparmor.rst
deleted file mode 100644
index fcf95bf0e42f..000000000000
--- a/doc/source/security/apparmor.rst
+++ /dev/null
@@ -1,420 +0,0 @@
-.. _enable-apparmor:
-
-=================================================
-Working with AppArmor 
-=================================================
-
-The operating system has a Discretionary Access Controls (DAC) system. AppArmor supplements the DAC with a Mandatory Access Control (MAC) system. AppArmor is the default security module for Ubuntu or Debian systems and uses profiles to define how programs access resources. 
-
-AppArmor is path-based and restricts processes by using profiles. Each profile contains a set of policy rules. Some applications may install their profile along with the application. If an installation does not also install a profile, then that application is not part of the AppArmor subsystem. You can also create profiles since they are simple text files stored in the ``/etc/apparmor.d`` directory. 
-
-A profile is in one of the following modes:
-
-* Enforce - the default setting, applications are prevented from taking actions restricted by the profile rules.
-
-* Complain - applications are allowed to take restricted actions, and the actions are logged.
-
-* Disabled - Applications are allowed to take restricted actions, and the actions are not logged. 
-
- You can mix enforce profiles and complain profiles in your server. 
-
-Install the Utilities used to control AppArmor
-------------------------------------------------
-
-Install the ``apparmor-utils`` package to work with profiles. Use these utilities to create, update, enforce, switch to complain mode, and disable profiles, as needed:
-
-    .. sourcecode:: bash
-
-        $ sudo apt-get -y install apparmor-utils
-        Reading package lists... Done
-        Building dependency tree
-        ...
-        The following additional packages will be installed:
-            python3-apparmor python3-libapparmor
-        ...
-
-Check the Current Status
------------------------------
-
-As root or using ``sudo``, you can check the AppArmor status:
-
-    .. sourcecode:: bash
-
-        $ sudo aa-status
-        apparmor module is loaded.
-        34 profiles are loaded.
-        32 profiles in enforce mode.
-        ...
-            /usr/sbin/mysqld
-        ...
-        2 profiles in complain mode.
-        ...
-        3 profiles have profiles defined.
-        ...
-        0 processes are in complain mode.
-        0 processes are unconfined but have a profile defined.
-
-.. _complain-one:
-
-Switch a Profile to Complain mode
------------------------------------------
-
-Switch a profile to complain mode when the program is in your path with this command:
-
-    .. sourcecode:: bash
-
-        $ sudo aa-complain <program>
-
-If needed, specify the program's path in the command:
-
-    .. sourcecode:: bash
-
-        $ sudo aa-complain /sbin/<program>
-
-If the profile is not in stored in ``/etc/apparmor.d/``, use the following command:
-
-    .. sourcecode:: bash
-
-        $ sudo aa-complain /path/to/profiles/<program>
-
-.. _enforce-one:
-
-Switch a Profile to Enforce mode
----------------------------------
-
-Switch a profile to the enforce mode when the program is in your path with this command:
-
-    .. sourcecode:: bash
-
-        $ sudo aa-enforce <program>
-
-If needed, specify the program's path in the command:
-
-    .. sourcecode:: bash
-
-        $ sudo aa-enforce /sbin/<program>
-
-If the profile is not stored in ``/etc/apparmor.d/``, use the following command:
-
-    .. sourcecode:: bash
-
-        $ sudo aa-enforce /path/to/profile
-
-.. _disable-one:
-
-Disable one profile
-------------------------------
-
-You can disable a profile but it is recommended to :ref:`complain-one`. 
-
-Use either of the following methods to disable a profile:
-
-    .. sourcecode:: bash
-
-        $ sudo ln -s /etc/apparmor.d/usr.sbin.mysqld /etc/apparmor.d/disable/ 
-        $ sudo apparmor_parser -R /etc/apparmor.d/usr.sbin.mysqld
-
-or
-
-    .. sourcecode:: bash
-
-        $ aa-disable /etc/apparmor.d/usr.sbin.mysqld
-
-Reload all profiles
------------------------
-
-Run either of the following commands to reload all profiles:
-
-    .. sourcecode:: bash
-
-        $ sudo service apparmor reload
-
-or
-
-    .. sourcecode:: bash
-
-        $ sudo systemctl reload apparmor.service
-
-.. _reload-one:
-
-Reload one profile
-----------------------
-
-To reload one profile, run the following:
-
-    .. sourcecode:: bash
-
-        $ sudo apparmor_parser -r /etc/apparmor.d/<profile>
-
-For some changes to take effect, you may need to restart the program.
-
-Disable AppArmor
---------------------
-
-AppArmor provides security and disabling the system is not recommened. If AppArmor must be disabled, run the following commands:
-
-1. Check the status.
-
-    .. sourcecode:: bash
-
-        $ sudo apparmor_status
-
-    2. Stop and disable AppArmor.
-
-    .. sourcecode:: bash
-
-        $ sudo systemctl stop apparmor
-        $ sudo systemctl disable apparmor
-
-.. _modify-mysqld:
-
-Add the mysqld profile
----------------------------------
-
-Add the mysqld profile with the following procedure: 
-
-1. Download the current version of the AppArmor:
-
-    ..  sourcecode:: bash
-
-        $ wget https://raw.githubusercontent.com/mysql/mysql-server/8.0/packaging/deb-in/extra/apparmor-profile
-        ...
-        Saving to 'apparamor-profile`
-        ...
-
-2. Move the file to `/etc/apparmor.d/usr.sbin.mysqld`
-
-    .. sourcecode:: bash
-
-        $ sudo mv apparmor-profile /etc/apparmor.d/usr.sbin.mysqld
-
-3. Create an empty file for editing:
-
-    .. sourcecode:: bash
-
-        $ sudo touch /etc/apparmor.d/local/usr.sbin.mysqld
-
-4. Load the profile:
-
-    .. sourcecode:: bash
-
-        $ sudo apparmor_parser -r -T -W /etc/apparmor.d/usr.sbin.mysqld
-
-5. Restart |Percona Server|:
-
-    .. sourcecode:: bash
-
-        $ sudo systemctl restart mysql
-
-6. Verify the profile status:
-
-    .. sourcecode:: bash
-
-        $ sudo aa-status
-        ...
-        processes are in enforce mode
-        ...
-        /usr/sbin/mysqld (100840)
-        ...
-
-Edit the mysqld profile
----------------------------
-
-Only edit :file:`/etc/apparmor.d/local/usr.sbin.mysql`. We recommend that you :ref:`complain-one` before editing the file. Edit the file in any text editor. When your work is done, :ref:`reload-one` and :ref:`enforce-one`.
-
-Configure a custom data directory location
--------------------------------------------
-
-You can change the data directory to a non-default location, like `/var/lib/mysqlcustom`. You should enable audit mode, to capture all of the actions, and edit the profile to allow access for the custom location.
-
-    .. sourcecode:: bash
-
-        $ cat /etc/mysql/mysql.conf.d/mysqld.cnf 
-        #
-        # The Percona Server 8.0 configuration file.
-        #
-        # For explanations see
-        # http://dev.mysql.com/doc/mysql/en/server-system-variables.html
-
-        [mysqld]
-        pid-file    = /var/run/mysqld/mysqld.pid
-        socket        = /var/run/mysqld/mysqld.sock
-        *datadir    = /var/lib/mysqlcustom*
-        log-error    = /var/log/mysql/error.log
-
-Enable audit mode for mysqld. In this mode, the security policy is enforced and all access is logged.
-
-    .. sourcecode:: bash
-
-        $ aa-audit mysqld
-
-Restart Percona Server for MySQL.
-
-    .. sourcecode:: bash
-
-        $ sudo systemctl mysql restart
-
-The restart fails because AppArmor has blocked access to the custom data directory location. To diagnose the issue, check the logs for the following:
-
-* ALLOWED - A log event when the profile is in complain mode and the action violates a policy.
-
-* DENIED - A log event when the profile is in enforce mode and the action is blocked.
-
-For example, the following log entries show ``DENIED``:
-
-    .. sourcecode:: bash
-
-        ...
-        Dec 07 12:17:08 ubuntu-s-4vcpu-8gb-nyc1-01-aa-ps audit[16013]: AVC apparmor="DENIED" operation="mknod" profile="/usr/sbin/mysqld" name="/var/lib/mysqlcustom/binlog.index" pid=16013 comm="mysqld" requested_mask="c" denied_mask="c" fsuid=111 ouid=111
-        Dec 07 12:17:08 ubuntu-s-4vcpu-8gb-nyc1-01-aa-ps kernel: audit: type=1400 audit(1607343428.022:36): apparmor="DENIED" operation="mknod" profile="/usr/sbin/mysqld" name="/var/lib/mysqlcustom/mysqld_tmp_file_case_insensitive_test.lower-test" pid=16013 comm="mysqld" requested_mask="c" denied_mask="c" fsuid=111 ouid=111
-        ...
-
-Open :file:`/etc/apparmor.d/local/usr.sbin.mysqld` in a text editor and edit the following entries in the ``Allow data dir access`` section.
-
-    ..  sourcecode:: text
-
-            # Allow data dir access
-            /var/lib/mysqlcustom/ r,
-            /var/lib/mysqlcustom/** rwk,
-
-In :file:`etc/apparmor.d/local/usr.sbin.mysqld`, comment out, using the `#` symbol, the current entries in the `Allow data dir access` section. This step is optional. If you skip this step, mysqld continues to access the default data directory location.
-
-.. note::
-
-    Edit the local version of the file instead of the main profile. Separating the changes makes maintenance easier. 
-
-Reload the profile:
-
-    .. sourcecode:: bash
-
-        $apparmor_parser -r -T /etc/apparmor.d/usr.sbin.mysqld
-
-Restart mysql:
-
-    .. sourcecode:: bash
-
-        $ systemctl restart mysqld
-
-Set up a custom log location
-----------------------------------
-
-To move your logs to a custom location, you must edit the my.cnf configuration file and then edit the local profile to allow access:
-    
-    .. sourcecode:: text
-
-        cat /etc/mysql/mysql.conf.d/mysqld.cnf 
-        #
-        # The Percona Server 8.0 configuration file.
-        #
-        # For explanations see
-        # http://dev.mysql.com/doc/mysql/en/server-system-variables.html
-
-        [mysqld]
-        pid-file    = /var/run/mysqld/mysqld.pid
-        socket        = /var/run/mysqld/mysqld.sock
-        datadir    = /var/lib/mysql
-        log-error    = /*custom-log-dir*/mysql/error.log
-
-Verify the custom directory exists.
-
-    .. sourcecode:: bash 
-
-        $ ls -la /custom-log-dir/
-        total 12
-        drwxrwxrwx  3 root root 4096 Dec  7 13:09 .
-        drwxr-xr-x 24 root root 4096 Dec  7 13:07 ..
-        drwxrwxrwx  2 root root 4096 Dec  7 13:09 mysql
-
-Restart Percona Server.
-
-    ..  sourcecode:: bash
-
-        $ service mysql start
-        Job for mysql.service failed because the control process exited with error code.
-        See "systemctl status mysql.service" and "journalctl -xe" for details.
-
-
-        $ journalctl -xe
-        ...
-        AVC apparmor="DENIED" operation="mknod" profile="/usr/sbin/mysqld" name="/custom-log-dir/mysql/error.log"
-        ...
-
-The access has been denied by AppArmor. Edit the local profile in the ``Allow log file access`` section to allow access to the custom log location.
-
-    ..  sourcecode:: bash
-
-        $ cat /etc/apparmor.d/local/usr.sbin.mysqld 
-        # Site-specific additions and overrides for usr.sbin.mysqld..
-        # For more details, please see /etc/apparmor.d/local/README.
-
-        # Allow log file access
-        /custom-log-dir/mysql/ r,
-        /custom-log-dir/mysql/** rw,
-
-Reload the profile:
-
-    .. sourcecode:: bash
-
-        $apparmor_parser -r -T /etc/apparmor.d/usr.sbin.mysqld
-
-Restart mysql:
-
-    .. sourcecode:: bash
-
-        $ systemctl restart mysqld
-
-Set ``secure_file_priv`` directory location
----------------------------------------------
-
-By default, `secure_file_priv` points to the following location:
-
-    ..  sourcecode:: mysql
-
-        mysql> show variables like 'secure_file_priv';
-        +------------------+-----------------------+
-        | Variable_name    | Value                 |
-        +------------------+-----------------------+
-        | secure_file_priv | /var/lib/mysql-files/ |
-        +------------------+-----------------------+
-
-To allow access to another location, in a text editor, open the local profile. Review the settings in the ``Allow data dir access`` section:
-
-    ..  sourcecode:: text
-
-        # Allow data dir access
-        /var/lib/mysql/ r,
-        /var/lib/mysql/** rwk,
-
-Edit the local profile in a text editor to allow access to the custom location.
-
-    ..  sourcecode:: bash
-
-        $ cat /etc/apparmor.d/local/usr.sbin.mysqld 
-        # Site-specific additions and overrides for usr.sbin.mysqld..
-        # For more details, please see /etc/apparmor.d/local/README.
-
-        # Allow data dir access
-        /var/lib/mysqlcustom/ r,
-        /var/lib/mysqlcustom/** rwk,
-
-Reload the profile:
-
-    .. sourcecode:: bash
-
-        $apparmor_parser -r -T /etc/apparmor.d/usr.sbin.mysqld
-
-Restart mysql:
-
-    .. sourcecode:: bash
-
-        $ systemctl restart mysqld
-
-
-.. seealso::
-
-    `Ubuntu and AppArmor <https://ubuntu.com/server/docs/security-apparmor>`_
-    
-    `Ubuntu Wiki AppArmor <https://wiki.ubuntu.com/AppArmor>`_
-
-
-
diff --git a/doc/source/security/data-at-rest-encryption.rst b/doc/source/security/data-at-rest-encryption.rst
deleted file mode 100644
index ffcc29a3edd8..000000000000
--- a/doc/source/security/data-at-rest-encryption.rst
+++ /dev/null
@@ -1,78 +0,0 @@
-.. _data_at_rest_encryption:
-
-================================================================================
-Data at Rest Encryption
-================================================================================
-
-.. contents::
-   :local:
-
-Data security is a concern for institutions and organizations. ``Transparent
-Data Encryption (TDE)`` or ``Data at Rest Encryption`` encrypts
-data files. Data at rest is
-any data which is not accessed or changed frequently, stored on different
-types of storage devices. Encryption ensures that if an unauthorized user
-accesses the data files from the file system, the user cannot read contents.
-
-If the user uses master key encryption, the MySQL keyring plugin stores the
-InnoDB master key, used for the master key encryption implemented by *MySQL*.
-The master key is also used to encrypt redo logs, and undo logs, along with the
-tablespaces.
-
-The InnoDB tablespace encryption has the following components:
-
-    * The database instance has a master key for tablespaces and a master key
-      for binary log encryption.
-
-    * Each tablespace has a tablespace key. The key is used to encrypt the
-      Tablespace data pages. Encrypted tablespace keys are written on
-      tablespace header. In the master key implementation, the tablespace key
-      cannot be changed unless you rebuild the table.
-
-Two separate keys allow the master key to be rotated in a minimal operation.
-When the master key is rotated, each tablespace key is decrypted and
-re-encrypted with the new master key. Only the first page of every tablespace
-(.ibd) file is read and written during the key rotation.
-
-An InnoDB tablespace file is comprised of multiple logical and physical pages.
-Page 0 is the tablespace header page and keeps the metadata for the tablespace.
-The encryption information is stored on page 0 and the tablespace key is
-encrypted.
-
-A buffer pool page is not encrypted. An encrypted page is decrypted at the I/O
-layer and added to the buffer pool and used to access the data. The page is
-encrypted by the I/O layer before the page is flushed to disk.
-
-.. note::
-
-   *Percona XtraBackup* version 8 supports the backup of encrypted general
-   tablespaces. Features which are not Generally Available (GA) in |Percona
-   Server| are not supported in version 8.
-
-.. seealso::
-
-    :ref:`vault`
-
-    :ref:`using-keyring-plugin`
-
-    :ref:`encrypting-tables`
-
-    :ref:`encrypting-tablespaces`
-
-    :ref:`encrypting-system-tablespace`
-
-    :ref:`encrypting-temporary-files`
-
-    :ref:`verifying-encryption`
-
-    :ref:`encrypting-doublewrite-buffers`
-
-    :ref:`encrypting-binlogs`
-
-    :ref:`encrypting-redo-log`
-
-    :ref:`undo-tablespace-encryption`
-
-    :ref:`rotating-master-key`
-    
-    :ref:`encrypting-threads`
diff --git a/doc/source/security/data-masking.rst b/doc/source/security/data-masking.rst
deleted file mode 100644
index 0fa4c5139827..000000000000
--- a/doc/source/security/data-masking.rst
+++ /dev/null
@@ -1,281 +0,0 @@
-.. _data-masking:
-
-.. highlight:: mysql
-
-==================================================================
-Data Masking
-==================================================================
-
-This feature was implemented in *Percona Server for MySQL* version :ref:`8.0.17-8`.
-
-The Percona Data Masking plugin is a free and Open Source implementation of the
-*MySQL*'s data masking plugin. Data Masking provides a set of functions to hide
-sensitive data with modified content.
-
-Data masking can have either of the characteristics:
-
-* Generation of random data, such as an email address
-
-* De-identify data by transforming the data to hide content
-
-.. rubric:: Installing the plugin
-
-The following command installs the plugin::
-
-    $ INSTALL PLUGIN data_masking SONAME 'data_masking.so';
-
-.. rubric:: Data Masking functions
-
-The data masking functions have the following categories:
-
-* General purpose
-
-* Special purpose
-
-* Generating Random Data with Defined characteristics
-
-* Using Dictionaries to Generate Random Data
-
-.. rubric:: General Purpose
-
-The general purpose data masking functions are the following:
-
-.. tabularcolumns:: |p{3cm}|p{3cm}|p{8.5cm}|
-.. list-table::
-    :widths: 2 2 6
-    :header-rows: 1
-
-    * - Parameter
-      - Description
-      - Sample
-    * - mask_inner(string, margin1, margin2 [, character])
-      - Returns a result where only the inner part of a string is masked. An optional masking character can be specified.
-      - ::
-
-            mysql> SELECT mask_inner('123456789', 1, 2);
-            +-----------------------------------+
-            | mask_inner('123456789', 1, 2)     |
-            +-----------------------------------+
-            |1XXXXXX89                          |
-            +-----------------------------------+
-
-    * - mask_outer(string, margin1, margin2 [, character])
-      - Masks the outer part of the string. The inner section is not masked.
-      - ::
-
-            mysql> SELECT mask_outer('123456789', 2, 2);
-            +------------------------------------+
-            | mask_outer('123456789', 2, 2).     |
-            +------------------------------------+
-            | XX34567XX                          |
-            +------------------------------------+
-
-.. rubric:: Special Purpose
-
-The special purpose data masking functions are as follows:
-
-.. tabularcolumns:: |p{3cm}|p{3cm}|p{8.5cm}|
-.. list-table::
-    :class: longtable
-    :widths: 2 3 6
-    :header-rows: 1
-
-    * - Parameter
-      - Description
-      - Sample
-    * - mask_pan(string)
-      - Masks the Primary Account Number (PAN) by replacing the
-        string with an "X" except for the last four characters. The PAN string must be 15 characters or 16 characters in length.
-      - ::
-
-            mysql> SELECT mask_pan (gen_rnd_pan());
-            +------------------------------------+
-            | mask_pan(gen_rnd_pan()).           |
-            +------------------------------------+
-            | XXXXXXXXXXX2345                    |
-            +------------------------------------+
-
-    * - mask_pan_relaxed(string)
-      - Returns the first six numbers and the last four numbers. The rest of
-        the string is replaced by "X".
-      - ::
-
-            mysql> SELECT mask_pan_relaxed(gen_rnd_pan());
-            +------------------------------------------+
-            | mask_pan_relaxed(gen_rnd_pan())          |
-            +------------------------------------------+
-            | 520754XXXXXX4848                         |
-            +------------------------------------------+
-
-    * - mask_ssn(string)
-      - Returns a string with only the last four numbers visible. The rest
-        of the string is replaced by "X".
-      - ::
-
-            mysql> SELECT mask_ssn('555-55-5555');
-            +-------------------------+
-            | mask_ssn('555-55-5555') |
-            +-------------------------+
-            | XXX-XX-5555             |
-            +-------------------------+
-
-.. rubric:: Generating Random Data for Specific Requirements
-
-These functions generate random values for specific requirements.
-
-.. tabularcolumns:: |p{3cm}|p{3cm}|p{8.5cm}|
-.. list-table::
-    :class: longtable
-    :widths: 2 3 6
-    :header-rows: 1
-
-    * - Parameter
-      - Description
-      - Sample
-    * - gen_range(lower, upper)
-      - Generates a random number based on a selected range and supports negative numbers.
-      - ::
-
-              mysql> SELECT gen_range(10, 100);
-              +--------------------------------------+
-              | gen_range(10,100)                    |
-              +--------------------------------------+
-              | 56                                   |
-              +--------------------------------------+
-
-              mysql> SELECT gen_range(-100,-80);
-              +--------------------------------------+
-              | gen_range(-100,-80)                    |
-              +--------------------------------------+
-              | -91                             |
-              +--------------------------------------+
-
-    * - gen_rnd_email()
-      - Generates a random email address. The domain is ``example.com``.
-      - ::
-
-             mysql> SELECT gen_rnd_email();
-             +---------------------------------------+
-             | gen_rnd_email()                       |
-             +---------------------------------------+
-             | sma.jrts@example.com                  |
-             +---------------------------------------+
-
-    * - gen_rnd_pan([size in integer])
-      - Generates a random primary account number. This function should only be used for test purposes.
-      - ::
-
-              mysql> SELECT mask_pan(gen_rnd_pan());
-              +-------------------------------------+
-              | mask_pan(gen_rnd_pan())             |
-              +-------------------------------------+
-              | XXXXXXXXXXXX4444                    |
-              +-------------------------------------+
-
-    * - gen_rnd_us_phone()
-      - Generates a random U.S. phone number. The generated number adds the
-        `1` dialing code and is in the `555` area code. The `555` area code
-        is not valid for any U.S. phone number.
-      - ::
-
-            mysql> SELECT gen_rnd_us_phone();
-            +-------------------------------+
-            | gen_rnd_us_phone()            |
-            +-------------------------------+
-            | 1-555-635-5709                |
-            +-------------------------------+
-
-    * - gen_rnd_ssn()
-      - Generates a random, non-legitimate US Social Security Number in an ``AAA-BBB-CCCC`` format. This function should only be used for test purposes.
-      - ::
-
-          mysql> SELECT gen_rnd_ssn()
-          +-----------------------------+
-          | gen_rnd_ssn()               |
-          +-----------------------------+
-          | 995-33-5656                 |
-          +-----------------------------+
-
-.. rubric:: Using Dictionaries to Generate Random Terms
-
-Use a selected dictionary to generate random terms. The dictionary must be loaded from a file with the following characteristics:
-
-* Plain text
-
-* One term per line
-
-* Must contain at least one entry
-
-Copy the dictionary files to a directory accessible to MySQL. The `secure-file-priv <https://dev.mysql.com/doc/refman/8.0/en/server-system-variables.html#sysvar_secure_file_priv>`_ option defines the directories where gen_dictionary_load() loads the dictionary files.
-
-.. note::
-
-    |Percona Server| 8.0.21-12 enabled using the ``secure-file-priv`` option for `gen_dictionary_load()`.
-    
-    
-.. tabularcolumns:: |p{4cm}|p{6cm}|p{6cm}|p{9cm}|
-.. list-table::
-    :class: longtable
-    :widths: 2 3 3 6
-    :header-rows: 1
-
-    * - Parameter
-      - Description
-      - Returns
-      - Sample
-    * - gen_blacklist(str, dictionary_name, replacement_dictionary_name)
-      - Replaces a term with a term from a second dictionary.
-      - A dictionary term
-      - ::
-
-            mysql> SELECT gen_blacklist('apple', 'fruit', 'nut');
-            +-----------------------------------------+
-            | gen_blacklist('apple', 'fruit', 'nut')  |
-            +-----------------------------------------+
-            | walnut                                  |
-            +-----------------------------------------+
-
-    * - gen_dictionary(dictionary_name)
-      - Randomizes the dictionary terms
-      - A random term from the selected dictionary.
-      - ::
-
-            mysql> SELECT gen_dictionary('trees');
-            +--------------------------------------------------+
-            | gen_dictionary('trees')                          |
-            +--------------------------------------------------+
-            | Norway spruce                                    |
-            +--------------------------------------------------+
-
-    * - gen_dictionary_drop(dictionary_name)
-      - Removes the selected dictionary from the dictionary registry. 
-      - Either success or failure
-      - ::
-
-          mysql> SELECT gen_dictionary_drop('mytestdict')
-          +-------------------------------------+
-          | gen_dictionary_drop('mytestdict')   |
-          +-------------------------------------+
-          | Dictionary removed                  |
-          +-------------------------------------+
-
-    * - gen_dictionary_load(dictionary path, dictionary name)
-      - Loads a file into the dictionary registry and configures the dictionary name. The name can be used with any function. If the dictionary is edited, you must drop and then reload the dictionary to view the changes.
-      - Either success or failure
-      - ::
-
-          mysql> SELECT gen_dictionary_load('/usr/local/mysql/dict-files/testdict', 'testdict');
-          +-------------------------------------------------------------------------------+
-          | gen_dictionary_load('/usr/local/mysql/mysql/dict-files/testdict', 'testdict') |
-          +-------------------------------------------------------------------------------+
-          | Dictionary load successfully                                                  |
-          +-------------------------------------------------------------------------------+
-
-.. rubric:: Uninstalling the plugin
-
-The `UNINSTALL PLUGIN <https://dev.mysql.com/doc/refman/8.0/en/uninstall-plugin.html>`_ statement disables and uninstalls the plugin.
-
-.. seealso::
-    *MySQL* Documentation
-    https://dev.mysql.com/doc/refman/8.0/en/data-masking-reference.html
-    https://dev.mysql.com/doc/refman/8.0/en/data-masking-functions.html
diff --git a/doc/source/security/data-scrubbing.rst b/doc/source/security/data-scrubbing.rst
deleted file mode 100644
index abd347060fc0..000000000000
--- a/doc/source/security/data-scrubbing.rst
+++ /dev/null
@@ -1,158 +0,0 @@
-.. _data-scrubbing:
-
-Data Scrubbing
-================================================================================
-
-:Availability: This feature is tech preview quality
-
-The ``DELETE`` statement does the following:
-
-* Marks the rows as deleted
-* Added to ``unused``
-* Records the deleted row position
-* Records the time when delete was committed
-
-The data is not immediately removed from disk storage. When a new row is inserted, the row is stored without fragmentation in a page with free space. The deleted data remains on the disk until new data overwrites it.
-
-Using Data Scrubbing, you have two options to remove the data and reclaim the space:
-
-+---------------------+------------------------------------------------------------------------------------+
-| How data is removed | Descriptions                                                                       |
-+=====================+====================================================================================+
-| Immediate           | The data is removed immediately, independent of key rotation or background threads |
-+---------------------+------------------------------------------------------------------------------------+
-| Background          | The moment when the data is removed can be unpredictable                           |
-+---------------------+------------------------------------------------------------------------------------+
-
-Once enabled, data scrubbing works automatically on each tablespace.
-
-To enable data scrubbing, you must enable either one or both of the following variables:
-
-- :ref:`innodb-background-scrub-data-uncompressed`
-- :ref:`innodb-background-scrub-data-compressed`
-
-Uncompressed tables can also be scrubbed immediately, independent of key
-rotation or background threads. Setting the variable
-:ref:`innodb-immediate-scrub-data-uncompressed` enables this operation. This variable does not support operations on compressed tables.
-
-For background scrubbing, you must set the :ref:`innodb_encryption_threads` variable to a value greater than **zero** when you enable data scrubbing. Intermediate scrubbing does not use encryption threads. A separate thread performs log scrubbing.
-
-System Variables
---------------------------------------------------------------------------------
-
-.. _innodb_background_scrub_data_compressed:
-
-.. rubric:: ``innodb_background_scrub_data_compressed``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--innodb-background-scrub-data-compressed``
-   * - Scope
-     - Global
-   * - Dynamic
-     - Yes
-   * - Data type
-     - Boolean
-   * - Default
-     - ``OFF``
-   
-Enables compressed data scrubbing.
-
-.. _innodb_background_scrub_data_uncompressed:
-
-.. rubric:: ``innodb_background_scrub_data_uncompressed``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--innodb-background-scrub-data-uncompressed``
-   * - Scope
-     - Global
-   * - Dynamic
-     - Yes
-   * - Data type
-     - Boolean
-   * - Default
-     - ``OFF``
- 
-Enables uncompressed data scrubbing.
-
-.. _innodb_scrub_log:
-
-.. rubric:: ``innodb_scrub_log``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--innodb-scrub-log``
-   * - Scope
-     - Global
-   * - Dynamic
-     - No
-   * - Data type
-     - Boolean
-   * - Default
-     - ``OFF``
-
-Enables redo log scrubbing.
-
-.. _innodb_scrub_log_speed:
-
-.. rubric:: ``innodb_scrub_log_speed``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--innodb-scrub-log-speed``
-   * - Scope
-     - Global
-   * - Dynamic
-     - Yes
-   * - Data type
-     - Numeric
-   * - Default
-     - 256
- 
-Defines the scrubbing speed in bytes/sec of the redo log.
-
-.. _innodb_immediate_scrub_data_uncompressed:
-
-.. rubric:: ``innodb_immediate_scrub_data_uncompressed``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--innodb-immediate-scrub-data-uncompressed``
-   * - Scope
-     - Global
-   * - Dynamic
-     - Yes
-   * - Data type
-     - Boolean
-   * - Default
-     - ``OFF``
-
-Enables data scrubbing of uncompressed data.
-
-.. seealso::
-
-   Vault Documentation
-      https://www.vaultproject.io/docs/index.html
-   General-Purpose Keyring Key-Management Functions
-      https://dev.mysql.com/doc/refman/8.0/en/keyring-udfs-general-purpose.html
diff --git a/doc/source/security/encrypting-binlogs.rst b/doc/source/security/encrypting-binlogs.rst
deleted file mode 100644
index 20678cc5462c..000000000000
--- a/doc/source/security/encrypting-binlogs.rst
+++ /dev/null
@@ -1,141 +0,0 @@
-.. _encrypting-binlogs:
-
-=======================================================================
-Encrypting Binary Log Files and Relay Log Files
-=======================================================================
-
-Binary log file and relay log file encryption at rest ensures the
-server-generated binary logs are encrypted in persistent storage.
-
-Upgrading from *Percona Server for MySQL* 8.0.15-5 to any Higher Version
-----------------------------------------------------------------
-
-Starting from the release :ref:`8.0.15-5`, *Percona Server for MySQL* uses the upstream
-implementation of binary log file and relay log file encryption.
-
-The :ref:`encrypt-binlog` variable is
-removed, and the related command-line option `--encrypt-binlog` is not
-supported. It is important to remove the `encrypt-binlog` variable from your
-configuration file before you attempt to upgrade either from another release
-in the *Percona Server for MySQL* 8.0 series or from *Percona Server for MySQL* 5.7.
-Otherwise, a server boot error is generated, and reports an unknown
-variable.
-
-The implemented binary log file encryption is compatible with the older
-format. The encrypted binary log file used in a previous version of MySQL 8.0
-series or Percona Server for MySQL series is supported.
-
-Architecture
-------------
-
-The Binary log encryption uses the following tiers:
-
-    * File password
-
-    * Binary log file encryption key
-
-The file password encrypts the content of a single binary file or relay log
-file. The binary log encryption key encrypts the file password and the key
-is stored in the keyring.
-
-Implementation
----------------
-
-After you have enabled the :ref:``binlog_encryption`` variable and the keyring is
-available, you can encrypt the data content for new binary log files and relay
-log files. Only the data content is encrypted. Attempting a binary log file or
-relay log file encryption without the keyring generates a MySQL error.
-
-In replication, the source maintains the binary log and the replica maintains a binary
-log copy called the relay log. The source copies a stream of decrypted binary
-log events to a replica using SSL connections to encrypt the stream. The events
-are re-executed on the replica.  The source and replicas can use separate
-keyring storages and different keyring plugins.
-
-When the :ref:`binlog_encryption` is set to ``OFF``, the server rotates the
-binary log files and the relay log files and all new log files are unencrypted.
-The encrypted files are not unencrypted, but the server can read the files.
-
-When an encrypted binary log is dumped, and this operation involves decryption,
-use ``mysqlbinlog`` with the ``--read-from-remote-server`` option.
-
-.. note::
-
-    The `--read-from-remote-server` option only applies to the binary logs.
-    Encrypted relay logs can not be dumped or decrypted with this option.
-    
-Enabling Binary Log Encryption
--------------------------------
-
-In versions *Percona Server for MySQL* 8.0.15-5 and later, set the `binlog_encryption` variable
-to ``ON`` in a startup configuration file, such as :file:`my.cnf`. The variable
-is set to ``OFF`` by default.
-
-.. code-block:: text
-
-    binlog_encryption=ON
-
-Verifying the Encryption
--------------------------
-
-To verify if the binary log encryption option is enabled, run the following
-statement:
-
-.. code-block:: mysql
-
-    mysql> SHOW BINARY LOGS;
-
-    +-------------------+----------------+---------------+
-    | Log_name          | File_size      | Encrypted     |
-    +-------------------+----------------+---------------+
-    | binlog.00011      | 72367          | No            |
-    | binlog:00012      | 71503          | No            |
-    | binlog:00013      | 73762          | Yes           |
-    +-------------------+----------------+---------------+
-
-The ``SHOW BINARY LOGS`` statement displays the name, size, and if a binary log
-file is encrypted or unencrypted.
-
-Binary log file variables
---------------------------
-
-.. _encrypt_binlog:
-
-.. rubric:: ``encrypt_binlog``
- 
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--encrypt-binlog``
-   * - Dynamic
-     - No
-   * - Scope
-     - Global
-   * - Data type
-     - Boolean
-   * - Default
-     - ``OFF``
-
-The variable was removed in :ref:`8.0.15-5`.
-
-This variable enables or disables the binary log file and relay log file encryption.
-
-.. seealso::
-
-    *MySQL* Documentation:
-    `Encrypting Binary Log Files and Relay Log Files <https://dev.mysql.com/doc/refman/8.0/en/replication-binlog-encryption.html>`_
-
-.. seealso::
-
-    :ref:`encrypting-tables`
-
-    :ref:`encrypting-tablespaces`
-
-    :ref:`encrypting-system-tablespace`
-
-    :ref:`encrypting-temporary-files`
-
-
diff --git a/doc/source/security/encrypting-doublewrite-buffers.rst b/doc/source/security/encrypting-doublewrite-buffers.rst
deleted file mode 100644
index 8ce21f07a689..000000000000
--- a/doc/source/security/encrypting-doublewrite-buffers.rst
+++ /dev/null
@@ -1,65 +0,0 @@
-.. _encrypting-doublewrite-buffers:
-
-=======================================================================
-Encrypting Doublewrite Buffers
-=======================================================================
-
-A summary of Doublewrite buffer and Doublewrite buffer encryption changes:
-
-.. tabularcolumns:: |p{5cm}|p{11cm}|
-
-.. list-table::
-   :header-rows: 1
-
-   * - *Percona Server for MySQL* Versions
-     - Doublewrite Buffer and Doublewrite Buffer Encryption Implementation
-   * - Percona-Server-8.0.12-1.alpha to Percona-Server-8.0.19-10 inclusive
-     - *Percona Server for MySQL* had its own implementation of the parallel doublewrite buffer which was enabled by setting the :ref:`innodb_parallel_doublewrite_path` variable.
-
-       Enabling the :ref:`innodb_parallel_dblwr_encrypt` controlled whether the parallel
-       doublewrite pages were encrypted or not. In case the parallel doublewrite buffer was disabled (:ref:`innodb_parallel_doublewrite_path` was set to empty string),the doublewrite buffer pages were located in the system tablespace (ibdata1). The system tablespace itself could be encrypted by setting :ref:`innodb_sys_tablespace_encrypt`, which also encrypted the  doublewrite buffer pages.
-   * - Percona Server from Percona-Server-8.0.20-11 to Percona-Server-8.0.22-13 inclusive
-     - *MySQL* 8.0.20 implemented its own `parallel doublewrite buffer <https://dev.mysql.com/doc/refman/8.0/en/innodb-doublewrite-buffer.html>`__, which is stored in external files (#ib_16384_xxx.dblwr) and not stored in the system tablespace. Percona's implementation was reverted. As a result, :ref:`innodb_parallel_doublewrite_path` was deprecated.
-
-       However, *MySQL* did not implement parallel doublewrite buffer
-       encryption at this time, so Percona reimplemented parallel doublewrite
-       buffer encryption on top of the *MySQL* parallel doublewrite buffer
-       implementation. Percona preserved the meaning and
-       functionality of the :ref:`innodb_parallel_dblwr_encrypt` variable.
-   * - Percona Server from Percona-Server-8.0.23-14
-     - *MySQL* 8.0.23 implemented its own version of `parallel doublewrite encryption <https://dev.mysql.com/doc/refman/8.0/en/innodb-data-encryption.html#innodb-doublewrite-file-encryption>`__.
-       Pages that belong to encrypted tablespaces are also written into the
-       doublewrite buffer in an encrypted form. Percona's
-       implementation was reverted and :ref:`innodb_parallel_dblwr_encrypt` is deprecated.
-
-For *Percona Server for MySQL* versions below *Percona Server for MySQL* version 8.0.23-14, *Percona* encrypts the ``doublewrite buffer`` using :ref:`innodb_parallel_dblwr_encrypt`.
-
-.. _innodb_parallel_dblwr_encrypt:
-
-.. rubric:: ``innodb_parallel_dblwr_encrypt``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--innodb-parallel-dblwr-encrypt``
-   * - Scope
-     - Global
-   * - Dynamic
-     - Yes
-   * - Data type
-     - Boolean
-   * - Default
-     - ``OFF``
-
-The variable was announced as deprecated in :ref:`8.0.23-14`.
-
-This variable controls whether the parallel doublewrite buffer pages were encrypted or not. The encryption used the key of the tablespace to which the page belong. 
-
-Starting from *Percona Server for MySQL* 8.0.23-14, regardless of the value of this variable, pages from the encrypted tablespaces are always written to the doublewrite buffer as encrypted, and pages from unencrypted tablespaces are always written unencrypted.
-
-The :ref:`innodb_parallel_dblwr_encrypt` is accepted but has no effect. An explicit attempt to change the value generates the following warning in the error log file:
-
-    **Setting Percona-specific INNODB_PARALLEL_DBLWR_ENCRYPT is deprecated and has no effect.**
diff --git a/doc/source/security/encrypting-redo-log.rst b/doc/source/security/encrypting-redo-log.rst
deleted file mode 100644
index 1ed002a54f10..000000000000
--- a/doc/source/security/encrypting-redo-log.rst
+++ /dev/null
@@ -1,76 +0,0 @@
-.. _encrypting-redo-log:
-
-================================================================================
-Encrypting the Redo Log files
-================================================================================
-
-MySQL uses the redo log files to apply changes during data recovery.
-
-Encrypt the redo log files by enabling the :ref:`innodb_redo_log_encrypt`
-variable. The default value for the variable is ``OFF``.
-
-The Redo log files uses the tablespace encryption key.
-
-.. _innodb_redo_log_encrypt:
-
-.. rubric:: ``innodb_redo_log_encrypt``
- 
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--innodb-redo-log-encrypt``
-   * - Dynamic
-     - Yes
-   * - Scope
-     - Global
-   * - Data type
-     - Text
-   * - Default
-     - OFF
-
-Determines the encryption for redo log data for tables.
-
-When you enable `innodb_redo_log_encrypt` any existing redo log pages stay
-unencrypted, and new pages are encrypted when they are written to disk. If you
-disable `innodb_redo_log_encrypt` after enabling the variable, any encrypted pages remain encrypted, but the new pages are unencrypted.
-
-As implemented in :ref:`8.0.16-7`, the supported values for
-:ref:`innodb_redo_log_encrypt` are the following:
-
-* ON
-
-* OFF
-
-* master_key
-
-* keyring_key
-
-The ``keyring_key`` value is in tech preview.
-
-.. seealso::
-
-   For more information on the keyring_key - :ref:`encrypting-threads`
-
-.. note::
-
-    For `innodb_redo_log_encrypt`, the "ON" value is a compatibility alias for
-    master_key.
-
-After starting the server, an attempt to encrypt the redo log files fails
-if you have the following conditions:
-
-    * Server started with no keyring specified
-
-    * Server started with a keyring, but you specified a redo
-      log encryption method that is different then previously used
-      method on the server.
-      
-.. seealso::
-
-    :ref:`encrypting-tables`
-
-    :ref:`encrypting-tablespaces`
-
diff --git a/doc/source/security/encrypting-system-tablespace.rst b/doc/source/security/encrypting-system-tablespace.rst
deleted file mode 100644
index 914617a68ef3..000000000000
--- a/doc/source/security/encrypting-system-tablespace.rst
+++ /dev/null
@@ -1,98 +0,0 @@
-.. _encrypting-system-tablespace:
-
-==================================================================
-Encrypting the System Tablespace
-==================================================================
-
-*Percona Server for MySQL* supports system tablespace encryption. The InnoDB system
-tablespace may be encrypted with the master key encryption or the keyring
-encryption with advanced encryption key rotation. 
-
-Keyring encryption is a **tech preview** feature.
-
-.. seealso::
-
-    :ref:`encrypting-threads`.  
-
-The limitation is the following:
-
-* You cannot convert the system tablespace from the encrypted state to the
-  unencrypted state, or the unencrypted state to the encrypted state. If a 
-  conversion is needed, create a new instance with the
-  system tablespace in the required state and transfer the user tables to that instance.
-
-.. important::
-
-    A server instance initialized with the encrypted InnoDB system tablespace
-    cannot be downgraded. It is not possible to parse encrypted InnoDB system
-    tablespace pages in a version of *Percona Server for MySQL* lower than the version
-    where the InnoDB system tablespace has been encrypted.
-
-To enable system tablespace encryption, edit the my.cnf file with the following:
-
-* Add the :ref:`innodb_sys_tablespace_encrypt`
-* Edit the `innodb_sys_tablespace_encrypt` value to "ON"
-
-System tablespace encryption can only be enabled with the ``--initialize``
-option
-
-You can create an encrypted table as follows:
-
-.. code-block:: MySQL
-
-    mysql> CREATE TABLE table_name TABLESPACE=innodb_system ENCRYPTION='Y';
-
-
-System Variables
-------------------------------------------------------------------
-
-.. _innodb_sys_tablespace_encrypt:
-
-.. rubric:: ``innodb_sys_tablespace_encrypt``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--innodb-sys-tablespace-encrypt``
-   * - Scope
-     - Global
-   * - Dynamic
-     - No
-   * - Data type
-     - Boolean
-   * - Default
-     - ``OFF``
-
-Enables the encryption of the InnoDB system tablespace. 
-
-.. seealso::
-
-   *MySQL* Documentation: mysql system Tablespace Encryption
-   https://dev.mysql.com/doc/refman/8.0/en/innodb-data-encryption.html#innodb-mysql-tablespace-encryption-enabling-disabling
-
-   *MySQL* Documentation: ``--initialize`` option
-      https://dev.mysql.com/doc/refman/8.0/en/server-options.html#option_mysqld_initialize
-
-Re-Encrypt the System Tablespace
-----------------------------------
-
-You can re-encrypt the system tablespace key with master key rotation. When
-the master key is rotated, the tablespace key is decrypted and re-encrypt
-with the new master key. Only the first page of the tablespace (.ibd) file is
-read and written during the key rotation. The tables in the tablespace are not
-re-encrypted.
-
-The command is as follows:
-
-.. code-block:: MySQL
-
-  mysql> ALTER INSTANCE ROTATE INNODB MASTER KEY;
-
-.. seealso::
-
-    :ref:`rotating-master-key`
-
-    :ref:`using-keyring-plugin`
diff --git a/doc/source/security/encrypting-tables.rst b/doc/source/security/encrypting-tables.rst
deleted file mode 100644
index 4caefae56760..000000000000
--- a/doc/source/security/encrypting-tables.rst
+++ /dev/null
@@ -1,47 +0,0 @@
-.. _encrypting-tables:
-
-=========================================================
-Encrypting File-Per-Table Tablespace
-=========================================================
-
-An file-per-table tablespace stores the
-table data and the indexes for a single InnoDB table. In this tablespace
-configuration, each table is stored in an .ibd file.
-
-The architecture for data at rest encryption for file-per-table tablespace
-has two tiers:
-
-* Master key
-* Tablespace keys.
-
-The keyring plugin must be installed and enabled. The
-file_per_table tablespace inherits the schema default encryption
-setting,unless you explicitly define encryption in the ``CREATE TABLE``
-statement.
-
-An example of the ``CREATE TABLE`` statement:
-
-.. code-block:: mysql
-
-   mysql> CREATE TABLE sample (id INT, mytext varchar(255)) ENCRYPTION='Y';
-
-An example of an ``ALTER TABLE`` statement.
-
-.. code-block:: mysql
-
-    mysql> ALTER TABLE ... ENCRYPTION='Y';
-
-Without the ``ENCRYPTION`` option in the `ALTER TABLE` statement, the table's
-encryption state does not change. An encrypted table remains encrypted. An
-unencrypted table remains unencrypted.
-
-.. seealso::
-
-  *MySQL* Documentation:
-  -  `File-Per-Table Encryption <https://dev.mysql.com/doc/refman/8.0/en/innodb-data-encryption.html#innodb-data-encryption-enabling-disabling>`__
-
-.. seealso::
-
-    :ref:`encrypting-tablespaces`
-
-    :ref:`encrypting-temporary-files`
diff --git a/doc/source/security/encrypting-tablespaces.rst b/doc/source/security/encrypting-tablespaces.rst
deleted file mode 100644
index 82619dd9f504..000000000000
--- a/doc/source/security/encrypting-tablespaces.rst
+++ /dev/null
@@ -1,203 +0,0 @@
-..  _encrypting-tablespaces:
-
-======================================================
-Encrypting a Schema or a General Tablespace
-======================================================
-
-*Percona Server for MySQL* uses the same encryption architecture as *MySQL*, a two-tier
-system consisting of a master key and tablespace keys. The master key can be
-changed, or rotated in the keyring, as needed. Each tablespace key, when
-decrypted, remains the same.
-
-The feature requires the keyring plugin.
-
-Setting the Default for Schemas and General Tablespace Encryption
-==================================================================
-
-The tables in a general tablespace are either all encrypted or all unencrypted.
-A tablespace cannot contain a mixture of encrypted tables and unencrypted
-tables.
-
-In versions before *Percona Server for MySQL* 8.0.16-7, use the variable
-:ref:`innodb_encrypt_tables`.
-
-.. _innodb_encrypt_tables:
-
-.. rubric:: ``innodb_encrypt_tables``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--innodb-encrypt-tables``
-   * - Scope
-     - Global
-   * - Dynamic
-     - Yes
-   * - Data type
-     - Text
-   * - Default
-     - ``OFF``
-
-The variable was removed in :ref:`8.0.16-7`.
-
-The variable is considered **deprecated** and was removed in version 8.0.16-7.
-The default setting is "OFF".
-
-The encryption of a schema or a general tablespace is determined by the
-:ref:`default_table_encryption` variable unless you specify the
-ENCRYPTION clause in the CREATE SCHEMA or CREATE TABLESPACE statement. This
-variable is implemented in *Percona Server for MySQL* version 8.0.16-7.
-
-You can set the :ref:`default_table_encryption` variable in an individual
-connection.
-
-.. code-block:: mysql
-
-    mysql> SET default_table_encryption=ON;
-
-System Variable
-----------------
-
-.. _default_table_encryption:
-
-.. rubric:: ``default_table_encryption``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``default-table-encryption``
-   * - Scope
-     - Session
-   * - Dynamic
-     - Yes
-   * - Data type
-     - Text
-   * - Default
-     - OFF
-
-Defines the default encryption setting for schemas and general tablespaces. The
-variable allows you to create or alter schemas or tablespaces without specifying
-the ENCRYPTION clause. The default encryption setting applies only to schemas
-and general tablespaces and is not applied to the MySQL system tablespace.
-
-The variable has the following possible values:
-
-.. tabularcolumns:: |p{5cm}|p{11cm}|
-
-.. list-table::
-   :header-rows: 1
-
-   * - Value 
-     - Description
-   * - ON
-     - New tables are encrypted. Add ``ENCRYPTION="N"`` to the ``CREATE TABLE`` or ``ALTER TABLE`` statement to create unencrypted tables.
-   * - OFF
-     - By default, new tables are unencrypted. Add ``ENCRYPTION="Y"`` to the ``CREATE TABLE`` or ``ALTER TABLE`` statement to create encrypted tables. 
-   * - ONLINE_TO_KEYRING
-     - :Availability: This value is **Experimental** quality.
-       
-       Converts a tablespace encrypted by a Master Key to use Advanced Encryption Key Rotation. You can only apply the keyring encryption when creating tables or altering tables.
-   * - ONLINE_FROM_KEYRING_TO_UNENCRYPTED
-     - :Availability: This value is **Experimental** quality
-       
-       Converts a tablespace encrypted by Advanced Encryption Key Rotation to unencrypted.
-
-.. note::
-
-    The `ALTER TABLE` statement changes the current encryption mode only if you
-    use the `ENCRYPTION` clause.
-
-.. seealso::
-
-      MySQL Documentation: default_table_encryption
-      https://dev.mysql.com/doc/refman/8.0/en/server-system-variables.html
-
-.. _merge-sort-encryption:
-
-.. rubric:: Merge-sort-encryption
-
-.. _innodb_encrypt_online_alter_logs:
-
-.. rubric:: ``innodb_encrypt_online_alter_logs``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--innodb_encrypt-online-alter-logs``
-   * - Scope
-     - Global
-   * - Dynamic
-     - Yes
-   * - Data type
-     - Boolean
-   * - Default
-     - OFF
-
-This variable simultaneously turns on the encryption of files used by InnoDB for
-full text search using parallel sorting, building indexes using merge sort, and
-online DDL logs created by InnoDB for online DDL. Encryption is available for
-file merges used in queries and backend processes.
-
-Setting Tablespace `ENCRYPTION` without the Default Setting
-----------------------------------------------------------------
-
-If you do not set the default encryption setting, you can create general
-tablespaces with the ``ENCRYPTION`` setting.
-
-.. code-block:: mysql
-
-    mysql> CREATE TABLESPACE tablespace_name ENCRYPTION='Y';
-
-All tables contained in the tablespace are either encrypted or not encrypted.
-You cannot encrypted only some of the tables in a general tablespace. This
-feature extends the  `CREATE TABLESPACE
-<https://dev.mysql.com/doc/refman/8.0/en/create-tablespace.html>`_ statement to
-accept the ``ENCRYPTION='Y/N'`` option.
-
-.. note::
-
-   Prior to *Percona Server for MySQL* 8.0.13, the ``ENCRYPTION`` option was specific to
-   the ``CREATE TABLE`` or ``SHOW CREATE TABLE`` statement. As of *Percona Server for MySQL*
-   8.0.13, this option is a tablespace attribute and  no longer  allowed with the
-   ``CREATE TABLE`` or ``SHOW CREATE TABLE`` statement except for file-per-table
-   tablespaces.
-
-In an encrypted general tablespace, an attempt to create an unencrypted table
-generates the following error:
-
-.. code-block:: mysql
-
-    mysql> CREATE TABLE t3 (a INT, b TEXT) TABLESPACE foo ENCRYPTION='N';
-    ERROR 1478 (HY0000): InnoDB: Tablespace 'foo' can contain only ENCRYPTED tables.
-
-An attempt to create or to move any tables, including partitioned ones, to a
-general tablespace with an incompatible encryption setting are diagnosed and
-the process is aborted.
-
-If you must move tables between incompatible tablespaces, create tables with the
-same structure in another tablespace and run ``INSERT INTO SELECT`` from each of
-the source tables into the destination tables.
-
-Exporting an Encrypted General Tablespace
---------------------------------------------
-
-You can only export encrypted file-per-table tablespaces
-
-.. seealso::
-
-    :ref:`encrypting-tables`
-
-    :ref:`encrypting-system-tablespace`
-
-    :ref:`encrypting-temporary-files`
-
-    :ref:`verifying-encryption`
diff --git a/doc/source/security/encrypting-temporary-files.rst b/doc/source/security/encrypting-temporary-files.rst
deleted file mode 100644
index 926108b925f0..000000000000
--- a/doc/source/security/encrypting-temporary-files.rst
+++ /dev/null
@@ -1,112 +0,0 @@
-.. _encrypting-temporary-files:
-
-==========================================================
-Encrypting Temporary Files
-==========================================================
-
-For InnoDB user-created temporary tables, created in a temporary tablespace
-file, use the :ref:`innodb_temp_tablespace_encrypt` variable.
-
-.. _innodb_temp_tablespace_encrypt:
-
-.. rubric:: ``innodb_temp_tablespace_encrypt``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``innodb-temp-tablespace-encrypt``
-   * - Scope
-     - Global
-   * - Dynamic
-     - Yes
-   * - Data type
-     - Boolean
-   * - Default
-     - ``OFF``
-
-When this variable is set to ``ON``, the server encrypts the global temporary
-tablespace (:file: `ibtmp*` files) and the session temporary tablespaces
-(:file: `#innodb_temp/temp_*.ibt` files). The variable does not enforce the
-encryption of currently open temporary files and does not rebuild the system
-temporary tablespace to encrypt data that has already been written.
-
-The ``CREATE TEMPORARY TABLE`` does not support the ``ENCRYPTION`` clause. The
-``TABLESPACE`` clause cannot be set to innodb_temporary.
-
-The global temporary tablespace datafile ``ibtmp1`` contains the temporary table
-undo logs while intrinsic temporary tables and user-created temporary tables
-are located in the encrypted session temporary tablespace.
-
-To create new temporary tablespaces unencrypted, the following variables must
-be set to ``OFF`` at runtime:
-
-* :ref:`innodb_temp_tablespace_encrypt`
-
-* :ref:`default_table_encryption`
-
-Any existing encrypted user-created temporary files and intrinsic temporary
-tables remain in an encrypted session.
-
-Temporary tables are only destroyed when the session is disconnected.
-
-The `default_table_encryption` setting in my.cnf determines if a temporary
-table is encrypted.
-
-If the `innodb_temp_tablespace_encrypt` = "OFF" and the
-`default_table_encryption` ="ON", the user-created temporary tables are
-encrypted. The temporary tablespace datafile ``ibtmp1``, which contains undo
-logs, is not encrypted.
-
-If the ``innodb_temp_tablespace_encrypt`` is "ON" for the system tablespace,
-InnoDB generates an encryption key and encrypts the system temporary
-tablespace.  If you reset the encryption to "OFF", all subsequent pages are
-written to an unencrypted tablespace. Any generated keys are not erased to
-allow encrypted tables and undo data to be decrypted.
-
-.. important::
-
-    The keyring plugin must be loaded to use the variable. The server generates an error and refuses to create temporary tables if the keyring plugin is not loaded.
-
-
-For each temporary file, an encryption key has the following attributes:
-
-* Generated locally
-
-* Maintained in memory for the lifetime of the temporary file 
-
-* Discarded with the temporary file
-
-System Variables
-----------------------
-
-.. _encrypt_tmp_files:
-
-.. rubric:: ``encrypt_tmp_files``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--encrypt_tmp_files``
-   * - Scope
-     - Global
-   * - Dynamic
-     - No
-   * - Data type
-     - Boolean
-   * - Default
-     - ``OFF``
-
-This variable turns "ON" the encryption of temporary files created by |Percona
-Server|. The default value is ``OFF``.
-
-  .. seealso::
-
-    *MySQL* Documentation
-    https://dev.mysql.com/doc/refman/8.0/en/create-temporary-table.html
-
diff --git a/doc/source/security/encrypting-threads.rst b/doc/source/security/encrypting-threads.rst
deleted file mode 100644
index 100ec5f26a08..000000000000
--- a/doc/source/security/encrypting-threads.rst
+++ /dev/null
@@ -1,169 +0,0 @@
-.. _encrypting-threads:
-
-================================================================================
-Working with Advanced Encryption Key Rotation
-================================================================================
-
-:Availability: This feature is tech preview.
-
-The Advanced Encryption Key Rotation feature lets you perform specific encryption and
-decryption tasks in real-time. 
-
-The following table explains the benefits of Advanced Encryption Key Rotation:
-
-.. list-table::
-    :widths: 25 25
-    :header-rows: 1
-    
-    * - Advanced Encryption Key Rotation
-      - Master Key Encryption
-    * - Encrypts any existing tablespaces in a single operation. Advanced
-        Encryption Key Rotation
-        allows encryption to be applied to all or selected existing
-        tablespaces. You can exclude tablespaces.
-      - Encrypts each existing tablespace as a separate operation.
-    * - Encrypts tables with a key from a keyring.
-      - Encrypts tables with a key that is then stored in the encryption header
-        of the
-        tablespace.
-    * - Re-encrypts each tablespace page by page when the key is rotated.
-      - Re-encrypts only the tablespace encryption header when the key is rotated.
-   
-If you enable Advanced Encryption Key Rotation with a Master key encrypted
-tablespace, the tablespace is re-encrypted with the keyring key in a background
-process. If the Advanced Encryption Key Rotation feature is enabled, you cannot
-convert a tablespace to use Master key encryption. You must disable the feature
-before you convert the tablespace.
-
-:Availability: This feature is tech preview quality.
-
-You must have the SYSTEM_VARIABLES_ADMIN privilege or the SUPER privilege to set
-these variables.
-
-.. _innodb_encryption_threads:
-
-.. rubric:: ``innodb_encryption_threads``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--innodb-encryption-threads``
-   * - Scope
-     - Global
-   * - Dynamic
-     - Yes
-   * - Data type
-     - Numeric
-   * - Default
-     - 0
-
-This variable works in combination with the
-:ref:`default_table_encryption` variable set to ``ONLINE_TO_KEYRING``.
-This variable
-configures the number of threads for background encryption. For the online
-encryption, the value must be greater than **zero**. 
-
-.. _innodb_online_encryption_rotate_key_age:
-
-.. rubric:: ``innodb_online_encryption_rotate_key_age``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--innodb-online-encryption-rotate-key-age``
-   * - Scope
-     - Global
-   * - Dynamic
-     - Yes
-   * - Data type
-     - Numeric
-   * - Default
-     - 1
-
-Defines the rotation for the re-encryption of a table encrypted using KEYRING.
-The value of this variable determines the how frequently the encrypted tables
-are re-encrypted.
-
-For example, the following values would trigger a re-encryption in the
-following intervals:
-
-*  The value is **1**, the table is re-encrypted on each key rotation. 
-*  The value is **2**, the table is re-encrypted on every other key rotation.
-*  The value is **10**, the table is re-encrypted on every tenth key rotation.
-
-You should select the value which best fits your operational requirements.
-
-.. _innodb_encryption_rotation_iops:
-
-.. rubric:: ``innodb_encryption_rotation_iops``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--innodb-encryption-rotation-iops``
-   * - Scope
-     - Global
-   * - Dynamic
-     - Yes
-   * - Data type
-     - Numeric
-   * - Default
-     - 100
-
-Defines the number of input/output operations per second (iops) available for
-use by a key rotation processes.
-
-.. _innodb_default_encryption_key_id:
-
-.. rubric:: ``innodb_default_encryption_key_id``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--innodb-default-encryption-key-id``
-   * - Scope
-     - Session
-   * - Dynamic
-     - Yes
-   * - Data type
-     - Numeric
-   * - Default
-     - 0
-    
-Defines the default encryption ID used to encrypt tablespaces.
-
-Using Keyring Encryption
--------------------------------------------
-
-:Availability: This feature is tech preview quality.
-
-Keyring management is enabled for each table, per file table, separately when
-you set encryption in the ``ENCRYPTION`` clause to ``KEYRING`` in the supported
-SQL statement.
-
-* CREATE TABLE ... ENCRYPTION='KEYRING'
-* ALTER TABLE ... ENCRYPTION='KEYRING'
-
-.. note::
-
-    Running an ``ALTER TABLE ... ENCRYPTION='N'`` on a table created with
-    ``ENCRYPTION='KEYRING'`` converts the table to the existing MySQL schema,
-    tablespace, or table encryption state. 
-
-.. seealso::
-
-    :ref:`using-keyring-plugin`
-
-
diff --git a/doc/source/security/encrypting-undo-tablespace.rst b/doc/source/security/encrypting-undo-tablespace.rst
deleted file mode 100644
index a46461ceaf87..000000000000
--- a/doc/source/security/encrypting-undo-tablespace.rst
+++ /dev/null
@@ -1,66 +0,0 @@
-.. _undo-tablespace-encryption:
-
-================================================================================
-Encrypting the Undo Tablespace
-================================================================================
-
-The undo data may contain sensitive information about the database operations.
-
-You can encrypt the data in an undo log using the
-:ref:`innodb_undo_log_encrypt` option. You can change the setting for this variable
-in the configuration file, as a startup parameter, or during runtime as a global
-variable. The undo data encryption must be enabled; the feature
-is disabled by default.
-
-.. _innodb_undo_log_encrypt:
-
-.. rubric:: ``innodb_undo_log_encrypt``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--innodb_undo-log_encrypt``
-   * - Scope
-     - Global
-   * - Dynamic
-     - Yes
-   * - Data type
-     - Boolean
-   * - Default
-     - OFF
-
-Defines if an undo log data is encrypted. The default for the undo log is
-"OFF", which disables the encryption.
-
-You can create up to 127 undo tablespaces and you can, with the server
-running, add or reduce the number of undo tablespaces.
-
-.. note::
-
-    If you disable encryption, any encrypted undo data remains encrypted. To
-    remove this data, truncate the undo tablespace.
-
-.. seealso::
-
-  *MySQL* Documentation
-  
-    `innodb_undo_log_encrypt
-    <https://dev.mysql.com/doc/refman/8.0/en/innodb-parameters.html#sysvar_innodb_undo_log_encrypt>`__
-
-How to Enable Encryption on an Undo Log
-----------------------------------------
-
-You enable encryption for an undo log by adding the following to the my.cnf
-file:
-
-.. code-block:: MySQL
-
-  [mysqld]
-  innodb_undo_log_encrypt=ON
-
-.. seealso::
-
-    :ref:`encrypting-redo-log`
diff --git a/doc/source/security/encryption-functions.rst b/doc/source/security/encryption-functions.rst
deleted file mode 100644
index 97e9460f7538..000000000000
--- a/doc/source/security/encryption-functions.rst
+++ /dev/null
@@ -1,478 +0,0 @@
-.. _encryption-functions:
-
-===============================================================================
-Encryption functions
-===============================================================================
-
-Percona Server for MySQL 8.0.28-20 adds encryption functions and variables to manage the encryption range. The functions may take an algorithm argument. Encryption converts plaintext into ciphertext using a key and an encryption algorithm.
-
-You can also use the user-defined functions with the PEM format keys generated externally by the OpenSSL utility.
-
-A digest uses plaintext and generates a hash value. This hash value can verify if the plaintext is unmodified. You can also sign or verify on digests to ensure that the original plaintext was not modified. You cannot decrypt the original text from the hash value.
-
-When choosing key lengths, consider the following:
-
-* Encryption strength increases with the key size and, also, the key generation time.
-
-* If performance is important and the functions are frequently used, use symmetric encryption. Symmetric encryption functions are faster than asymmetric encryption functions. Moreover, asymmetric encryption has restrictions on the maximum length of a message being encrypted. For example, for `RSA` the algorithm maximum message size is the key length in bytes (key length in bits / 8) minus 11. 
-
-The following table and sections describe the functions. For examples, see :ref:`function-examples`.
-
-.. list-table::
-   :header-rows: 1
-
-   * - Function Name
-   * - :ref:`asym_decrypt`
-   * - :ref:`asym_derive`
-   * - :ref:`asym_encrypt`
-   * - :ref:`asym_sign`
-   * - :ref:`asym_verify`
-   * - :ref:`create_priv_key`
-   * - :ref:`create_pub_key`
-   * - :ref:`create_dh_param`
-   * - :ref:`create_digest`
-
-The following table describes the :ref:`encryption_variables` which can be used to set the maximum value for a key length based on the type of encryption.
-
-.. list-table::
-   :header-rows: 1
-
-   * - Variable Name
-   * - :ref:`dh_threshold`
-   * - :ref:`dsa_threshold`
-   * - :ref:`rsa_threshold`
-
-.. _install_functions:
-
-Install `component_encryption_udf`
--------------------------------------------------
-
-Use the `Install Component Statement <https://dev.mysql.com/doc/refman/8.0/en/install-component.html>`__ to add the `component_encryption_udf` component. The functions and variables are available. The user-defined functions and the :ref:`encryption_variables` are auto-registered. There is no requirement to invoke ``CREATE FUNCTION ... SONAME ...``.
-
-The ``INSERT`` privilege on the ``mysql.component`` system table is required to run the ``INSTALL COMPONENT`` statement. To register the component, the operation adds a row to this table.
-
-The following is an example of the installation command:
-
-.. code-block:: mysql
-
-    mysql> INSTALL COMPONENT 'file://component_encryption_udf';
-
-.. note::
-  
-    If you are :ref:`compile_from_source`, the Encryption UDF component is built by default when Percona Server for MySQL is built. Specify the ``-DWITH_ENCRYPTION_UDF=OFF`` cmake option to exclude it.
-
-
-User-Defined Functions Described
-----------------------------------------------------
-
-.. _asym_decrypt:
-
-asymmetric_decrypt(*algorithm, crypt_str, key_str*)
------------------------------------------------------------
-
-Decrypts an encrypted string using the algorithm and a key string.
-
-.. rubric:: Returns
-
-A plaintext as a string.
-
-.. rubric:: Parameters
-
-The following are the function's parameters:
-
-* algorithm - the encryption algorithm supports `RSA` to decrypt the string.
-
-* key_str - a string in the PEM format. The key string must have the following attributes:
-
-  - Valid
-
-  - Public or private key string that corresponds with the private or public key string used with the :ref:`asymmetric_encrypt<asym_encrypt>` function.
-
-.. _asym_derive:
-
-asymmetric_derive(*pub_key_str, priv_key_str*)
-------------------------------------------------------------
-
-Derives a symmetric key using a public key generated on one side and a private key generated on another.
-
-.. rubric:: Returns
-
-A key as a binary string.
-
-.. rubric:: Parameters
-
-The ``pub_key_str`` must be a public key in the PEM format and generated using the Diffie-Hellman (DH) algorithm.
-
-The ``priv_key_str`` must be a private key in the PEM format and generated using the Diffie-Hellman (DH) algorithm.
-
-.. _asym_encrypt:
-
-asymmetric_encrypt(*algorithm, str, key_str*)
---------------------------------------------------------------
-
-Encrypts a string using the algorithm and a key string.
-
-.. rubric:: Returns
-
-A ciphertext as a binary string.
-
-.. rubric:: Parameters
-
-The parameters are the following:
-
-* algorithm - the encryption algorithm supports `RSA` to encrypt the string.
-
-* str - measured in bytes. The length of the string must not be greater than the key_str modulus length in bytes - 11 (additional bytes used for PKCS1 padding)
-
-* key_str - a key (either private or public) in the PEM format
-
-.. _asym_sign:
-
-asymmetric_sign(*algorithm, digest_str, priv_key_str, digest_type*)
-------------------------------------------------------------------------
-
-Signs a digest string using a private key string.
-
-.. rubric:: Returns
-
-A signature is a binary string.
-
-.. rubric:: Parameters
-
-The parameters are the following:
-
-* algorithm - the encryption algorithm supports either `RSA` or `DSA` to encrypt the string.
-
-* digest_str - the digest binary string that is signed. Invoking :ref:`create_digest<create_digest>` generates the digest.
-
-* priv_key_str - the private key used to sign the digest string. The key must be in the PEM format.
-
-* digest_type - the supported values are listed in the digest type table of :ref:`create_digest<create_digest>`.
-
-.. _asym_verify:
-
-asymmetric_verify(*algorithm, digest_str, sig_str, pub_key_str, digest_type*)
---------------------------------------------------------------------------------
-
-Verifies whether the signature string matches the digest string.
-
-.. rubric:: Returns
-
-A ``1`` (success) or a ``0`` (failure).
-
-.. rubric:: Parameters
-
-The parameters are the following:
-
-* algorithm - supports either 'RSA' or 'DSA'.
-
-* digest_str - invoking :ref:`create_digest<create_digest>` generates this digest binary string.
-
-* sig_str - the signature binary string. Invoking :ref:`asymmetric_sign<asym_sign>` generates this string.
-
-* pub_key_str - the signer's public key string. This string must correspond to the private key passed to :ref:`asymmetric_sign<asym_sign>` to generate the signature string. The string must be in the PEM format.
-
-* digest_type - the supported values are listed in the digest type table of :ref:`create_digest<create_digest>`
-
-.. _create_priv_key:
-
-create_asymmetric_priv_key(*algorithm, (key_len | dh_parameters)*)
---------------------------------------------------------------------------------
-
-Generates a private key using the given algorithm and key length for RSA or DSA
-or Diffie-Hellman parameters for DH. For RSA or DSA, if needed, execute ``KILL
-[QUERY|CONNECTION] <id>`` to terminate a long-lasting key generation. The
-DH key generation from existing parameters is a quick operation. Therefore, it
-does not make sense to terminate that operation with ``KILL``.
-
-.. rubric:: Returns
-
-The key as a string in the PEM format.
-
-.. rubric:: Parameters
-
-The parameters are the following:
-
-* algorithm - the supported values are 'RSA', 'DSA', or 'DH'.
-
-* key_len - the supported key length values are the following:
-
-  - RSA - the minimum length is 1,024. The maximum length is 16,384. 
-
-  - DSA - the minimum length is 1,024. The maximum length is 9,984. 
-
-    .. note:: The key length limits are defined by OpenSSL. To change the maximum key length, use either :ref:`rsa_threshold` or :ref:`dsa_threshold`.
-
-* dh_parameters - Diffie-Hellman (DH) parameters. Invoking :ref:`create_dh_parameter<create_dh_param>` creates the DH parameters.
-
-.. _create_pub_key:
-
-create_asymmetric_pub_key(*algorithm, priv_key_str*)
---------------------------------------------------------------------------
-
-Derives a public key from the given private key using the given algorithm.
-
-.. rubric:: Returns
-
-The key as a string in the PEM format.
-
-.. rubric:: Parameters
-
-The parameters are the following:
-
-* algorithm - the supported values are 'RSA', 'DSA', or 'DH'.
-
-* priv_key_str - must be a valid key string in the PEM format.
-
-.. _create_dh_param:
-
-create_dh_parameters(*key_len*)
---------------------------------------
-
-Creates parameters for generating a Diffie-Hellman (DH) private/public key pair.
-If needed, execute ``KILL [QUERY|CONNECTION] <id>`` to terminate the generation of long-lasting parameters.
-
-Generating the DH parameters can take more time than generating the RSA keys or
-the DSA keys.
-OpenSSL defines the parameter length limits. To change the
-maximum parameter length, use :ref:`dh_threshold`.
-
-.. rubric:: Returns
-
-A string in the PEM format and can be passed to :ref:`create_asymmetric_private_key<create_priv_key>`.
-
-.. rubric:: Parameters
-
-The parameters are the following:
-
-* key_len - the range for the key length is from 1024 to 10,000. The default value is 10,000.
-
-.. _create_digest:
-
-create_digest(*digest_type, str*)
---------------------------------------------
-
-Creates a digest from the given string using the given digest type. The digest string can be used with :ref:`asymmetric_sign<asym_sign>` and :ref:`asymmetric_verify<asym_verify>`.
-
-.. rubric:: Returns
-
-The digest of the given string as a binary string
-
-.. rubric:: Parameters
-
-The parameters are the following:
-
-* digest_type - the supported values are the following (based on the OpenSSL version):
-
-  .. list-table::
-      :header-rows: 1
-
-      * - Value Name for OpenSSL 1.0.2
-        - Value Name for OpenSSL 1.1.x addition
-      * - 'MD5'
-        - 'BLAKE2B512'
-      * - 'SHA1'
-        - 'BLAKE2S256'
-      * - 'SHA224'
-        - 'RIPEMD'
-      * - 'SHA256'
-        - 'RMD160'
-      * - 'SHA384'
-        - 'SHAKE128'
-      * - 'SHA512'
-        - 'SHAKE256'
-      * - 'MD4'
-        - 'SM3'
-      * - 'RIPEMD160'
-        - 'WHIRLPOOL'
-
-* str - String used to generate the digest string.
-
-.. _encryption_variables:
-
-.. rubric:: Encryption threshold variables
-
-The maximum key length limits are defined by OpenSSL. Server administrators can limit the maximum key length using the encryption threshold variables. 
-
-The variables are automatically registered when `component_encryption_udf` is installed.
-
-
-.. list-table::
-   :header-rows: 1
-
-   * - Variable Name
-   * - :ref:`dh_threshold`
-
-.. _dh_threshold:
-
-.. rubric:: ``encryption_udf.dh_bits_threshold``
-
-The variable sets the maximum limit for the :ref:`create_dh_parameters <create_dh_param>` user-defined function and takes precedence over the OpenSSL maximum length value.
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - command-line
-     - Yes
-   * - scope
-     - Global
-   * - data type
-     - unsigned integer
-   * - default
-     - 10000
-
-The range for this variable is from 1024 to 10,000. The default value is 10,000.
-
-.. _dsa_threshold:
-
-.. rubric:: `encryption_udf.dsa_bits_threshold`
-
-The variable sets the threshold limits for :ref:`create_asymmetric_priv_key <create_priv_key>` user-defined function when the function is invoked with the `DSA` parameter and takes precedence over the OpenSSL maximum length value.
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - command-line
-     - Yes
-   * - scope
-     - Global
-   * - data type
-     - unsigned integer
-   * - default
-     - 9984
-
-
-The range for this variable is from 1,024 to 9,984. The default value is 9,984.
-
-.. _rsa_threshold:
-
-.. rubric:: `encryption_udf.rsa_bits_threshold`
-
-The variable sets the threshold limits for the :ref:`create_asymmetric_priv_key <create_priv_key>` user-defined function when the function is invoked with the `RSA` parameter and takes precedence over the OpenSSL maximum length value.
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - command-line
-     - Yes
-   * - scope
-     - Global
-   * - data type
-     - unsigned integer
-   * - default
-     - 16384
-
-The range for this variable is from 1,024 to 16,384. The default value is 16,384.
-
-.. _function_examples:
-
-.. rubric:: Examples
-
-Code examples for the following operations: 
-
-* set the threshold variables
-* create a private key 
-* create a public key
-* encrypt data
-* decrypt data
-
-
-.. code-block:: mysql
-
-    -- Set Global variable
-    mysql> SET GLOBAL encryption_udf.dh_bits_threshold = 4096;
-
-    -- Set Global variable
-    mysql> SET GLOBAL encryption_udf.rsa_bits_threshold = 4096;
-
-.. code-block:: mysql
-
-    -- Create private key
-    mysql> SET @private_key = create_asymmetric_priv_key('RSA', 3072);
-
-    -- Create public key
-    mysql> SET @public_key = create_asymmetric_pub_key('RSA', @private_key);
-
-    -- Encrypt data using the private key (you can also use the public key)
-    mysql> SET @ciphertext = asymmetric_encrypt('RSA', 'This text is secret', @private_key);
-
-    -- Decrypt data using the public key (you can also use the private key)
-    -- The decrypted value @plaintext should be identical to the original 'This text is secret'
-    mysql> SET @plaintext = asymmetric_decrypt('RSA', @ciphertext, @public_key);
-
-Code examples for the following operations: 
-
-* generate a digest string
-
-* generate a digest signature
-
-* verify the signature against the digest
-
-
-.. code-block:: mysql
-
-   -- Generate a digest string
-   mysql> SET @digest = create_digest('SHA256', 'This is the text for digest');
-
-   -- Generate a digest signature
-   mysql> SET @signature = asymmetric_sign('RSA', @digest, @private_key, 'SHA256');
-
-   -- Verify the signature against the digest
-   -- The @verify_signature must be equal to 1
-   mysql> SET @verify_signature = asymmetric_verify('RSA', @digest, @signature, @public_key, 'SHA256');
-
-Code examples for the following operations:
-
-* generate a DH parameter
-* generates two DH key pairs
-* generate a symmetric key using the public_1 and the private_2
-* generate a symmetric key using the public_2 and the private_1
-
-.. code-block:: mysql
-
-   -- Generate a DH parameter
-   mysql> SET @dh_parameter = create_dh_parameters(3072);
-
-   -- Generate DH key pairs
-   mysql> SET @private_1 = create_asymmetric_priv_key('DH', @dh_parameter);
-   mysql> SET @public_1 = create_asymmetric_pub_key('DH', @private_1);
-   mysql> SET @private_2 = create_asymmetric_priv_key('DH', @dh_parameter);
-   mysql> SET @public_2 = create_asymmetric_pub_key('DH', @private_2);
-
-  -- Generate a symmetric key using the public_1 and private_2
-  -- The @symmetric_1 must be identical to @symmetric_2
-  mysql> SET symmetric_1 = asymmetric_derive(@public_1, @private_2);
-
-  -- Generate a symmetric key using the public_2 and private_1
-  -- The @symmetric_2 must be identical to @symmetric_1
-  mysql> SET symmetric_2 = asymmetric_derive(@public_2, @private_1);
-
-Code examples for the following operations: 
-
-* create a private key using a ``SET`` statement
-* create a private key using a  ``SELECT`` statement
-* create a private key using an ``INSERT`` statement
-
-.. code-block:: mysql
-
-  mysql> SET @private_key1 = create_asymmetric_priv_key('RSA', 3072);
-  mysql> SELECT create_asymmetric_priv_key('RSA', 3072) INTO @private_key2;
-  mysql> INSERT INTO key_table VALUES(create_asymmetric_priv_key('RSA', 3072));
-
-
-.. _uninstall_functions:
-
-Uninstall `component_encryption_udf`
----------------------------------------
-
-You can deactivate and uninstall the component using the `Uninstall Component statement <https://dev.mysql.com/doc/refman/8.0/en/uninstall-component.html>`__.
-
-.. code-block:: mysql
-
-  mysql> UNINSTALL COMPONENT 'file://component_encryption_udf';
diff --git a/doc/source/security/pam_plugin.rst b/doc/source/security/pam_plugin.rst
deleted file mode 100644
index 92014b2e9b95..000000000000
--- a/doc/source/security/pam_plugin.rst
+++ /dev/null
@@ -1,91 +0,0 @@
-.. _pam_plugin:
-
-===========================
- PAM Authentication Plugin
-===========================
-
-Percona PAM Authentication Plugin is a free and Open Source implementation of the *MySQL*'s authentication plugin. This plugin acts as a mediator between the *MySQL* server, the *MySQL* client, and the PAM stack. The server plugin requests authentication from the PAM stack, forwards any requests and messages from the PAM stack over the wire to the client (in cleartext) and reads back any replies for the PAM stack.
-
- PAM plugin uses dialog as its client side plugin. Dialog plugin can be loaded to any client application that uses :file:`libperconaserverclient`/:file:`libmysqlclient` library.
-
-Here are some of the benefits that Percona dialog plugin offers over the default one:
-
-  * It correctly recognizes whether PAM wants input to be echoed or not, while the default one always echoes the input on the user's console.
-  * It can use the password which is passed to *MySQL* client via "-p" parameter.
-  * Dialog client `installation bug <https://bugs.mysql.com/bug.php?id=60745>`_ has been fixed.
-  * This plugin works on *MySQL* and *Percona Server for MySQL*.
-
-Percona offers two versions of this plugin:  
-
-  * Full PAM plugin called *auth_pam*. This plugin uses *dialog.so*. It fully supports the PAM protocol with arbitrary communication between client and server.
-  * Oracle-compatible PAM called *auth_pam_compat*. This plugin uses *mysql_clear_password* which is a part of Oracle MySQL client. It also has some limitations, such as, it supports only one password input. You must use ``-p`` option in order to pass the password to *auth_pam_compat*.
-
-These two versions of plugins are physically different. To choose which one you want used, you must use *IDENTIFIED WITH 'auth_pam'* for auth_pam, and *IDENTIFIED WITH 'auth_pam_compat'* for auth_pam_compat.
-
-Installation
-============
-
-This plugin requires manual installation because it isn't installed by default. :: 
-
- mysql> INSTALL PLUGIN auth_pam SONAME 'auth_pam.so';
- 
-After the plugin has been installed it should be present in the plugins list. To check if the plugin has been correctly installed and active :: 
-
- mysql> SHOW PLUGINS;
- ...
- ...
- | auth_pam                       | ACTIVE   | AUTHENTICATION     | auth_pam.so | GPL     |
-
-Configuration
-=============
-
-In order to use the plugin, authentication method should be configured. Simple setup can be to use the standard UNIX authentication method (``pam_unix``).
-
-.. note:: 
-
-  To use ``pam_unix``, mysql will need to be added to the shadow group in order to have enough privileges to read the /etc/shadow.
-
-A sample `/etc/pam.d/mysqld` file: ::
-
-  auth       required     pam_unix.so
-  account    required     pam_unix.so
-
-For added information in the system log, you can expand it to be: ::
-
-  auth       required     pam_warn.so
-  auth       required     pam_unix.so audit
-  account    required     pam_unix.so audit
-
-Creating a user
-================
-
-After the PAM plugin has been configured, users can be created with the PAM plugin as authentication method :: 
-
-  mysql> CREATE USER 'newuser'@'localhost' IDENTIFIED WITH auth_pam;
-
-This will create a user ``newuser`` that can connect from ``localhost`` who will be authenticated using the PAM plugin. If the ``pam_unix`` method is being used user will need to exist on the system.
-
-Supplementary groups support
-============================
-
-*Percona Server for MySQL* has implemented PAM plugin support for supplementary groups. Supplementary or secondary groups are extra groups a specific user is member of. For example user ``joe`` might be a member of groups: ``joe`` (his primary group) and secondary groups ``developers`` and ``dba``. A complete list of groups and users belonging to them can be checked with ``cat /etc/group`` command.
-
-This feature enables using secondary groups in the mapping part of the authentication string, like "``mysql, developers=joe, dba=mark``". Previously only primary groups could have been specified there. If user is a member of both ``developers`` and ``dba``, PAM plugin will map it to the ``joe`` because ``developers`` matches first. 
-
-Known issues
-============
-
-Default mysql stack size is not enough to handle ``pam_ecryptfs`` module. Workaround is to increase the *MySQL* stack size by setting the `thread-stack <https://dev.mysql.com/doc/refman/8.0/en/server-system-variables.html#sysvar_thread_stack>`_ variable to at least ``512KB`` or by increasing the old value by ``256KB``.
-
-PAM authentication can fail with ``mysqld: pam_unix(mysqld:account): Fork failed: Cannot allocate memory`` error in the :file:`/var/log/secure` even when there is enough memory available. Current workaround is to set `vm.overcommit_memory <https://www.kernel.org/doc/Documentation/vm/overcommit-accounting>`_ to ``1``:
-
-.. code-block:: bash
-
-   echo 1 > /proc/sys/vm/overcommit_memory
-
-and by adding the ``vm.overcommit_memory = 1`` to :file:`/etc/sysctl.conf` to make the change permanent after reboot. Authentication of internal (i.e. non PAM) accounts continues to work fine when ``mysqld`` reaches this memory utilization level. *NOTE:* Setting the ``vm.overcommit_memory`` to ``1`` will cause kernel to perform no memory overcommit handling which could increase the potential for memory overload and invoking of OOM killer. 
-
-Version Specific Information
-============================
-
-  * :ref:`8.0.12-1`: The feature was ported from *Percona Server for MySQL* 5.7.
diff --git a/doc/source/security/rotating-master-key.rst b/doc/source/security/rotating-master-key.rst
deleted file mode 100644
index 60cc85cb48e8..000000000000
--- a/doc/source/security/rotating-master-key.rst
+++ /dev/null
@@ -1,33 +0,0 @@
-.. _rotating-master-key:
-
-==============================================================================
-Rotating the Master Key
-==============================================================================
-
-The Master key should be periodically rotated. You should rotate the key if you
-believe the key has been compromised. The Master key rotation changes the Master
-key and tablespace keys are re-encrypted and updated in the tablespace headers.
-The operation does not affect tablespace data.
-
-If the master key rotation is interrupted, the rotation operation is rolled
-forward when the server restarts. InnoDB reads the encryption data from the
-tablespace header, if certain tablespace keys have been encrypted with the prior
-master key, InnoDB retrieves the master key from the keyring to decrypt the
-tablespace key. InnoDB re-encrypts the tablespace key with the new Master key.
-
-To allow for Master Key rotation, you can encrypt an already encrypted InnoDB
-system tablespace with a new master key by running the following ``ALTER
-INSTANCE`` statement:
-
-.. code-block:: mysql
-
-   mysql> ALTER INSTANCE ROTATE INNODB MASTER KEY;
-
-The rotation operation must complete before any tablespace encryption operation
-can begin.
-
-.. note::
-
-    The rotation re-encrypts each tablespace key. The tablespace key is not
-    changed. If you want to change a tablespace key, you should disable and then
-    re-enable encryption.
diff --git a/doc/source/security/selinux.rst b/doc/source/security/selinux.rst
deleted file mode 100644
index 4254237faaa7..000000000000
--- a/doc/source/security/selinux.rst
+++ /dev/null
@@ -1,590 +0,0 @@
-.. _selinux:
-
-===========================
-Working with SELinux
-===========================
-
-The Linux kernel, through the Linux Security Module (LSM), supports Security-Enhanced Linux (SELinux). This module provides a way to support mandatory access control policies. SELinux defines how confined processes interact with files, network ports, directories, other processes, and additional server components. 
-
-An SELinux policy defines the set of rules, the ``types`` for files, and the ``domains`` for processes. Rules determine how a process interacts with another type. SELinux decides whether to allow or deny an action based on the subject's context, what object initiates the action and what object is the action's target. 
-
-A label represents the context for administrators and users. 
-
-CentOS 7 and CentOS 8 contain a MySQL SELinux policy. *Percona Server for MySQL* is a drop-in replacement for MySQL and can use this policy without changes. 
-
-SELinux context example
-------------------------------
-
-To view the SELinux context, add the ``-Z`` switch to many of the utilities. Here is an example of the context for ``mysqld``:
-
-    .. sourcecode:: bash
-
-        $ ps -eZ | grep mysqld_t
-        system_u:system_r:mysqld_t:s0    3356 ?        00:00:01 mysqld
-
-The context has the following properties:
-
-* User - system_u
-
-* Role - system_r
-
-* Type or domain - mysqld_t
-
-* Sensitivity level - s0    3356
-
-Most SELinux policy rules are based on the type or domain. 
-
-List SELinux Types or Domains associated with files
-----------------------------------------------------
-
-The security property that SELinux relies on is the Type security property. The type name often end with a ``_t``. A group of objects with the same type security value belongs to the same domain. 
-
-To view the ``mysqldb_t`` types associated with the MySQL directories and files, run the following command:
-
-    .. sourcecode:: bash
-
-        $ ls -laZ /var/lib/ | grep mysql
-        drwxr-x--x. mysql   mysql   system_u:object_r:mysqld_db_t:s0 mysql
-        drwxr-x---. mysql   mysql   system_u:object_r:mysqld_db_t:s0 mysql-files
-        drwxr-x---. mysql   mysql   system_u:object_r:mysqld_db_t:s0 mysql-keyring
-
-.. note::
-
-    If a policy type does not define the type property for an object, the default value is ``unconfined_t``. 
-
-SELinux modes
--------------
-
-SELinux has the following modes:
-
-* Disabled - No SELinux policy modules loaded, which disables policies. Nothing is reported.
-
-* Permissive - SELinux is active, but policy modules are not enforced. A policy violation is reported but does not stop the action. 
-
-* Enforcing - SELinux is active, and violations are reported and denied. If there is no rule to allow access to a confined resource, SELinux denies the access.
-
-Policy Types 
-----------------
-
-SELinux has several policy types:
-
-* Targeted - Most processes operate without restriction. Specific services are contained in security domains and defined by policies.
-
-* Strict - All processes are contained in security domains and defined by policies.
-
-SELinux has confined processes that run in a domain and restricts everything unless explicitly allowed. An unconfined process in an unconfined domain is allowed almost all access. 
-
-MySQL is a confined process, and the policy module defines which files are read, which ports are opened, and so on. SELinux assumes the *Percona Server for MySQL* installation uses the default file locations and default ports. 
-
-If you change the default, you must also edit the policy. If you do not update the policy, SELinux, in enforcing mode, denies access to all non-default resources.
-
-Check the SELinux mode
----------------------------
-
-To check the current SELinux mode, use either of the following commands:
-
-    .. sourcecode:: bash
-
-        $ sestatus
-        SELinux status:                 enabled
-        SELinuxfs mount:                /sys/fs/selinux
-        SELinux root directory:         /etc/selinux
-        Loaded policy name:             targeted
-        Current mode:                   enforcing
-        Mode from config file:          enforcing
-        Policy MLS status:              enabled
-        Policy deny_unknown status:     allowed
-        Memory protection checking:     actual (secure)
-        Max kernel policy version:      31
-
-or 
-
-    .. sourcecode:: bash
-
-        $ grep ^SELINUX= /etc/selinux/config
-        SELINUX=enforcing
-
-    .. note:: Add the ``-b`` parameter to ``sestatus`` to display the ``Policy booleans``. The boolean values for each parameter is shown. An example of using the ``b`` parameter is the following:
-
-        .. sourcecode:: bash
-
-            $ sestatus -b | grep mysql
-            mysql_connect_any                           off
-            selinuxuser_mysql_connect_enabled
-
-
-The ``/etc/selinux/config`` file controls if SELinux is disabled or enabled, and if enabled, whether SELinux operates in enforcing mode or permissive mode.
-
-
-
-
-Disable SELinux
-------------------
-
-If you plan to use the enforcing mode at another time, use the permissive mode instead of disabling SELinux. During the time that SELinux is disabled, the system may contain mislabeled objects or objects with no label. If you re-enable SELinux and plan to set SELinux to enforcing, you must follow the steps to :ref:`relabel`.
-
-On boot, to disable SELinux, set the ``selinux=0`` kernel option. The kernel does not load the SELinux infrastructure. This option has the same effect as changing the ``SELINUX=disabled`` instruction in the configuration file and then rebooting the system. 
-
-Additional SELinux tools
----------------------------------
-
-Install the SELinux management tools, such as ``semanage`` or ``sesearch``, if needed. 
-
-On RHEL 7 or compatible operating systems, use the following command as root:
-
-    .. sourcecode:: bash
-
-        $ yum -y install policycoreutils-python
-
-On RHEL 8 or compatible operating systems, use the following command as root:
-
-    .. sourcecode:: bash
-
-        $ yum -y install policycoreutils-python-utils 
-
-.. note:: You may need root privileges to run SELinux management commands.
-
-.. _changing-selinux-mode:
-
-Switch the mode in the configuration file
-------------------------------------------------------
-
-Switching between modes may help when troubleshooting or when modifying rules. 
-
-To permanently change the mode, edit the ``/etc/selinux/config`` file and change the ``SELINUX=`` value. You should also verify the change. 
-
-    .. sourcecode:: bash
-
-        $ cat /etc/selinux/config | grep SELINUX= | grep -v ^#
-        SELINUX=enforcing
-        SELINUX=enforcing
-
-        $ sudo sed -i 's/^SELINUX=.*/SELINUX=permissive/g' /etc/selinux/config
-
-        $ cat /etc/selinux/config | grep SELINUX= | grep -v ^#
-        SELINUX=permissive
-        SELINUX=permissive
-
-Reboot your system after the change.
-
-If switching from either disabled mode or permissive mode to enforcing, see :ref:`relabel`.
-
-Switch the mode until the next reboot
------------------------------------------
-
-To change the mode until the next reboot, use either of the following commands as root:
-
-    .. sourcecode:: bash
-
-        $ setenforce Enforcing
-
-or 
-
-    .. sourcecode:: bash
-
-        $ setenforce 1
-
-    .. note:: The following ``setenforce`` parameters are available:
-
-            +-----------------------+----------------+
-            | setenforce parameters | Also Permitted |
-            +=======================+================+
-            | 0                     | Permissive     |
-            +-----------------------+----------------+
-            | 1                     | Enforcing      |
-            +-----------------------+----------------+
-
-You can view the current mode by running either of the following commands:
-
-    .. sourcecode:: bash
-
-        $ getenforce
-        Enforcing
-
-or 
-
-    .. sourcecode:: bash
-
-        $ sestatus | grep -i mode
-        Current mode:                   permissive
-        Mode from config file:          enforcing
-
-
-Switch the mode for a service
----------------------------------
-
-You can move one or more services into a permissive domain. The other services remain in enforcing mode. 
-
-To add a service to the permissive domain, run the following as root:
-
-    .. sourcecode:: bash
-
-        $ sudo semanage permissive -a mysqld_t
-
-To list the current permissive domains, run the following command:
-
-    .. sourcecode:: bash
-
-        $ sudo semanage permissive -l 
-        ...
-        Customized Permissive Types
-
-        mysqld_t
-
-        Builtin Permissive Types
-
-To delete a service from the permissive domain, run the following:
-
-    .. sourcecode:: bash
-
-        $ sudo semanage permissive -d mysqld_t
-
-The service returns to the system's SELinux mode. Be sure to follow the steps to :ref:`relabel`.
-
-.. _relabel:
-
-Relabel the entire file system
--------------------------------------
-
-Switching from disabled or permissive to enforcing requires additional steps. The enforcing mode requires the correct contexts, or labels, to function. The permissive mode allows users and processes to label files and system objects incorrectly. The disabled mode does not load the SELinux infrastructure and does not label resources or processes. 
-
-RHEL and compatible systems, use the ``fixfiles`` application for relabeling. You can relabel the entire file system or the file contexts of an application. 
-
-For one application, run the following command:
-
-    .. sourcecode:: bash
-
-        $ fixfiles -R mysqld restore
-
-To relabel the file system without rebooting the system, use the following command:
-
-    .. sourcecode:: bash
-
-        $ fixfiles -f -F relabel
-
-Another option relabels the file system during a reboot. You can either add a touch file, read during the reboot operation, or configure a kernel boot parameter. The completion of the relabeling operation automatically removes the touch file.
-
-Add the touch file as root:
-
-    .. sourcecode:: bash
-
-        $ touch /.autorelabel
-
-To configure the kernel, add the ``autorelabel=1`` kernel parameter to the boot parameter list. The parameter forces a system relabel. Reboot in permissive mode to allow the process to complete before changing to enforcing. 
-
-.. note:: Relabeling an entire filesystem takes time. When the relabeling is complete, the system reboots again. 
-
-.. _selinux-custom-data-directory:
-
-Set a Custom Data directory
---------------------------------
-
-If you do not use the default settings, SELinux, in enforcing mode, prevents access to the system.
-
-For example, during installation, you have used the following configuration:
-
-    .. sourcecode:: text
-
-        datadir=/var/lib/mysqlcustom
-        socket=/var/lib/mysqlcustom/mysql.sock
-
-Restart the service.
-
-    .. sourcecode:: bash
-
-        $ service mysqld restart
-        Redirecting to /bin/systemctl restart mysqld.service
-        Job for mysqld.service failed because the control process exited with error code.
-        See "systemctl status mysqld.service" and "journalctl -xe" for details.
-
-Check the journal log to see the error code.
-
-    .. sourcecode:: bash
-
-        $ journalctl -xe
-        ...
-        SELinux is preventing mysqld from getattr access to the file /var/lib/mysqlcustom/ibdata1.
-        ... 
-
-Check the SELinux types in ``/var/lib/mysqlcustom``.
-
-    .. sourcecode:: bash
-
-        ls -1aZ /var/lib/mysqlcustom
-        total 164288
-        drwxr-x--x.  6 mysql mysql system_u:object_r:var_lib_t:s0       4096 Dec  2 07:58  .
-        drwxr-xr-x. 38 root  root  system_u:object_r:var_lib_t:s0       4096 Dec  1 14:29  ..
-        ...
-        -rw-r-----.  1 mysql mysql system_u:object_r:var_lib_t:s0   12582912 Dec  1 14:29  ibdata1
-        ...
-
-To solve the issue, use the following methods:
-
-* Set the proper labels for ``mysqlcustom`` files
-
-* Change the mysqld SELinux policy to allow mysqld access to ``var_lib_t`` files.
-
-The recommended solution is to set the proper labels. The following procedure assumes you have already created and set ownership to the custom data directory location:
-
-1. To change the SELinux context, use ``semanage fcontext``. In this step, you define how SELinux deals with the custom paths:
-
-    .. sourcecode:: bash
-
-        $ semanage fcontext -a -e /var/lib/mysql /var/lib/mysqlcustom
-
-    SELinux applies the same labeling schema, defined in the mysqld policy, for the ``/var/lib/mysql`` directory to the custom directory. Files created within the custom directory are labeled as if they were in ``/var/lib/mysql``. 
-
-2. To ``restorecon`` command applies the change. 
-
-    .. sourcecode:: bash
-
-        $ restorecon -R -v /var/lib/mysqlcustom
-
-3. Restart the mysqld service:
-
-    .. sourcecode:: bash
-
-        $ service mysqld start
-
-.. _selinux-custom-logs:
-
-Set a Custom Log Location 
-------------------------------
-
-If you do not use the default settings, SELinux, in enforcing mode, prevents access to the location. Change the log location to a custom location in my.cnf:
-
-    .. sourcecode:: text
-
-        log-error=/logs/mysqld.log
-
-Verify the log location with the following command:
-
-    .. sourcecode:: bash
-
-        $ ls -laZ /
-        ...
-        drwxrwxrwx.   2 root root unconfined_u:object_r:default_t:s0    6 Dec  2 09:16 logs
-        ...
-
-Starting MySQL returns the following message:
-
-    .. sourcecode:: bash
-
-        $ service mysql start
-        Redirecting to /bin/systemctl start mysql.service
-        Job for mysqld.service failed because the control process exited with error code.
-        See "systemctl status mysqld.service" and "journalctl -xe" for details.
-
-        $ journalctl -xe
-        ...
-        SELinux is preventing mysqld from write access to the directory logs.
-        ...
-
-The default SELinux policy allows mysqld to write logs into a location tagged with ``var_log_t``, which is the ``/var/log`` location. You can solve the issue with either of the following methods:
-
-* Tag the ``/logs`` location properly
-
-* Edit the SELinux policy to allow mysqld access to all directories.
-
-To tag the custom ``/logs`` location is the recommended method since it locks down access. Run the following commands to tag the custom location:
-
-    .. sourcecode:: bash
-
-        $ semanage fcontext -a -t var_log_t /logs
-        $ restorecon -v /logs
-
-You may not be able to change the ``/logs`` directory label. For example, other applications, with their own rules, use the same directory. 
-
-To adjust the SELinux policy when a directory is shared, follow these steps:
-
-1. Create a local policy:
-
-    .. sourcecode:: bash
-
-        ausearch -c 'mysqld' --raw | audit2allow -M my-mysqld
-
-2. This command generates the my-mysqld.te and the my-mysqld.pp files. The mysqld.te is the type enforcement policy file. The my-mysqld.pp is the policy module loaded as a binary file into the SELinux subsystem.
-
-    An example of the my-myslqd.te file:
-
-    .. sourcecode:: text
-
-        module my-mysqld 1.0;
-
-        require {
-            *type mysqld_t*;
-            type var_lib_t;
-            *type default_t*;
-            class file getattr;
-            *class dir write*;
-        }
-
-        #============= mysqld_t ==============
-        *allow mysqld_t default_t:dir write*;
-        allow mysqld_t var_lib_t:file getattr;
-
-    The policy contains rules for the custom data directory and the custom logs directory. We have set the proper labels for the data directory location, and applying this autogenerated policy would loosen our hardening by allowing mysqld to access ``var_lib_t`` tags. 
-
-3. SELinux-generated events are converted to rules. A generated policy may contain rules for recent violations and include unrelated rules. Unrelated rules are generated from actions, such as changing the data directory location, that are not related to the logs directory. Add the ``--start`` parameter to use log events after a specific time to filter out the unwanted events. This parameter captures events when the time stamp is equal to the specified time or later. SELinux generates a policy for the current actions.
-
-    .. sourcecode:: bash
-
-        $ ausearch --start 10:00:00 -c 'mysqld' --raw | audit2allow -M my-mysqld
-
-4. This policy allows mysqld writing into the tagged directories. Open the my_mysqld file:
-
-    .. sourcecode:: text
-
-        module my-mysqld 1.0;
-
-        require {
-            type mysqld_t;
-            type default_t;
-            class dir write;
-        }
-
-        #============= mysqld_t ==============
-        allow mysqld_t default_t:dir write;
-
-5. Install the SELinux policy module:
-
-    .. sourcecode:: bash
-
-        $ semodule -i my-mysqld.pp
-
-Restart the service. If you have a failure, check the journal log and follow the same procedure.
-
-If SELinux prevents mysql from creating a log file inside the directory. You can view all the violations by changing the SELinux mode to ``permissive`` and then running mysqld. All violations are logged in the journal log. After this run, you can generate a local policy module, install it, and switch SELinux back to ``enforcing`` mode. Follow this procedure:
-
-1. Unload the current local my-mysqld policy module:
-
-    .. sourcecode:: bash
-
-        $ semodule -r my-mysqld
-
-2. You can put a single domain into permissive mode. Other domains on the system to remain in enforcing mode. Use ``semanage permissive`` with the ``-a`` parameter to change mysqld_t to permissive mode:
-
-    .. sourcecode:: bash
-
-        $ semanage permissive -a mysqld_t
-
-3. Verify the mode change:
-
-    .. sourcecode:: bash
-
-        semdule -l | grep permissive
-        ...
-        permissive_mysqld_t
-        ...
-
-4. To make searching the log easier, return the time:
-
-    .. sourcecode:: bash
-
-        $ date
-
-5. Start the service.
-
-    .. sourcecode:: bash
-
-        $ service mysqld start
-
-6. MySQL starts, and SELinux logs the violations in the journal log. Check the journal log:
-
-    .. sourcecode:: bash
-
-        $ journalctl -xe
-
-7. Stop the service:
-
-    .. sourcecode:: bash
-
-        $ service mysqld stop 
-
-8. Generate a local mysqld policy, using the time returned from step 4:
-
-    .. sourcecode:: bash
-
-        $ ausearch --start <date> -c 'mysqld' --raw | audit2allow -M my-mysqld
-
-9. Review the policy (the policy you generate may be different):
-
-    .. sourcecode:: bash
-
-        $ cat my-mysqld.te
-        module my-mysqld 1.0;
-
-        require {
-        type default_t;
-            type mysqld_t;
-            class dir { add_name write };
-            class file { append create open };
-        }
-
-        #============= mysqld_t ==============
-        allow mysqld_t default_t:dir { add_name write };
-        allow mysqld_t default_t:file { append create open };
-
-10. Install the policy:
-
-    .. sourcecode:: bash
-
-        $ semodule -i my-mysqld.pp
-
-11. Use ``semanage permissive`` with the ``-d`` parameter, which deletes the permissive domain for the service:
-
-    .. sourcecode:: bash
-
-        $ semanage permissive -d mysqld_t
-
-12. Restart the service:
-
-    .. sourcecode:: bash
-
-            $ service mysqld start
-
-.. note::
-
-    Use this procedure to adjust the local mysqld policy module. You should review the changes which are generated to ensure the rules are not too tolerant.
-
-.. _selinux-secure-file-priv:
-
-Set ``secure_file_priv`` directory
----------------------------------------
-
-Update the SELinux tags for the ``/var/lib/mysql-files/`` directory, used for ``SELECT ... INTO OUTFILE`` or similar operations, if required. The server needs only read/write access to the destination directory.
-
-To set ``secure_file_priv`` to use this directory, run the following commands to set the context:
-
-    .. sourcecode:: bash
-
-        $ semanage fcontext -a -t mysqld_db_t "/var/lib/mysql-files/(/.*)?"
-        $ restorecon -Rv /var/lib/mysql-files
-
-Edit the path for a different location, if needed.
-
-.. seealso::
-
-    `SELinux and MySQL <https://blogs.oracle.com/mysql/selinux-and-mysql-v2>`_
-
-    `Red Hat SELinux User's and Administrator's Guide <https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/selinux_users_and_administrators_guide/index>`_
-
-    `CentOS HowTos SELinux <https://wiki.centos.org/HowTos/SELinux>`_
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/doc/source/security/simple-ldap-variables.rst b/doc/source/security/simple-ldap-variables.rst
deleted file mode 100644
index d5dc766f13a0..000000000000
--- a/doc/source/security/simple-ldap-variables.rst
+++ /dev/null
@@ -1,206 +0,0 @@
-.. _simple_ldap_variables:
-
-=========================================================
-Simple LDAP Variables
-=========================================================
-
-The following variables are static and can only be changed at runtime.
-
-.. tabularcolumns:: |p{10cm}|p{2cm}|p{2cm}|p{2cm}|
-
-.. list-table::
-   :header-rows: 1
-   
-   * - Name
-     - Command Line
-     - Dynamic
-     - Scope
-   * - :ref:`authentication_ldap_simple_bind_root_dn`
-     - Yes
-     - No
-     - Global
-   * - :ref:`authentication_ldap_simple_bind_root_pwd`
-     - Yes
-     - No
-     - Global
-   * - :ref:`authentication_ldap_simple_ca_path`
-     - Yes
-     - No
-     - Global
-   * - :ref:`authentication_ldap_simple_server_host`
-     - Yes
-     - No
-     - Global
-   * - :ref:`authentication_ldap_simple_server_port`
-     - Yes
-     - No
-     - Global
-   * - :ref:`authentication_ldap_simple_ssl`
-     - Yes
-     - No
-     - Global
-   * - :ref:`authentication_ldap_simple_tls`
-     - Yes
-     - No
-     - Global
-     
-.. _authentication_ldap_simple_bind_root_dn:
-
-.. rubric:: ``authentication_ldap_simple_bind_root_dn``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--authentication-ldap-simple-bind-root-dn=value``
-   * - Scope
-     - Global
-   * - Dynamic
-     - No
-   * - Data type
-     - String
-   * - Default
-     - Null
-
-The ``root`` credential used to authenticate against an LDAP. This variable is used with
-``authentication_ldap_simple_bind_root_pwd``.
-
-.. _authentication_ldap_simple_bind_root_pwd:
-
-.. rubric:: ``authentication_ldap_simple_bind_root_pwd``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--authentication-ldap-simple-bind-root-pwd=value``
-   * - Scope
-     - Global
-   * - Dynamic
-     - No
-   * - Data type
-     - String
-   * - Default
-     - Null
-    
-The ``root`` password used to authenticate against an LDAP. This variable is used with
-``authentication_ldap_simple_bind_root_dn``.
-
-.. _authentication_ldap_simple_ca_path:
-
-.. rubric:: ``authentication_ldap_simple_ca_path``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--authentication-ldap-simple-ca_path=value``
-   * - Scope
-     - Global
-   * - Dynamic
-     - No
-   * - Data type
-     - String
-   * - Default
-     - Null
-    
-The certificate authority's absolute path used to verify the LDAP certificate.
-
-.. _authentication_ldap_simple_server_host:
-
-.. rubric:: ``authentication_ldap_simple_server_host``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--authentication-ldap-simple-server-host=value``
-   * - Scope
-     - Global
-   * - Dynamic
-     - No
-   * - Data type
-     - String
-   * - Default
-     - Null
-    
-The LDAP server host used for LDAP authentication.
-
-.. _authentication_ldap_simple_server_port:
-
-.. rubric:: ``authentication_ldap_simple_server_port``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--authentication-ldap-simple-server-port=value``
-   * - Scope
-     - Global
-   * - Dynamic
-     - No
-   * - Data type
-     - String
-   * - Default
-     - Null
-    
-The LDAP server TCP/IP port number used for LDAP authentication.
-
-.. _authentication_ldap_simple_ssl:
-
-.. rubric:: ``authentication_ldap_simple_ssl``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--authentication-ldap-simple-ssl=value``
-   * - Scope
-     - Global
-   * - Dynamic
-     - No
-   * - Data type
-     - String
-   * - Default
-     - Null
-    
-If this variable is enabled, the plugin connects to the server with SSL.
-
-.. _authentication_ldap_simple_tls:
-
-.. rubric:: ``authentication_ldap_simple_tls``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--authentication-ldap-simple-tls=value``
-   * - Scope
-     - Global
-   * - Dynamic
-     - No
-   * - Data type
-     - String
-   * - Default
-     - Null
-    
-If this variable is enabled, the plugin connects to the server with TLS.
-
-.. seealso::
-
-    `Simple LDAP Authentication <https://dev.mysql.com/doc/mysql-security-excerpt/8.0/en/ldap-pluggable-authentication.html#ldap-pluggable-authentication-usage-simple>`_
-    
diff --git a/doc/source/security/simple-ldap.rst b/doc/source/security/simple-ldap.rst
deleted file mode 100644
index acac3ee7bdf7..000000000000
--- a/doc/source/security/simple-ldap.rst
+++ /dev/null
@@ -1,208 +0,0 @@
-.. _simple-ldap:
-
-
-======================================================
-Using Simple LDAP Authentication
-======================================================
-
-This feature was implemented in :ref:`8.0.19-10`.
-
-LDAP (Lightweight Directory Access Protocol) provides an alternative method to
-access existing directory servers, which maintain information about
-individuals, groups, and organizations.
-
-The Percona Simple LDAP plugin is a free and Open Source implementation of the
-MySQL Enterprise Simple LDAP plugin.
-
-.. rubric:: Install the plugin
-
-Install the plugin with the following command::
-
-    mysql> INSTALL PLUGIN authentication_ldap_simple SONAME 'authentication_ldap_simple.so';
-
-The installation adds the following variables:
-
-.. list-table::
-    :widths: 20 15 15 6 6 10 5 8
-    :header-rows: 1
-
-    * - Variable Name
-      - Description
-      - Default
-      - Minimum
-      - Maximum
-      - Scope
-      - Dynamic
-      - Type
-    * - authentication_ldap_simple_bind_base_dn
-      - Base distinguished name (DN)
-      -
-      -
-      -
-      - global
-      - Yes
-      - string
-    * - authentication_ldap_simple_bind_root_dn
-      - Root distinguished name (DN)
-      -
-      -
-      -
-      - global
-      - yes
-      - string
-    * - authentication_ldap_simple_bind_root_pwd
-      - Password for the root distinguished name
-      - 
-      -
-      -
-      - global
-      - yes
-      - string
-    * - authentication_ldap_simple_ca_path
-      - Absolute path of the certificate authority file
-      -
-      -
-      -
-      - global
-      - yes
-      - string
-    * - authentication_ldap_simple_group_search_attr
-      - Name of the attribute that specifies the group names in LDAP directory
-        entries
-      - cn
-      -
-      -
-      - global
-      - yes
-      - string
-    * - authentication_ldap_simple_group_search_filter
-      - Custom group search filter
-      - (|(&(objectClass=posixGroup)(memberUid={UA}))(&(objectClass=group)(member={UD})))
-      -
-      -
-      - global
-      - yes
-      - string
-    * - authentication_ldap_simple_init_pool_size
-      - Initial size of the connection pool to the LDAP server
-      - 10
-      - 1
-      - 32767
-      - global
-      - yes
-      - uint
-    * - authentication_ldap_simple_log_status
-      - logging level
-      - 1
-      - 1
-      - 5
-      - global
-      - yes
-      - uint
-    * - authentication_ldap_simple_max_pool_size
-      - Maximum size of the pool of connections to the LDAP server
-      - 1000
-      - 1
-      - 32767
-      - global
-      - yes
-      - uint
-    * - authentication_ldap_simple_server_host
-      - LDAP server host
-      -
-      -
-      -
-      - global
-      - yes
-      - string
-    * - authentication_ldap_simple_server_port
-      - LDAP server TCP/IP port number
-      - 389
-      - 1
-      - 65535
-      - global
-      - yes
-      - uint
-    * - authentication_ldap_simple_ssl
-      - If plugin connections to the LDAP server use the SSL protocol (ldaps://)
-      - OFF
-      -
-      -
-      - global
-      - yes
-      - bool
-    * - authentication_ldap_simple_tls
-      - If plugin connections to the LDAP server are secured with STARTTLS (ldap://)
-      - OFF
-      -
-      -
-      - global
-      - yes
-      - bool
-    * - authentication_ldap_simple_user_search_attr
-      - Name of the attribute that specifies user names in LDAP directory
-        entries
-      - uid
-      -
-      -
-      - global
-      - yes
-      - string
-
-
-For simple LDAP authentication, you must specify the authentication_ldap_simple
-plugin in the ``CREATE USER`` statement or the ``ALTER USER`` statement.::
-
-    mysql> CREATE USER ... IDENTIFIED WITH authentication_ldap_simple;
-
-or ::
-
-    mysql> CREATE USER ... IDENTIFIED WITH authentication_ldap_simple BY 'cn=[user
-    name],ou=[organization unit],dc=[domain component],dc=com'
-
-.. note::
-
-    If the user is created with the "BY 'cn,ou,dc,dc'" the following variables
-    are not used:
-
-    * authentication_ldap_simple_bind_base_dn
-    * authentication_ldap_simple_bind_root_dn
-    * authentication_ldap_simple_bind_root_pwd
-    * authentication_ldap_simple_user_search_attr
-    * authentication_ldap_simple_group_search_attr
-
-    If the user is created with "IDENTIFIED BY authentication_ldap_simple" the
-    listed variables are used.
-
-If a MySQL user `rshimek` has the following entry in the LDAP directory:
-
-.. code-block:: text
-
-    uid=rshimek, ou=users, dc=hr, dc=com
-
-To create a MySQL account for `rshimek`, use the following statement:
-
-.. code-block:: MySQL
-
-    CREATE USER 'rshimek'@'localhost'
-    IDENTIFIED WITH authentication_ldap_simple
-    AS 'uid=rshimek,ou=users,dc=hr,dc=com';
-
-.. note::
-
-    **Security** The plugin requires sending the password in clear text.
-
-.. seealso::
-
-    `Client-Side Cleartext Pluggable Authentication <https://dev.mysql.com/doc/refman/8.0/en/cleartext-pluggable-authentication.html>`_
-
-.. rubric:: Uninstall the plugin
-
-To uninstall the plugin, run the following command::
-
-    mysql> UNINSTALL PLUGIN authentication_ldap_simple;
-
-.. seealso::
-
-    `LDAP Pluggable Authentication
-    <https://dev.mysql.com/doc/refman/8.0/en/ldap-pluggable-authentication.html>`_
diff --git a/doc/source/security/ssl-improvement.rst b/doc/source/security/ssl-improvement.rst
deleted file mode 100644
index dabb13d61566..000000000000
--- a/doc/source/security/ssl-improvement.rst
+++ /dev/null
@@ -1,19 +0,0 @@
-.. _ssl:
-
-================================================================================
-SSL Improvements
-================================================================================
-
-By default, *Percona Server for MySQL* passes elliptic-curve crypto-based
-ciphers to OpenSSL, such as ECDHE-RSA-AES128-GCM-SHA256.
-
-.. note::
-
-   Although documented as supported, elliptic-curve crypto-based ciphers do not work with *MySQL*.
-
-   .. seealso::
-
-      MySQL Bug System (solved for *Percona Server for MySQL*):
-         `#82935 Cipher ECDHE-RSA-AES128-GCM-SHA256 listed in man/Ssl_cipher_list, not supported <https://bugs.mysql.com/bug.php?id=82935>`_
-
-.. |openssl| replace:: OpenSSL
diff --git a/doc/source/security/system-variables.rst b/doc/source/security/system-variables.rst
deleted file mode 100644
index 0bd33bb7ff8e..000000000000
--- a/doc/source/security/system-variables.rst
+++ /dev/null
@@ -1,36 +0,0 @@
-.. _secure-variables:
-
-================================================================================
-Server variables
-================================================================================
-
-Use system variables to configure the server operation. 
-    
-.. _secure_log_path:
-
-.. rubric:: `secure_log_path`
-
-
-Implemented in :ref:`8.0.28-19`.
-
-.. list-table::
-   :header-rows: 1
-   
-   * - Variable Name
-     - Description
-   * - Command-line
-     - ``--secure-log-path``
-   * - Dynamic
-     - No
-   * - Scope
-     - Global
-   * - Data type
-     - String
-   * - Default
-     - empty string
-     
-This variable restricts the dynamic log file locations. The variable is read-only and must be set up in a configuration file or the command line. 
-
-The accepted value is the directory name as a string. The default value is an empty string. When the value is an empty string, the variable only adds a warning to the error log and does nothing. If the value contains a directory name, then the slow query log and the general log must be located in that directory. An attempt to move either of these files outside of the specified directory results in an error.
-
-
diff --git a/doc/source/security/using-amz-kms.rst b/doc/source/security/using-amz-kms.rst
deleted file mode 100644
index 56d9c5ef0835..000000000000
--- a/doc/source/security/using-amz-kms.rst
+++ /dev/null
@@ -1,130 +0,0 @@
-.. _using-amz-kms:
-
-================================================================================
-Using the Amazon Key Management Service (AWS KMS)
-================================================================================
-
-This feature is **technical preview** quality.
-
-**Percona Server for MySQL** 8.0.28-20 adds support for the `Amazon Key
-Management Server (AWS KMS) <https://aws.amazon.com/kms/>`__. Percona Server
-generates the keyring keys. Amazon Web Services (AWS) encrypts the keyring data.
-
-The AWS KMS lets you create and manage cryptographic keys across AWS services. For more information, see the
-`AWS Key Management Service Documentation <https://docs.aws.amazon.com/kms/>`__.
-
-To use the AWS KMS component, do the following:
-
-* Have an AWS user account. This account has an access key and a secret key.
-* Create a KMS key ID. The KMS key can then be referenced in the configuration
-  either by its ID, alias (the key can have any number of aliases), or ARN.
-
-
-Component installation
---------------------------------------
-
-You should only load the AWS KMS component with a manifest file. The server uses
-this manifest file and the
-component consults its configuration file during initialization.
-
-For more information, see `Installing and Uninstalling Components
-<https://dev.mysql.com/doc/refman/8.0/en/component-loading.html>`__
-
-You should create a global manifest file named ``mysqld.my`` in the installation directory and, optionally, create a local manifest file, also named ``mysqld.my`` in a data directory.
-
-To install a KMS component, do the following:
-
-1. Write a manifest in a valid JSON format
-2. Write a configuration file
-
-A manifest file indicates which component to load. The server does not load the
-component if the manifest file associated with the component does not exist.
-During startup, the server reads the global manifest file from the installation
-directory. The global manifest file can contain the required information or
-point to a local manifest file located in the data directory. If you have
-multiple server instances that use different keyring components, use a local
-manifest file in each data directory to load the correct keyring component for that instance.
-
-.. note:: 
-
-    Enable only one keyring plugin or one keyring component at a time for each server instance. Enabling multiple keyring plugins or keyring components or mixing keyring plugins or keyring components is not supported and may result in data loss.
-
-The following example is a global manifest file that does not use local
-manifests:
-
-.. code-block:: json
-
-    {
-     "read_local_manifest": false,
-     "components": "file:///component_keyring_kmip"
-    }
-
-The following is an example of a global manifest file that points to a local manifest file:
-
-.. code-block:: json
-
-    {
-     "read_local_manifest": true
-    }
-
-The following is an example of a local manifest file:
-
-.. code-block:: json
-
-    {
-     "components": "file:///component_keyring_kmip"
-    }
-
-The configuration settings are either in a global configuration file or a local
-configuration file. The settings are the same.
-
-The KMS configuration file has the following options:
-
-* read_local_config
-
-* path - the location of the JSON keyring database file.
-
-* read_only - if true, the keyring cannot be modified.
-
-* kms_key - the identifier of an AWS KMS master key. This key must be created by
-  the user before creating the manifest file. The identifier can be one of the
-  following:
-
-  * UUID
-  * Alias
-  * ARN
-
-  For more information, see `Finding the key ID and key ARN
-  <https://docs.aws.amazon.com/kms/latest/developerguide/find-cmk-id-arn.html>`__.
-
-* region - the AWS where the KMS is stored. Any HTTP request connect to this
-  region.
-
-* auth_key - an AWS user authentication key. The user must have access to the
-  KMS key.
-
-* secret_access_key - the secret key (API "password") for the AWS user.
-
-
-.. note::
-
-    The configuration file contains authentication information. Only the
-    MySQL process should be able to read this file.
-
-The following **JSON** is an example of a configuration file:
-
-
-.. code-block:: json
-
-    {
-     "read_local_config": "true/false",
-     "path": "/usr/local/mysql/keyring-mysql/aws-keyring-data",
-     "region": "eu-central-1",
-     "kms_key": "UUID, alias or ARN as displayed by the KMS console",
-     "auth_key": "AWS user key",
-     "secret_access_key": "AWS user secret key"
-    }
-
-
-For more information, see `Keyring Component installation <https://dev.mysql.com/doc/refman/8.0/en/keyring-component-installation.html>`__ 
-
diff --git a/doc/source/security/using-keyring-plugin.rst b/doc/source/security/using-keyring-plugin.rst
deleted file mode 100644
index c20e280f4f5f..000000000000
--- a/doc/source/security/using-keyring-plugin.rst
+++ /dev/null
@@ -1,282 +0,0 @@
-.. _using-keyring-plugin:
-
-=======================================================
-Using the Keyring Plugin
-=======================================================
-
-*Percona Server for MySQL* may use either of the following plugins:
-
-*  `keyring_file` stores the keyring data locally
-
-* `keyring_vault` provides an interface for the database with a HashiCorp Vault
-  server to store key and secure encryption keys.
-
-.. note::
-
-    The ``keyring_file`` plugin should not be used for regulatory compliance.
-
-To install the plugin, follow the `installing and uninstalling plugins
-<https://dev.mysql.com/doc/refman/8.0/en/plugin-loading.html>`__ instructions.
-
-Loading the Keyring Plugin
---------------------------------------------------------------------------------
-
-You should load the plugin at server startup with the ``-early-plugin-load``
-option to enable keyrings.
-
-.. warning::
-
-    Only one keyring plugin should be enabled at a time. Enabling multiple
-    keyring plugins is not supported and may result in data loss.
-
-We recommend the plugin should be loaded in the configuration file to facilitate
-recovery for encrypted tables. Also, the redo log and the undo log encryption cannot
-be used without ``--early-plugin-load``. The normal plugin load happens too late
-in startup.
-
-.. note::
-
-    The keyring_vault extension, ".so" and the file location for the vault
-    configuration should be changed to match your operating system's extension
-    and the file location in your operating system.
-
-To use the keyring_vault, you can add this option to your configuration file:
-
-.. code-block:: text
-
-    [mysqld]
-    early-plugin-load="keyring_vault=keyring_vault.so"
-    loose-keyring_vault_config="/home/mysql/keyring_vault.conf"
-
-    The keyring_vault extension, ".so" and the file location for the vault
-    configuration should be changed to match your operating system's extension
-    and operating system location.
-
-
-You could also run the following command which loads the keyring_file plugin:
-
-.. code-block:: bash
-
-   $ mysqld --early-plugin-load="keyring_file=keyring_file.so"
-
-
-
-.. note::
-
-     If a server starts with different plugins loaded early, the
-     ``--early-plugin-load`` option should contain the plugin names in a
-     double-quoted list with each plugin name separated by a semicolon. The
-     use of double quotes ensures the semicolons do not create issues when the
-     list is executed in a script.
-
-.. seealso::
-
-   *MySQL* Documentation:
-      - `Installing a Keyring Plugin
-        <https://dev.mysql.com/doc/refman/8.0/en/keyring-installation.html>`__
-      - `The ` --early-plugin-load Option
-        <https://dev.mysql.com/doc/refman/8.0/en/server-options.html#option_mysqld_early-plugin-load>`__
-
-Apart from installing the plugin you also must set the
-:ref:`keyring_vault_config` variable to point to the keyring_vault
-configuration file.
-
-The `keyring_vault_config` file has the following information:
-
-* ``vault_url`` - the Vault server address
-
-* ``secret_mount_point`` - the mount point name where the `keyring_vault` stores the keys.
-
-* ``secret_mount_point_version`` - the ``KV Secrets Engine version (kv or kv-v2)`` used. Implemented in *Percona Server for MySQL* 8.0.23-14.
-
-* ``token`` - a token generated by the Vault server
-
-* ``vault_ca [optional]`` - if the machine does not trust the Vault's CA certificate, this variable points to the CA certificate used to sign the Vault's certificates
-
-This is an example of a configuration file: ::
-
-  vault_url = https://vault.public.com:8202
-  secret_mount_point = secret
-  secret_mount_point_version = AUTO
-  token = 58a20c08-8001-fd5f-5192-7498a48eaf20
-  vault_ca = /data/keyring_vault_confs/vault_ca.crt
-
-.. warning::
-
-    Each ``secret_mount_point`` must be used by only one server. If multiple
-    servers use the same secret_mount_point, the behavior is unpredictable.
-
-The first time a key is fetched from a `keyring`, the `keyring_vault`
-communicates with the Vault server to retrieve the key type and data.
-
-secret_mount_point_version information
----------------------------------------
-
-Implemented in *Percona Server for MySQL* 8.0.23-14, the ``secret_mount_point_version``
-can be either a ``1``, ``2``, ``AUTO``, or the ``secret_mount_point_version``
-parameter is not listed in the configuration file.
-
-.. list-table::
-  :widths: 10 40
-  :header-rows: 1
-
-  * - Value
-    - Description
-  * - 1
-    - Works with ``KV Secrets Engine - Version 1 (kv)``. When forming key
-      operation URLs, the ``secret_mount_point`` is always used without any
-      transformations.
-
-      For example, to return a key named ``skey``, the URL is
-      ::
-      
-      <vault_url>/v1/<secret_mount_point>/skey
-  * - 2
-    - Works with ``KV Secrets Engine - Version 2 (kv)`` The initialization
-      logic splits the ``secret_mount_point`` parameter into two parts:
-      
-      * The ``mount_point_path`` - the mount path under which the Vault Server secret was created
-      
-      * The ``directory_path`` - a virtual directory suffix that can be used to create virtual namespaces with the same real mount point
-
-      For example, both the ``mount_point_path`` and the ``directory_path`` are needed to
-      form key access URLs: ::
-
-      <vault_url>/v1/<mount_point_path/data/<directory_path>/skey
-
-  * - AUTO
-    - An autodetection mechanism probes and determines if the secrets engine
-      version is ``kv`` or ``kv-v2`` and based on the outcome will either use
-      the ``secret_mount_point`` as is, or split the ``secret_mount_point`` into
-      two parts.
-  * - Not listed
-    - If the ``secret_mount_point_version`` is not listed in the configuration file, the behavior is the
-      same as ``AUTO``.
-
-If you set the ``secret_mount_point_version`` to ``2`` but the path pointed
-by ``secret_mount_point`` is based on ``KV Secrets Engine - Version 1 (kv)``,
-an error is reported and the plugin fails to initialize.
-
-If you set the ``secret_mount_point_version`` to ``1`` but the path pointed
-by ``secret_mount_point`` is based on ``KV Secrets Engine -
-Version 2 (kv-v2)``, the plugin initialization succeeds but any MySQL
-keyring-related operations fail.
-
-
-Upgrading from 8.0.22-13 or earlier to 8.0.23-14 or later
-----------------------------------------------------------
-
-The ``keyring_vault`` plugin configuration files created before
-*Percona Server for MySQL* 8.0.23-14 work only with ``KV Secrets Engine -
-Version 1 (kv)`` and do not have the ``secret_mount_point_version``
-parameter. After the upgrade to 8.0.23-14 or later, the
-``secret_mount_point_version`` is implicitly considered ``AUTO`` and the
-information is probed and the secrets engine version is determined to ``1``.
-
-Upgrading from Vault Secrets Engine Version 1 to Version 2
------------------------------------------------------------
-
-You can upgrade from the Vault Secrets Engine Version 1 to Version 2.
-Use either of the following methods:
-
-- Set the ``secret_mount_point_version`` to ``AUTO`` or the variable is not set in the ``keyring_vault`` plugin configuration files in all Percona Servers. The ``AUTO`` value ensures the autodetection mechanism is invoked during the plugin initialization.
-
-- Set the ``secret_mount_point_version`` to ``2`` to ensure that plugins do not initialize unless the ``kv`` to ``kv-v2`` upgrade completes.
-
-.. note:: The ``keyring_vault`` plugin that works with ``kv-v2`` secret engines does not use the built-in key versioning capabilities. The keyring key versions are encoded into key names.
-
-KV Secret Engine considerations for upgrading from 5.7 to 8.0
----------------------------------------------------------------
-
-When you upgrade from *Percona Server for MySQL* 5.7.32 or older, you can only use
-``KV Secrets Engine 1 (kv)``. You can upgrade to any version of
-*Percona Server for MySQL* 8.0. Both the old ``keyring_vault`` plugin and new
-``keyring_vault`` plugin work correctly with the existing Vault Server
-data under the existing ``keyring_vault`` plugin configuration file.
-
-If you upgrade from *Percona Server for MySQL* 5.7.33 or newer, you have the following options:
-
-  - If you are using ``KV Secrets Engine 1 (kv)`` you can upgrade with any version of *Percona Server for MySQL* 8.0.
-
-  - If you are using ``KV Secrets Engine 2 (kv-v2)`` you can upgrade with *Percona Server for MySQL* 8.0.23 or newer. *Percona Server for MySQL* 8.0.23.14 is the first version of the 8.0 series which has the ``keyring_vault`` plugin that supports ``kv-v2``.
-
-A user-created key deletion is only possible with the use of the keyring_udf
-plugin and deletes the key from the in-memory hash map and the Vault server.
-You cannot delete system keys, such as the master key.
-
-This plugin supports the SQL interface for keyring key management described in
-`General-Purpose Keyring Key-Management Functions
-<https://dev.mysql.com/doc/refman/8.0/en/keyring-udfs-general-purpose.html>`_
-manual.
-
-The plugin library contains keyring user-defined functions which allow
-access to the internal keyring service functions. To enable the functions, you
-must enable the ``keyring_udf`` plugin:
-
-.. code-block:: MySQL
-
-    mysql> INSTALL PLUGIN keyring_udf SONAME 'keyring_udf.so';
-
-.. note::
-
-    The ``keyring_udf`` plugin must be installed. Using the user-defined functions
-    without the ``keyring_udf`` plugin generates an error.
-
-You must also create keyring encryption user-defined functions.
-
-System Variables
---------------------
-
-.. _keyring_vault_config:
-
-.. rubric:: ``keyring_vault_config``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--keyring-vault-config``
-   * - Scope
-     - Global
-   * - Dynamic
-     - Yes
-   * - Data type
-     - Text
-   * - Default
-     - 
-
-This variable is used to define the location of the `keyring_vault_plugin`
-configuration file.
-
-.. _keyring_vault_timeout:
-
-.. rubric:: ``keyring_vault_timeout``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - ``--keyring-vault-timeout``
-   * - Scope
-     - Global
-   * - Dynamic
-     - Yes
-   * - Data type
-     - Numeric
-   * - Default
-     - ``15``
-
-Set the duration in seconds for the Vault server connection timeout. The
-default value is ``15``. The allowed range is from ``0`` to ``86400``. The
-timeout can be also disabled to wait an infinite amount of time by setting
-this variable to ``0``.
-
-.. seealso::
-
-    :ref:`vault`
-
-    :ref:`rotating-master-key`
diff --git a/doc/source/security/using-kmip.rst b/doc/source/security/using-kmip.rst
deleted file mode 100644
index a2a70a2ad39c..000000000000
--- a/doc/source/security/using-kmip.rst
+++ /dev/null
@@ -1,74 +0,0 @@
-.. _using-kmip:
-
-==========================================================
-Using the Key Management Interoperability Protocol (KMIP)
-==========================================================
-
-This feature is **technical preview** quality.
-
-**Percona Server for MySQL** 8.0.27-18 adds support for the `OASIS Key Management Interoperability Protocol (KMIP) <https://docs.oasis-open.org/kmip/kmip-spec/v2.0/os/kmip-spec-v2.0-os.html>`__. This implementation was tested with the `PyKMIP server <https://pykmip.readthedocs.io/en/latest/server.html>`__ and the `HashiCorp Vault Enterprise KMIP Secrets Engine <https://www.vaultproject.io/docs/secrets/kmip>`__.
-
-KMIP enables communication between key management systems and the database server. The protocol can do the following:
-
-* Streamline encryption key management
-
-* Eliminate redundant key management processes
-
-Component installation
---------------------------------------
-
-The KMIP component must be installed with a manifest. A keyring component is not loaded with the ``--early-plugin-load`` option on the server. The server uses a manifest and the component consults its configuration file during initialization. You should only load a keyring component with a manifest file. Do not use the ``INSTALL_COMPONENT`` statement, which loads the keyring components too late in the startup sequence of the server. For example, ``InnoDB`` requires the component, but because the components are registered in the ``mysql.component`` table, this table is loaded after ``InnoDB`` initialization. 
-
-You should create a global manifest file named ``mysqld.my`` in the installation directory and, optionally, create a local manifest file, also named ``mysqld.my`` in a data directory.
-
-To install a keyring component, you must do the following:
-
-1. Write a manifest in a valid JSON format
-2. Write a configuration file
-
-A manifest file indicates which component to load. If the manifest file does not exist, the server does not load the component associated with that file. During startup, the server reads the global manifest file from the installation directory. The global manifest file can contain the required information or point to a local manifest file located in the data directory. If you have multiple server instances that use different keyring components use a local manifest file in each data directory to load the correct keyring component for that instance.
-
-.. note:: 
-
-    Enable only one keyring plugin or one keyring component at a time for each server instance. Enabling multiple keyring plugins or keyring components or mixing keyring plugins or keyring components is not supported and may result in data loss.
-
-The following is an example of a global manifest file that does not use local manifests:
-
-.. code-block:: json
-
-    {
-     "read_local_manifest": false,
-     "components": "file:///component_keyring_kmip"
-    }
-
-The following is an example of a global manifest file that points to a local manifest file:
-
-.. code-block:: json
-
-    {
-     "read_local_manifest": true
-    }
-
-The following is an example of a local manifest file:
-
-.. code-block:: json
-
-    {
-     "components": "file:///component_keyring_kmip"
-    }
-
-The configuration settings are either in a global configuration file or a local configuration file. The settings are the same. The following **JSON** example of a configuration file.
-
-.. code-block:: json
-
-   {
-    "server_addr": "127.0.0.1",
-    "server_port": "5696",
-    "client_ca": "client_certificate.pem",
-    "client_key": "client_key.pem",
-    "server_ca": "root_certificate.pem"
-   }
-
-
-For more information, see `Keyring Component installation <https://dev.mysql.com/doc/refman/8.0/en/keyring-component-installation.html>`__ 
-
diff --git a/doc/source/security/vault.rst b/doc/source/security/vault.rst
deleted file mode 100644
index ce2529e64231..000000000000
--- a/doc/source/security/vault.rst
+++ /dev/null
@@ -1,32 +0,0 @@
-.. _vault:
-
-================================================================================
-Information about HashiCorp Vault
-================================================================================
-
-The ``keyring_vault`` plugin can store the encryption keys inside the `HashiCorp
-Vault <https://www.hashicorp.com/products/vault/data-protection>`__.
-
-.. important::
-
-  The ``keyring_vault`` plugin works with `KV Secrets Engine - Version 1 <https://www.vaultproject.io/docs/secrets/kv/kv-v1.html>`__ and
-  `KV Secrets Engine - Version 2 <https://www.vaultproject.io/docs/secrets/kv/kv-v2>`__
-
-
-.. seealso::
-
-  HashiCorp Documentation:
-
-  Installing Vault
-  https://www.vaultproject.io/docs/install/index.html
-
-  Production Hardening
-  https://learn.hashicorp.com/vault/operations/production-hardening
-
-.. seealso::
-
-    :ref:`using-keyring-plugin`
-
-    :ref:`rotating-master-key`
-
-
diff --git a/doc/source/security/verifying-encryption.rst b/doc/source/security/verifying-encryption.rst
deleted file mode 100644
index 00d2138d4ea2..000000000000
--- a/doc/source/security/verifying-encryption.rst
+++ /dev/null
@@ -1,99 +0,0 @@
-.. _verifying-encryption:
-
-===================================================================
-Verifying the Encryption for Tables, Tablespaces, and Schemas
-===================================================================
-
-If a general tablespace contains tables, check the table information to see if
-the table is encrypted. When the general tablespace contains no tables, you
-may verify if the tablespace is encrypted or not.
-
-For single tablespaces, verify the ENCRYPTION option using
-`INFORMATION_SCHEMA.TABLES` and the `CREATE OPTIONS` settings.
-
-.. code-block:: MySQL
-
-    mysql> SELECT TABLE_SCHEMA, TABLE_NAME, CREATE_OPTIONS FROM
-           INFORMATION_SCHEMA.TABLES WHERE CREATE_OPTIONS LIKE '%ENCRYPTION%';
-
-    +----------------------+-------------------+------------------------------+
-    | TABLE_SCHEMA         | TABLE_NAME        | CREATE_OPTIONS               |
-    +----------------------+-------------------+------------------------------+
-    |sample                | t1                | ENCRYPTION="Y"               |
-    +----------------------+-------------------+------------------------------+
-
-
-A ``flag`` field in the ``INFORMATION_SCHEMA.INNODB_TABLESPACES`` has bit number
-13 set if the tablespace is encrypted. This bit can be checked with the ``flag &
-8192`` expression in the following way:
-
-.. code-block:: mysql
-
-    SELECT space, name, flag, (flag & 8192) != 0 AS encrypted FROM
-    INFORMATION_SCHEMA.INNODB_TABLESPACES WHERE name in ('foo', 'test/t2', 'bar',
-    'noencrypt');
-
-.. admonition:: Output
-
-   .. code-block:: mysql
-
-      +-------+-----------+-------+-----------+
-      | space | name      | flag  | encrypted |
-      +-------+-----------+-------+-----------+
-      |    29 | foo       | 10240 |      8192 |
-      |    30 | test/t2   |  8225 |      8192 |
-      |    31 | bar       | 10240 |      8192 |
-      |    32 | noencrypt |  2048 |         0 |
-      +-------+-----------+-------+-----------+
-      4 rows in set (0.01 sec)
-
-The encrypted table metadata is contained in the
-INFORMATION_SCHEMA.INNODB_TABLESPACES_ENCRYPTION table. You must have the
-``Process`` privilege to view the table information.
-
-.. note::
-
-    This table is in tech preview and may change in future releases.
-
-.. code-block:: MySQL
-
-  >desc INNODB_TABLESPACES_ENCRYPTION:
-
-  +-----------------------------+--------------------+-----+----+--------+------+
-  | Field                       | Type               | Null| Key| Default| Extra|
-  +-----------------------------+--------------------+-----+----+--------+------+
-  | SPACE                       | int(11) unsigned   | NO  |    |        |      |
-  | NAME                        | varchar(655)       | YES |    |        |      |
-  | ENCRYPTION_SCHEME           | int(11) unsigned   | NO  |    |        |      |
-  | KEYSERVER_REQUESTS          | int(11) unsigned   | NO  |    |        |      |
-  | MIN_KEY_VERSION             | int(11) unsigned   | NO  |    |        |      |
-  | CURRENT_KEY_VERSION         | int(11) unsigned   | NO  |    |        |      |
-  | KEY_ROTATION_PAGE_NUMBER    | bigint(21) unsigned| YES |    |        |      |
-  | KEY_ROTATION_MAX_PAGE_NUMBER| bigint(21) unsigned| YES |    |        |      |
-  | CURRENT_KEY_ID              | int(11) unsigned   | NO  |    |        |      |
-  | ROTATING_OR_FLUSHING        | int(1) unsigned    | NO  |    |        |      |
-  +-----------------------------+--------------------+-----+----+--------+------+
-
-To identify encryption-enabled schemas, query the
-INFORMATION_SCHEMA.SCHEMATA table:
-
-..  code-block:: MySQL
-
-    mysql> SELECT SCHEMA_NAME, DEFAULT_ENCRYPTION FROM
-    INFORMATION_SCHEMA.SCHEMATA WHERE DEFAULT_ENCRYPTION='YES';
-
-    +------------------------------+---------------------------------+
-    | SCHEMA_NAME                  | DEFAULT_ENCRYPTION              |
-    +------------------------------+---------------------------------+
-    | samples                      | YES                             |
-    +------------------------------+---------------------------------+
-
-.. note::
-
-    The ``SHOW CREATE SCHEMA`` statement returns the ``DEFAULT ENCRYPTION``
-    clause.
-
-.. seealso::
-
-   *MariaDB* Documentation
-    https://mariadb.com/kb/en/library/information-schema-innodb_tablespaces_encryption-table/
diff --git a/doc/source/tokudb/fast_updates.rst b/doc/source/tokudb/fast_updates.rst
deleted file mode 100644
index 4cd1ef59dd43..000000000000
--- a/doc/source/tokudb/fast_updates.rst
+++ /dev/null
@@ -1,139 +0,0 @@
-.. _fast_updates:
-
-==========================
- Fast Updates with TokuDB
-==========================
-
-.. Important:: 
-
-   Starting with :ref:`8.0.28-19`, the TokuDB storage engine is no longer supported. We have removed the storage engine from the installation packages and disabled the storage engine in our binary builds.
-
-   Starting with :ref:`8.0.26-16`, the binary builds and packages include but disable the TokuDB storage engine plugins. The ``tokudb_enabled`` option and the ``tokudb_backup_enabled`` option control the state of the plugins and have a default setting of ``FALSE``. The result of attempting to load the plugins are the plugins fail to initialize and print a deprecation message.
-
-   We recommend :ref:`migrate-myrocks`. To enable the plugins to migrate to another storage engine, set the ``tokudb_enabled`` and ``tokudb_backup_enabled`` options to ``TRUE`` in your ``my.cnf`` file and restart your server instance. Then, you can load the plugins.
-
-   The TokuDB Storage Engine was `declared as deprecated <https://www.percona.com/doc/percona-server/8.0/release-notes/Percona-Server-8.0.13-3.html>`__ in Percona Server for MySQL 8.0. For more information, see the Percona blog post: `Heads-Up: TokuDB Support Changes and Future Removal from Percona Server for MySQL 8.0 <https://www.percona.com/blog/2021/05/21/tokudb-support-changes-and-future-removal-from-percona-server-for-mysql-8-0/>`__.
-
-Introduction
-============
-
-Update intensive applications can have their throughput limited by the random
-read capacity of the storage system. The cause of the throughput limit is the
-read-modify-write algorithm that *MySQL* uses to process update statements
-(read a row from the storage engine, apply the updates to it, write the new row
-back to the storage engine).
-
-To address this throughput limit, *TokuDB* provides an experimental fast update
-feature, which uses a different update algorithm. Update expressions of the SQL
-statement are encoded into tiny programs that are stored in an update Fractal
-Tree message. This update message is injected into the root of the Fractal Tree
-index. Eventually, these update  messages reach a leaf node, where the update
-programs are applied to the row. Since messages are moved between Fractal Tree
-levels in batches, the cost of reading in the leaf node is amortized over many
-update messages.
-
-This feature is available for ``UPDATE`` and ``INSERT`` statements, and can be
-turned ON/OFF separately for them with use of two variables. Variable
-:ref:`tokudb_enable_fast_update` variable toggles fast updates for the
-``UPDATE``, and  :ref:`tokudb_enable_fast_upsert` does the same  for
-``INSERT``.
-
-Limitations
-===========
-
-Fast updates are activated instead of normal MySQL read-modify-write updates
-if the executed expression meets the number of conditions.
-
-* fast updates can be activated for a statement or a mixed replication,
-
-* a primary key must be defined for the involved table,
-
-* both simple and compound primary keys are supported, and ``int``, ``char`` or
-  ``varchar`` are the allowed data types for them,
-
-* updated fields should have ``Integer`` or ``char`` data type,
-
-* fields that are part of any key should be not updated,
-
-* clustering keys are not allowed,
-
-* triggers should be not involved,
-
-* supported update expressions should belong to one of the following types:
-
-  * ``x = constant``
-
-  * ``x = x + constant``
-
-  * ``x = x - constant``
-
-  * ``x = if (x=0,0,x-1)``
-
-  * ``x = x + values``
-
-Usage Specifics and Examples
-============================
-
-Following example creates a table that associates event identifiers with their
-count:
-
-.. code-block:: sql
-
-   CREATE TABLE t (
-       event_id bigint unsigned NOT NULL PRIMARY KEY,
-       event_count bigint unsigned NOT NULL
-   );
-
-Many graph applications that map onto relational tables can use duplicate key
-inserts and updates to maintain the graph. For example, one can update the
-meta-data associated with a link in the graph using duplicate key insertions.
-If the affected rows is not used by the application, then the insertion or
-update can be marked and executed as a fast insertion or a fast update.
-
-Insertion example
------------------
-
-If it is not known if the event identifier (represented by `event_id`) already
-exists in the table, then ``INSERT ... ON DUPLICATE KEY UPDATE ...`` statement
-can insert it if not existing, or increment its `event_count` otherwise. Here
-is an example with duplicate key insertion statement, where ``%id`` is some
-specific `event_id` value:
-
-.. code-block:: sql
-
-   INSERT INTO t VALUES (%id, 1)
-     ON DUPLICATE KEY UPDATE event_count=event_count+1;
-
-Explanation
-***********
-If the event id’s are random, then the throughput of this application would be
-limited by the random read capacity of the storage system since each ``INSERT``
-statement has to determine if this `event_id` exists in the table.
-
-*TokuDB* replaces the primary key existence check with an insertion of an
-“upsert” message into the Fractal Tree index. This “upsert” message contains a
-copy of the row and a program that increments event_count. As the Fractal Tree
-buffer’s get filled, this “upsert” message is flushed down the tree.
-Eventually, the message reaches a leaf node and gets executed there.
-If the key exists in the leaf node, then the event_count is incremented.
-Otherwise, the new row is inserted into the leaf node.
-
-Update example
---------------
-
-If `event_id` is known to exist in the table, then ``UPDATE`` statement can be
-used to increment its `event_count` (once again, specific `event_id` value is
-written here as ``%id``):
-
-.. code-block:: sql
-
-   UPDATE t SET event_count=event_count+1 
-   WHERE event_id=%id;
-
-Explanation
-***********
-
-TokuDB generates an “update” message from the ``UPDATE`` statement and its
-update expression trees, and inserts this message into the Fractal Tree index.
-When the message eventually reaches the leaf node, the increment program is
-extracted from the message and executed.
diff --git a/doc/source/tokudb/removing_tokudb.rst b/doc/source/tokudb/removing_tokudb.rst
deleted file mode 100644
index b0a0e71c38ea..000000000000
--- a/doc/source/tokudb/removing_tokudb.rst
+++ /dev/null
@@ -1,118 +0,0 @@
-.. _removing_tokudb:
-
-==================================================
-Migrating and Removing the TokuDB storage engine
-==================================================
-
-.. Important:: 
-
-   Starting with :ref:`8.0.28-19`, the TokuDB storage engine is no longer supported. We have removed the storage engine from the installation packages and disabled the storage engine in our binary builds.
-
-   Starting with :ref:`8.0.26-16`, the binary builds and packages include but disable the TokuDB storage engine plugins. The ``tokudb_enabled`` option and the ``tokudb_backup_enabled`` option control the state of the plugins and have a default setting of ``FALSE``. The result of attempting to load the plugins are the plugins fail to initialize and print a deprecation message.
-
-   We recommend :ref:`migrate-myrocks`. To enable the plugins to migrate to another storage engine, set the ``tokudb_enabled`` and ``tokudb_backup_enabled`` options to ``TRUE`` in your ``my.cnf`` file and restart your server instance. Then, you can load the plugins.
-
-   The TokuDB Storage Engine was `declared as deprecated <https://www.percona.com/doc/percona-server/8.0/release-notes/Percona-Server-8.0.13-3.html>`__ in Percona Server for MySQL 8.0. For more information, see the Percona blog post: `Heads-Up: TokuDB Support Changes and Future Removal from Percona Server for MySQL 8.0 <https://www.percona.com/blog/2021/05/21/tokudb-support-changes-and-future-removal-from-percona-server-for-mysql-8-0/>`__.
-
-.. _migrate-myrocks:
-
-Migrating the data to MyRocks Storage Engine
----------------------------------------------------------
-
-To migrate data use the `mysqldump <https://dev.mysql.com/doc/refman/8.0/en/mysqldump.html>`__ client utility or the tools in the `MySQL Workbench <https://dev.mysql.com/downloads/workbench/>`__ to dump and restore the database.
-
-We recommended migrating to the `MyRocks` storage engine. Follow these steps to migrate the data:
-
-1. Use mysqldump to backup the TokuDB database into a single file.
-
-2. Create a MyRocks instance with MyRocks tables with no data.
-
-3. Replace the references to `TokuDB` with `MyRocks`.
-
-4. Enable the following variable: `rocksdb_bulk_load`. This variable also enables `rocksdb_commit_in_the_middle`.
-
-5. Import the data into the MyRocks database.
-
-Follow the :ref:`remove-plugins` steps.
-
-Migrating from TokuDB to InnoDB
----------------------------------
-
-In case you want remove the TokuDB storage engine from *Percona Server for MySQL* without
-causing any errors following is the recommended procedure:
-
-Change the tables from TokuDB to InnoDB
----------------------------------------
-
-If you still need the data in the TokuDB tables you must alter the tables
-to other supported storage engine i.e., *InnoDB*: :mysql:`ALTER TABLE City
-ENGINE=InnoDB;`
-
-.. note::
-
-   Do not remove the TokuDB storage engine before you've changed your
-   tables to the other supported storage engine. Otherwise, you will not be able to access that
-   data without reinstalling the TokuDB storage engine.
-
-.. _remove-plugins:
-
-Removing the plugins
---------------------
-
-To remove the *TokuDB* storage engine with all installed plugins you can use the
-**ps-admin** script:
-
-.. code-block:: bash
-
-   $ ps-admin --disable-tokudb -uroot -pPassw0rd
-
-Script output should look like this:
-
-.. admonition:: Output
-
-   .. code-block:: bash
-
-      Checking if Percona server is running with jemalloc enabled...
-      >> Percona server is running with jemalloc enabled.
-
-      Checking transparent huge pages status on the system...
-      >> Transparent huge pages are currently disabled on the system.
-
-      Checking if thp-setting=never option is already set in config file...
-      >> Option thp-setting=never is set in the config file.
-
-      Checking TokuDB plugin status...
-      >> TokuDB plugin is installed.
-
-      Removing thp-setting=never option from /etc/mysql/my.cnf
-      >> Successfuly removed thp-setting=never option from /etc/mysql/my.cnf
-
-      Uninstalling TokuDB plugin...
-      >> Successfuly uninstalled TokuDB plugin.
-
-Another option is to manually remove the *TokuDB* storage engine with all installed plugins:
-
-.. code-block:: mysql
-
-   UNINSTALL PLUGIN tokudb;
-   UNINSTALL PLUGIN tokudb_file_map;
-   UNINSTALL PLUGIN tokudb_fractal_tree_info;
-   UNINSTALL PLUGIN tokudb_fractal_tree_block_map;
-   UNINSTALL PLUGIN tokudb_trx;
-   UNINSTALL PLUGIN tokudb_locks;
-   UNINSTALL PLUGIN tokudb_lock_waits;
-   UNINSTALL PLUGIN tokudb_background_job_status;
-
-After the engine and the plugins have been uninstalled you can remove the TokuDB package by using the apt/yum commands:
-
-.. code-block:: bash
-
- [root@centos ~]# yum remove Percona-Server-tokudb-80.x86_64
-
-or :bash:`apt remove percona-server-tokudb-8.0`
-
-.. note::
-
-   Make sure you've removed all the TokuDB specific variables from your configuration file (:file:`my.cnf`) before you restart the server, otherwise server could show errors or warnings and won't be able to start.
-
-.. include:: ../.res/replace.program.txt
diff --git a/doc/source/tokudb/toku_backup.rst b/doc/source/tokudb/toku_backup.rst
deleted file mode 100644
index f892bb851dff..000000000000
--- a/doc/source/tokudb/toku_backup.rst
+++ /dev/null
@@ -1,321 +0,0 @@
-.. _toku_backup:
-
-==================
-Percona TokuBackup
-==================
-
-.. Important:: 
-
-   Starting with :ref:`8.0.28-19`, the TokuDB storage engine is no longer supported. We have removed the storage engine from the installation packages and disabled the storage engine in our binary builds.
-
-   Starting with :ref:`8.0.26-16`, the binary builds and packages include but disable the TokuDB storage engine plugins. The ``tokudb_enabled`` option and the ``tokudb_backup_enabled`` option control the state of the plugins and have a default setting of ``FALSE``. The result of attempting to load the plugins are the plugins fail to initialize and print a deprecation message.
-
-   We recommend :ref:`migrate-myrocks`. To enable the plugins to migrate to another storage engine, set the ``tokudb_enabled`` and ``tokudb_backup_enabled`` options to ``TRUE`` in your ``my.cnf`` file and restart your server instance. Then, you can load the plugins.
-
-   The TokuDB Storage Engine was `declared as deprecated <https://www.percona.com/doc/percona-server/8.0/release-notes/Percona-Server-8.0.13-3.html>`__ in Percona Server for MySQL 8.0. For more information, see the Percona blog post: `Heads-Up: TokuDB Support Changes and Future Removal from Percona Server for MySQL 8.0 <https://www.percona.com/blog/2021/05/21/tokudb-support-changes-and-future-removal-from-percona-server-for-mysql-8-0/>`__.
-
-Percona *TokuBackup* is an open-source hot backup utility for *MySQL* servers running the *TokuDB* storage engine (including *Percona Server for MySQL* and *MariaDB*). It does not lock your database during backup. The *TokuBackup* library intercepts system calls that write files and duplicates the writes to the backup directory.
-
-.. note:: This feature is currently considered *tech preview* and should not be used in a production environment. 
-
-.. contents::
-   :local:
-
-Installing From Binaries
-------------------------
-
-The installation of *TokuBackup* can be performed with the **ps-admin** script.
-
-To install *Percona TokuBackup* complete the following steps. Run the following commands as root or by using the **sudo** command.
-
-1. Run **ps-admin.enable-tokubackup** to add the ``preload-hotbackup`` option into **[mysqld_safe]** section of :file:`my.cnf`.
-
-   .. admonition:: Output
-
-      .. code-block:: bash
-
-	 Checking SELinux status...
-	 INFO: SELinux is disabled.
-
-	 Checking if preload-hotbackup option is already set in config file...
-	 INFO: Option preload-hotbackup is not set in the config file.
-
-	 Checking TokuBackup plugin status...
-	 INFO: TokuBackup plugin is not installed.
-
-	 Adding preload-hotbackup option into /etc/my.cnf
-	 INFO: Successfully added preload-hotbackup option into /etc/my.cnf
-	 PLEASE RESTART MYSQL SERVICE AND RUN THIS SCRIPT AGAIN TO FINISH INSTALLATION!
-
-2. Restart mysql service: :bash:`service mysql restart
-3. Run :program:`ps-admin --enable-tokubackup` again to finish the installation of the *TokuBackup* plugin.
-
-   .. admonition:: Output
-
-      .. code-block:: bash
-
-	 Checking SELinux status...
-	 INFO: SELinux is disabled.
-
-	 Checking if preload-hotbackup option is already set in config file...
-	 INFO: Option preload-hotbackup is set in the config file.
-
-	 Checking TokuBackup plugin status...
-	 INFO: TokuBackup plugin is not installed.
-
-	 Checking if Percona Server is running with libHotBackup.so preloaded...
-	 INFO: Percona Server is running with libHotBackup.so preloaded.
-
-	 Installing TokuBackup plugin...
-	 INFO: Successfully installed TokuBackup plugin.
-
-Making a Backup
----------------
-
-To run *Percona TokuBackup*, the backup destination directory must
-exist, be writable and owned by the same user under which *MySQL*
-server is running (usually ``mysql``) and empty.
-
-Once this directory is created, the backup can be run using the
-following command:
-
-.. code-block:: mysql
-
-   mysql> set tokudb_backup_dir='/path_to_empty_directory';
-
-.. note::
-
-   Setting the :ref:`tokudb_backup_dir` variable automatically
-   starts the backup process to the specified directory. Percona
-   TokuBackup will take full backup each time, currently there is no
-   incremental backup option
-
-If you get any error on this step (e.g. caused by some
-misconfiguration), the `Reporting Errors`_ section explains how to
-find out the reason.
-
-Restoring From Backup
----------------------
-
-*Percona TokuBackup* does not have any functionality for restoring a
-backup. You can use :command:`rsync` or :command:`cp` to restore the
-files. You should check that the restored files have the correct
-ownership and permissions.
-
-.. note::
-
-   Make sure that the datadir is empty and that *MySQL* server is shut
-   down before restoring from backup. You can't restore to a datadir
-   of a running mysqld instance (except when importing a partial
-   backup).
-
-The following example shows how you might use the :command:`rsync` command to restore the backup:
-
-.. code-block:: bash
-
-   $ rsync -avrP /data/backup/ /var/lib/mysql/
-
-Since attributes of files are preserved, in most cases you will need to change their ownership to *mysql* before starting the database server. Otherwise, the files will be owned by the user who created the backup.
-
-.. code-block:: bash
-
-  $ chown -R mysql:mysql /var/lib/mysql
-
-If you have changed default *TokuDB* data directory (:ref:`tokudb_data_dir`) or *TokuDB* log directory (:ref:`tokudb_log_dir`) or both of them, you will see separate folders for each setting in backup directory after taking backup. You'll need to restore each folder separately:
-
-.. code-block:: bash
-
-  $ rsync -avrP /data/backup/mysql_data_dir/ /var/lib/mysql/
-  $ rsync -avrP /data/backup/tokudb_data_dir/ /path/to/original/tokudb_data_dir/
-  $ rsync -avrP /data/backup/tokudb_log_dir/ /path/to/original/tokudb_log_dir/
-  $ chown -R mysql:mysql /var/lib/mysql
-  $ chown -R mysql:mysql /path/to/original/tokudb_data_dir
-  $ chown -R mysql:mysql /path/to/original/tokudb_log_dir
-
-Advanced Configuration
-----------------------
-
-.. contents::
-   :local:
-
-Monitoring Progress
-*******************
-
-*TokuBackup* updates the *PROCESSLIST* state while the backup is in progress. You can see the output by running ``SHOW PROCESSLIST`` or ``SHOW FULL PROCESSLIST``.
-
-Excluding Source Files
-**********************
-
-You can exclude certain files and directories based on a regular expression set in the :ref:`tokudb_backup_exclude` session variable. If the source file name matches the excluded regular expression, then the source file is excluded from backup.
-
-For example, to exclude all :file:`lost+found` directories from backup, use the following command:
-
-.. code-block:: mysql
-
-  mysql> SET tokudb_backup_exclude='/lost\\+found($|/)';
-
-.. note::
-
-   The server ``pid`` file is excluded by default. If you're providing your own
-   additions to the exclusions and have the ``pid`` file in the default
-   location, you will need to add the mysqld_safe.pid entry.
-
-Throttling Backup Rate
-**********************
-
-You can throttle the backup rate using the :ref:`tokudb_backup_throttle` session-level variable. This variable throttles the write rate in bytes per second of the backup to prevent TokuBackup from crowding out other jobs in the system. The default and max value is 18446744073709551615.
-
-.. code-block:: mysql
-
-  mysql> SET tokudb_backup_throttle=1000000;
-
-Restricting Backup Target
-*************************
-
-You can restrict the location of the destination directory where the backups can be located using the :ref:`tokudb_backup_allowed_prefix` system-level variable. Attempts to backup to a location outside of the specified directory or its children will result in an error.
-
-The default is ``null``, backups have no restricted locations. This read-only variable can be set in the :file:`my.cnf` configuration file and displayed with the ``SHOW VARIABLES`` command:
-
-.. code-block:: mysql
-
-  mysql> SHOW VARIABLES LIKE 'tokudb_backup_allowed_prefix';
-  +------------------------------+-----------+
-  | Variable_name                | Value     |
-  +------------------------------+-----------+
-  | tokudb_backup_allowed_prefix | /dumpdir  |
-  +------------------------------+-----------+
-
-
-Reporting Errors
-****************
-
-*Percona TokuBackup* uses two variables to capture errors. They are :ref:`tokudb_backup_last_error` and :ref:`tokudb_backup_last_error_string`. When *TokuBackup* encounters an error, these will report on the error number and the error string respectively. For example, the following output shows these parameters following an attempted backup to a directory that was not empty:
-
-.. code-block:: mysql
-
-  mysql> SET tokudb_backup_dir='/tmp/backupdir';
-  ERROR 1231 (42000): Variable 'tokudb_backup_dir' can't be set to the value of '/tmp/backupdir'
-
-  mysql> SELECT @@tokudb_backup_last_error;
-  +----------------------------+
-  | @@tokudb_backup_last_error |
-  +----------------------------+
-  |                         17 |
-  +----------------------------+
-
-  mysql> SELECT @@tokudb_backup_last_error_string;
-  +---------------------------------------------------+
-  | @@tokudb_backup_last_error_string                 |
-  +---------------------------------------------------+
-  | tokudb backup couldn't create needed directories. |
-  +---------------------------------------------------+
-
-Using TokuDB Hot Backup for Replication
-***************************************
-
-TokuDB Hot Backup makes a transactionally consistent copy of the TokuDB
-files while applications read and write to these files. The TokuDB hot
-backup library intercepts certain system calls that writes files and duplicates
-the writes on backup files while copying files to the backup directory. The
-copied files contain the same content as the original files.
-
-TokuDB Hot Backup also has an API. This API includes the ``start capturing`` and
-``stop capturing`` commands. The "capturing" command starts the process, when a
-portion of a file is copied to the backup location, and this portion is changed,
-these changes are also applied to the backup location.
-
-Replication often uses backup replication to create replicas. You must know the
-last executed global transaction identifier (GTID) or binary log position both
-for the replica and source configuration.
-
-To lock tables, use ``FLUSH TABLE WITH READ LOCK`` or use the smart locks like
-``LOCK TABLES FOR BACKUP`` or ``LOCK BINLOG FOR BACKUP``.
-
-During the copy process, the binlog is flushed, and the changes are copied to
-backup by the "capturing" mechanism. After everything has been copied, and the
-"capturing" mechanism is still running, use the ``LOCK BINLOG FOR BACKUP``.
-After this statement is executed, the binlog is flushed, the changes are
-captured, and any queries that could change the binlog position or executed GTID
-are blocked.
-
-After this command, we can stop capturing and retrieve the last executed GTID or
-binlog log position and unlock the binlog.
-
-After a backup is taken, there are the following files in the backup directory:
-
-* tokubackup_slave_info
-* tokubackup_binlog_info
-
-These files contain information for replica and source. You can use this
-information to start a new replica from the source or replica.
-
-The ``SHOW MASTER STATUS`` and ``SHOW SLAVE STATUS`` commands provide the
-information.
-
-.. important::
-
-    As of *MySQL* 8.0.22, the ``SHOW SLAVE STATUS`` statement is
-    `deprecated <https://dev.mysql.com/doc/refman/8.0/en/show-replicas.html>`_.
-    Use ``SHOW REPLICA STATUS`` instead.
-    
-In specific binlog formats, a binary log event can contain statements that
-produce temporary tables on the replica side, and the result of further statements
-may depend on the temporary table content. Typically, temporary tables are not
-selected for backup because they are created in a separate directory. A backup
-created with temporary tables created by binlog events can cause issues when
-restored because the temporary tables are not restored. The data may be
-inconsistent.
-
-The following system variables :ref:`--tokudb-backup-safe-slave`, which
-enables or disables the safe-slave mode, and
-:ref:`--tokudb-backup-safe-slave-timeout`, which defines the maximum amount
-of time in seconds to wait until temporary tables disappear.  The
-``safe-slave`` mode, when used with ``LOCK BINLOG FOR BACKUP``, the replica SQL
-thread is stopped and checked to see if temporary tables produced by the replica
-exist or do not exist. If temporary tables exist, the replica SQL thread is
-restarted until there are no temporary tables or a defined timeout is reached.
-
-You should not use this option for group-replication.
-Create a Backup with a Timestamp
-*********************************
-
-If you plan to store more than one backup in a location, you should add a
-timestamp to the backup directory name.
-
-A sample Bash script has this information:
-
-.. code-block:: bash
-
-   #!/bin/bash
-
-   tm=$(date "+%Y-%m-%d-%H-%M-%S");
-   backup_dir=$PWD/backup/$tm;
-   mkdir -p $backup_dir;
-   bin/mysql -uroot -e "set tokudb_backup_dir='$backup_dir'"
-
-Limitations and known issues
-----------------------------
-
-* You must disable *InnoDB* asynchronous IO if backing up *InnoDB* tables with *TokuBackup*. Otherwise you will have inconsistent, unrecoverable backups. The appropriate setting is ``innodb_use_native_aio=0``.
-
-* To be able to run Point-In-Time-Recovery you'll need to manually get the binary log position.
-
-* Transactional storage engines (*TokuDB* and *InnoDB*) will perform recovery on the backup copy of the database when it is first started.
-
-* Tables using non-transactional storage engines (*MyISAM*) are not locked during the copy and may report issues when starting up the backup. It is best to avoid operations that modify these tables at the end of a hot backup operation (adding/changing users, stored procedures, etc.).
-
-* The database is copied locally to the path specified in :file:`/path/to/backup`. This folder must exist, be writable, be empty, and contain enough space for a full copy of the database.
-
-* *TokuBackup* always makes a backup of the *MySQL* :ref:`datadir` and optionally the :ref:`tokudb_data_dir`, :ref:`tokudb_log_dir`, and the binary log folder. The latter three are only backed up separately if they are not the same as or contained in the *MySQL* :ref:`datadir`. None of these three folders can be a parent of the *MySQL* :ref:`datadir`.
-
-* No other directory structures are supported. All *InnoDB*, *MyISAM*, and other storage engine files must be within the *MySQL* :ref:`datadir`.
-
-* *TokuBackup* does not follow symbolic links.
-
-* *TokuBackup* does not backup *MySQL* configuration file(s).
-
-* *TokuBackup* does not backup tablespaces if they are out of :ref:`datadir`.
-
-* Due to upstream bug :mysqlbug:`80183`, *TokuBackup* can't recover backed-up table data if backup was taken while running ``OPTIMIZE TABLE`` or ``ALTER TABLE ... TABLESPACE``.
-
-* *TokuBackup* doesn't support incremental backups.
diff --git a/doc/source/tokudb/tokudb_background_analyze_table.rst b/doc/source/tokudb/tokudb_background_analyze_table.rst
deleted file mode 100644
index f6bf1ea2019d..000000000000
--- a/doc/source/tokudb/tokudb_background_analyze_table.rst
+++ /dev/null
@@ -1,232 +0,0 @@
-.. _tokudb_background_analyze_table:
-
-===============================
-TokuDB Background ANALYZE TABLE
-===============================
-
-.. Important:: 
-
-   Starting with :ref:`8.0.28-19`, the TokuDB storage engine is no longer supported. We have removed the storage engine from the installation packages and disabled the storage engine in our binary builds.
-
-   Starting with :ref:`8.0.26-16`, the binary builds and packages include but disable the TokuDB storage engine plugins. The ``tokudb_enabled`` option and the ``tokudb_backup_enabled`` option control the state of the plugins and have a default setting of ``FALSE``. The result of attempting to load the plugins are the plugins fail to initialize and print a deprecation message.
-
-   We recommend :ref:`migrate-myrocks`. To enable the plugins to migrate to another storage engine, set the ``tokudb_enabled`` and ``tokudb_backup_enabled`` options to ``TRUE`` in your ``my.cnf`` file and restart your server instance. Then, you can load the plugins.
-
-   The TokuDB Storage Engine was `declared as deprecated <https://www.percona.com/doc/percona-server/8.0/release-notes/Percona-Server-8.0.13-3.html>`__ in Percona Server for MySQL 8.0. For more information, see the Percona blog post: `Heads-Up: TokuDB Support Changes and Future Removal from Percona Server for MySQL 8.0 <https://www.percona.com/blog/2021/05/21/tokudb-support-changes-and-future-removal-from-percona-server-for-mysql-8-0/>`__.
-
-*Percona Server for MySQL* has an option to automatically analyze tables in the background based on a measured change in data. This has been done by implementing the background job manager that can perform operations on a background thread. 
-
-Background Jobs
-===============
-
-Background jobs and schedule are transient in nature and are not persisted anywhere. Any currently running job will be terminated on shutdown and all scheduled jobs will be forgotten about on server restart. There can't be two jobs on the same table scheduled or running at any one point in time. If you manually invoke an ``ANALYZE TABLE`` that conflicts with either a pending or running job, the running job will be canceled and the users task will run immediately in the foreground. All the scheduled and running background jobs can be viewed by querying the :ref:`TOKUDB_BACKGROUND_JOB_STATUS` table.
-
-New :ref:`tokudb_analyze_in_background` variable has been implemented in order to control if the ``ANALYZE TABLE`` will be dispatched to the background process or if it will be running in the foreground. 
-To control the function of ``ANALYZE TABLE`` a new :ref:`tokudb_analyze_mode` variable has been implemented. This variable offers options to cancel any running or scheduled job on the specified table (``TOKUDB_ANALYZE_CANCEL``), use existing analysis algorithm (``TOKUDB_ANALYZE_STANDARD``), or to recount the logical rows in table and update persistent count (``TOKUDB_ANALYZE_RECOUNT_ROWS``).
-
-``TOKUDB_ANALYZE_RECOUNT_ROWS`` is a new mechanism that is used to perform a logical recount of all rows in a table and persist that as the basis value for the table row estimate. This mode was added for tables that have been upgraded from an older version of *TokuDB* that only reported physical row counts and never had a proper logical row count. Newly created tables/partitions will begin counting logical rows correctly from their creation and should not need to be recounted unless some odd edge condition causes the logical count to become inaccurate over time. This analysis mode has no effect on the table cardinality counts. It will take the currently set session values for :ref:`tokudb_analyze_in_background`, and :ref:`tokudb_analyze_throttle`. Changing the global or session instances of these values after scheduling will have no effect on the job.
-
-Any background job, both pending and running, can be canceled by setting the :ref:`tokudb_analyze_mode` to ``TOKUDB_ANALYZE_CANCEL`` and issuing the ``ANALYZE TABLE`` on the table for which you want to cancel all the jobs for.
-
-Auto analysis
-=============
-
-To implement the background analysis and gathering of cardinality statistics on a *TokuDB* tables new ``delta`` value is now maintained in memory for each *TokuDB* table. This value is not persisted anywhere and it is reset to ``0`` on a server start. It is incremented for each ``INSERT/UPDATE/DELETE`` command and ignores the impact of transactions (rollback specifically). When this delta value exceeds the :ref:`tokudb_auto_analyze` percentage of rows in the table an analysis is performed according to the current session's settings. Other analysis for this table will be disabled until this analysis completes. When this analysis completes, the delta is reset to ``0`` to begin recalculating table changes for the next potential analysis. 
-
-Status values are now reported to server immediately upon completion of any analysis (previously new status values were not used until the table has been closed and re-opened). Half-time direction reversal of analysis has been implemented, meaning that if a :ref:`tokudb_analyze_time` is in effect and the analysis has not reached the half way point of the index by the time :ref:`tokudb_analyze_time`/2 has been reached: it will stop the forward progress and restart the analysis from the last/rightmost row in the table, progressing leftwards and keeping/adding to the status information accumulated from the first half of the scan.
-
-For small ratios of ``table_rows`` / :ref:`tokudb_auto_analyze`, auto analysis will be run for almost every change. The trigger formula is: ``if (table_delta >= ((table_rows * tokudb_auto_analyze) / 100))`` then run ``ANALYZE TABLE``. If a user manually invokes an ``ANALYZE TABLE`` and :ref:`tokudb_auto_analyze` is enabled and there are no conflicting background jobs, the users ``ANALYZE TABLE`` will behave exactly as if the delta level has been exceeded in that the analysis is executed and delta reset to ``0`` upon completion.
-
-System Variables
-================
-
-.. _tokudb_analyze_in_background:
-
-.. rubric:: ``tokudb_analyze_in_background``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - Yes
-   * - Config file
-     - Yes
-   * - Scope
-     - Global/Session
-   * - Dynamic
-     - Yes
-   * - Data type
-     - Boolean
-   * - Default
-     - ``ON``
-
-When this variable is set to ``ON``  it will dispatch any ``ANALYZE TABLE`` job to a background process and return immediately, otherwise ``ANALYZE TABLE`` will run in foreground/client context.
-
-.. _tokudb_analyze_mode:
-
-.. rubric:: ``tokudb_analyze_mode``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - Yes
-   * - Config file
-     - Yes
-   * - Scope
-     - Global/Session
-   * - Dynamic
-     - Yes
-   * - Data type
-     - ENUM
-   * - Default
-     - ``TOKUDB_ANALYZE_STANDARD``
-   * - Range
-     - ``TOKUDB_ANALYZE_CANCEL``, ``TOKUDB_ANALYZE_STANDARD``, ``TOKUDB_ANALYZE_RECOUNT_ROWS``
-
-This variable is used to control the function of ``ANALYZE TABLE``. Possible values are:
-
- * ``TOKUDB_ANALYZE_CANCEL`` - Cancel any running or scheduled job on the specified table. 
- * ``TOKUDB_ANALYZE_STANDARD`` - Use existing analysis algorithm. This is the standard table cardinality analysis mode used to obtain cardinality statistics for a tables and its indexes. It will take the currently set session values for :ref:`tokudb_analyze_time`, :ref:`tokudb_analyze_in_background`, and :ref:`tokudb_analyze_throttle` at the time of its scheduling, either via a user invoked ``ANALYZE TABLE`` or an auto schedule as a result of :ref:`tokudb_auto_analyze` threshold being hit. Changing the global or session instances of these values after scheduling will have no effect on the scheduled job.
- * ``TOKUDB_ANALYZE_RECOUNT_ROWS`` - Recount logical rows in table and update persistent count. This is a new mechanism that is used to perform a logical recount of all rows in a table and persist that as the basis value for the table row estimate. This mode was added for tables that have been upgraded from an older version of *TokuDB*/PerconaFT that only reported physical row counts and never had a proper logical row count. Newly created tables/partitions will begin counting logical rows correctly from their creation and should not need to be recounted unless some odd edge condition causes the logical count to become inaccurate over time. This analysis mode has no effect on the table cardinality counts. It will take the currently set session values for :ref:`tokudb_analyze_in_background`, and :ref:`tokudb_analyze_throttle`. Changing the global or session instances of these values after scheduling will have no effect on the job.
-
-.. _tokudb_analyze_throttle:
-
-.. rubric:: ``tokudb_analyze_throttle``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - Yes
-   * - Config file
-     - Yes
-   * - Scope
-     - Global/Session
-   * - Dynamic
-     - Yes
-   * - Data type
-     - Numeric
-   * - Default
-     - 0
-
-This variable is used to define maximum number of keys to visit per second when performing ``ANALYZE TABLE`` with either a ``TOKUDB_ANALYZE_STANDARD`` or ``TOKUDB_ANALYZE_RECOUNT_ROWS``.
-
-.. _tokudb_analyze_time:
-
-.. rubric:: ``tokudb_analyze_time``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - Yes
-   * - Config file
-     - Yes
-   * - Scope
-     - Global/Session
-   * - Dynamic
-     - Yes
-   * - Data type
-     - Numeric
-   * - Default
-     - 5
-
-This session variable controls the number of seconds an analyze operation will spend on each index when calculating cardinality. Cardinality is shown by executing the following command:
-
-  .. code-block:: mysql
-
-    SHOW INDEXES FROM table_name;
-
-If an analyze is never performed on a table then the cardinality is ``1`` for primary key indexes and unique secondary indexes, and ``NULL`` (unknown) for all other indexes. Proper cardinality can lead to improved performance of complex SQL statements.
-
-.. _tokudb_auto_analyze:
-
-.. rubric:: ``tokudb_auto_analyze``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - Yes
-   * - Config file
-     - Yes
-   * - Scope
-     - Global/Session
-   * - Dynamic
-     - Yes
-   * - Data type
-     - Numeric
-   * - Default
-     - 30
-
-Percentage of table change as ``INSERT/UPDATE/DELETE`` commands to trigger an ``ANALYZE TABLE`` using the current session :ref:`tokudb_analyze_in_background`, :ref:`tokudb_analyze_mode`, :ref:`tokudb_analyze_throttle`, and :ref:`tokudb_analyze_time` settings. If this variable is enabled and :ref:`tokudb_analyze_in_background` variable is set to ``OFF``, analysis will be performed directly within the client thread context that triggered the analysis. **NOTE:** *InnoDB* enabled this functionality by default when they introduced it. Due to the potential unexpected new load it might place on a server, it is disabled by default in *TokuDB*.
-
-.. _tokudb_cardinality_scale_percent:
-
-.. rubric:: ``tokudb_cardinality_scale_percent``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - Yes
-   * - Config file
-     - Yes
-   * - Scope
-     - Global/Session
-   * - Dynamic
-     - Yes
-   * - Data type
-     - Numeric
-   * - Default
-     - 100
-   * - Range
-     - 0-100
-
-Percentage to scale table/index statistics when sending to the server to make an index appear to be either more or less unique than it actually is. *InnoDB* has a hard coded scaling factor of 50%. So if a table of 200 rows had an index with 40 unique values, InnoDB would return 200/40/2 or 2 for the index. The new TokuDB formula is the same but factored differently to use percent, for the same table.index (200/40 * :ref:`tokudb_cardinality_scale`) / 100, for a scale of 50% the result would also be 2 for the index.
-
-INFORMATION_SCHEMA Tables
-=========================
-
-.. _TOKUDB_BACKGROUND_JOB_STATUS:
-
-``INFORMATION_SCHEMA.TOKUDB_BACKGROUND_JOB_STATUS``
-
-.. list-table::
-      :header-rows: 1
-
-      * - Column Name
-        - Description
-      * - 'id'
-        - 'Simple monotonically incrementing job id, resets to ``0`` on server start.'
-      * - 'database_name'
-        - 'Database name'
-      * - 'table_name'
-        - 'Table name'
-      * - 'job_type'
-        - 'Type of job, either ``TOKUDB_ANALYZE_STANDARD`` or ``TOKUDB_ANALYZE_RECOUNT_ROWS``'
-      * - 'job_params'
-        - 'Param values used by this job in string format. For example: ``TOKUDB_ANALYZE_DELETE_TIME=1.0; TOKUDB_ANALYZE_TIME=5; TOKUDB_ANALYZE_THROTTLE=2048;``'
-      * - 'scheduler'
-        - 'Either ``USER`` or ``AUTO`` to indicate if the job was explicitly scheduled by a user or if it was scheduled as an automatic trigger'
-      * - 'scheduled_time'
-        - 'The time the job was scheduled'
-      * - 'started_time'
-        - 'The time the job was started'
-      * - 'status'
-        - 'Current job status if running. For example: ``ANALYZE TABLE standard db.tbl.idx 3 of 5 50% rows 10% time scanning forward``'
-
-This table holds the information on scheduled and running background ``ANALYZE TABLE`` jobs for *TokuDB* tables.
\ No newline at end of file
diff --git a/doc/source/tokudb/tokudb_faq.rst b/doc/source/tokudb/tokudb_faq.rst
deleted file mode 100644
index 96eba3154acf..000000000000
--- a/doc/source/tokudb/tokudb_faq.rst
+++ /dev/null
@@ -1,249 +0,0 @@
-.. _tokudb_faq:
-
-==========================
-Frequently Asked Questions
-==========================
-
-.. Important:: 
-
-   Starting with :ref:`8.0.28-19`, the TokuDB storage engine is no longer supported. We have removed the storage engine from the installation packages and disabled the storage engine in our binary builds.
-
-   Starting with :ref:`8.0.26-16`, the binary builds and packages include but disable the TokuDB storage engine plugins. The ``tokudb_enabled`` option and the ``tokudb_backup_enabled`` option control the state of the plugins and have a default setting of ``FALSE``. The result of attempting to load the plugins are the plugins fail to initialize and print a deprecation message.
-
-   We recommend :ref:`migrate-myrocks`. To enable the plugins to migrate to another storage engine, set the ``tokudb_enabled`` and ``tokudb_backup_enabled`` options to ``TRUE`` in your ``my.cnf`` file and restart your server instance. Then, you can load the plugins.
-
-   The TokuDB Storage Engine was `declared as deprecated <https://www.percona.com/doc/percona-server/8.0/release-notes/Percona-Server-8.0.13-3.html>`__ in Percona Server for MySQL 8.0. For more information, see the Percona blog post: `Heads-Up: TokuDB Support Changes and Future Removal from Percona Server for MySQL 8.0 <https://www.percona.com/blog/2021/05/21/tokudb-support-changes-and-future-removal-from-percona-server-for-mysql-8-0/>`__.
-
-This section contains frequently asked questions regarding *TokuDB* and related software. 
-
-.. contents::
-   :local:
-   :depth: 1
-
-Transactional Operations
-------------------------
-
-.. rubric:: What transactional operations does TokuDB support?
-
-*TokuDB* supports ``BEGIN TRANSACTION``, ``END TRANSACTION``, ``COMMIT``, ``ROLLBACK``, ``SAVEPOINT``, and ``RELEASE SAVEPOINT``. 
-
-TokuDB and the File System
---------------------------
-
-.. rubric:: How can I determine which files belong to the various tables and indexes in my schemas?
-
-The :ref:`tokudb_file_map` plugin lists all Fractal Tree Indexes and their corresponding data files. The ``internal_file_name`` is the actual file name (in the data folder).
-
-.. code-block:: sql
-
-   mysql> SELECT * FROM information_schema.tokudb_file_map;
-
-   +--------------------------+---------------------------------------+---------------+-------------+------------------------+
-   | dictionary_name          | internal_file_name                    | table_schema  | table_name  | table_dictionary_name  |
-   +--------------------------+---------------------------------------+---------------+-------------+------------------------+
-   | ./test/tmc-key-idx_col2  | ./_test_tmc_key_idx_col2_a_14.tokudb  | test          | tmc         | key_idx_col2           |
-   | ./test/tmc-main          | ./_test_tmc_main_9_14.tokudb          | test          | tmc         | main                   |
-   | ./test/tmc-status        | ./_test_tmc_status_8_14.tokudb        | test          | tmc         | status                 |
-   +--------------------------+---------------------------------------+---------------+-------------+------------------------+
-
-.. _tokudb_full_disks:
-
-Full Disks
-----------
-
-.. rubric:: What happens when the disk system fills up?
-
-The disk system may fill up during bulk load operations, such as ``LOAD DATA IN FILE`` or ``CREATE INDEX``, or during incremental operations like ``INSERT``.
-
-In the bulk case, running out of disk space will cause the statement to fail with ``ERROR 1030 (HY000): Got error 1 from storage engine``. The temporary space used by the bulk loader will be released. If this happens, you can use a separate physical disk for the temporary files (for more information, see :ref:`tokudb_tmp_dir`). If server runs out of free space *TokuDB* will assert the server to prevent data corruption to existing data files.
-
-Otherwise, disk space can run low during non-bulk operations. When available space is below a user-configurable reserve (5% by default) inserts are prevented and transactions that perform inserts are aborted. If the disk becomes completely full then *TokuDB* will freeze until some disk space is made available.
-
-Details about the disk system:
-
-* There is a free-space reserve requirement, which is a user-configurable parameter given as a percentage of the total space in the file system. The default reserve is five percent. This value is available in the global variable :ref:`tokudb_fs_reserve_percent`. We recommend that this reserve be at least half the size of your physical memory.
-
-  *TokuDB* polls the file system every five seconds to determine how much free space is available. If the free space dips below the reserve, then further table inserts are prohibited. Any transaction that attempts to insert rows will be aborted. Inserts are re-enabled when twice the reserve is available in the file system (so freeing a small amount of disk storage will not be sufficient to resume inserts). Warning messages are sent to the system error log when free space dips below twice the reserve and again when free space dips below the reserve.
-
-  Even with inserts prohibited it is still possible for the file system to become completely full. For example this can happen because another storage engine or another application consumes disk space.
-
-* If the file system becomes completely full, then *TokuDB* will freeze. It will not crash, but it will not respond to most SQL commands until some disk space is made available. When *TokuDB* is frozen in this state, it will still respond to the following command:
-
- .. code-block:: mysql
-
-    SHOW ENGINE TokuDB STATUS;
-
-    Make disk space available will allow the storage engine to continue running, but inserts will still be prohibited until twice the reserve is free.
-
- .. note:: 
- 
-   Engine status displays a field indicating if disk free space is above twice the reserve, below twice the reserve, or below the reserve. It will also display a special warning if the disk is completely full.
-
-* In order to make space available on this system you can:
-
-  * Add some disk space to the filesystem.
-
-  * Delete some non-TokuDB files manually.
-
-  * If the disk is not completely full, you may be able to reclaim space by aborting any transactions that are very old. Old transactions can consume large volumes of disk space in the recovery log.
-
-  * If the disk is not completely full, you can drop indexes or drop tables from your *TokuDB* databases.
-
-  * Deleting large numbers of rows from an existing table and then closing the table may free some space, but it may not. Deleting rows may simply leave unused space (available for new inserts) inside *TokuDB* data files rather than shrink the files (internal fragmentation).
-
-The fine print:
-
-* The *TokuDB* storage engine can use up to three separate file systems simultaneously, one each for the data, the recovery log, and the error log. All three are monitored, and if any one of the three falls below the relevant threshold then a warning message will be issued and inserts may be prohibited.
-
-* Warning messages to the error log are not repeated unless available disk space has been above the relevant threshold for at least one minute. This prevents excess messages in the error log if the disk free space is fluctuating around the limit.
-
-* Even if there are no other storage engines or other applications running, it is still possible for *TokuDB* to consume more disk space when operations such as row delete and query are performed, or when checkpoints are taken. This can happen because *TokuDB* can write cached information when it is time-efficient rather than when inserts are issued by the application, because operations in addition to insert (such as delete) create log entries, and also because of internal fragmentation of *TokuDB* data files.
-
-* The :ref:`tokudb_fs_reserve_percent` variable can not be changed once the system has started. It can only be set in :file:`my.cnf` or on the mysqld command line.
-
-Backup
-------
-
-.. rubric:: How do I back up a system with TokuDB tables?
-
-Taking backups with :ref:`toku_backup`
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-*TokuDB* is capable of performing online backups with :ref:`toku_backup`. To perform a backup, execute ``backup to '/path/to/backup';``. This will create backup of the server and return when complete. The backup can be used by another server using a copy of the binaries on the source server. You can view the progress of the backup by executing ``SHOW PROCESSLIST;``. *TokuBackup* produces a copy of your running *MySQL* server that is consistent at the end time of the backup process. The thread copying files from source to destination can be throttled by setting the :ref:`tokudb_backup_throttle` server variable. For more information check :ref:`toku_backup`.
-
-  The following conditions apply:
-
-  * Currently, *TokuBackup* only supports tables using the *TokuDB* storage engine and the *MyISAM* tables in the ``mysql`` database. 
-
-    .. warning:: You must disable *InnoDB* asynchronous IO if backing up *InnoDB* tables via *TokuBackup* utility. Otherwise you will have inconsistent, unrecoverable backups. The appropriate setting is :ref:`innodb_use_native_aio` to ``0``.
-
-  * Transactional storage engines (*TokuDB* and *InnoDB*) will perform recovery on the backup copy of the database when it is first started.
-
-  * Tables using non-transactional storage engines (*MyISAM*) are not locked during the copy and may report issues when starting up the backup. It is best to avoid operations that modify these tables at the end of a hot backup operation (adding/changing users, stored procedures, etc.).
-
-  * The database is copied locally to the path specified in :file:`/path/to/backup`. This folder must exist, be writable, be empty, and contain enough space for a full copy of the database.
-
-  * *TokuBackup* always makes a backup of the *MySQL* ``datadir`` and optionally the :ref:`tokudb_data_dir`, :ref:`tokudb_log_dir`, and the binary log folder. The latter three are only backed up separately if they are not the same as or contained in the *MySQL* ``datadir``. None of these three folders can be a parent of the *MySQL* ``datadir``.
-
-  * A folder is created in the given backup destination for each of the source folders.
-
-  * No other directory structures are supported. All *InnoDB*, *MyISAM*, and other storage engine files must be within the *MySQL* ``datadir``.
-
-  * *TokuBackup* does not follow symbolic links.
-
-Other options for taking backups
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-  *TokuDB* tables are represented in the file system with dictionary files, log files, and metadata files. A consistent copy of all of these files must be made during a backup. Copying the files while they may be modified by a running *MySQL* may result in an inconsistent copy of the database.
-
-  LVM snapshots may be used to get a consistent snapshot of all of the *TokuDB* files. The LVM snapshot may then be backed up at leisure.
-
-  The ``SELECT INTO OUTFILE`` statement or :program:`mysqldump` application may also be used to get a logical backup of the database.
-
-.. rubric:: References
-
-The MySQL 5.5 reference manual describes several backup methods and strategies. In addition, we recommend reading the backup and recovery chapter in the following book:
-
-*High Performance MySQL, 3rd Edition*, by Baron Schwartz, Peter Zaitsev, and Vadim Tkachenko, Copyright 2012, O'Reilly Media.
-
-.. rubric:: Cold Backup
- 
-When *MySQL* is shut down, a copy of the *MySQL* data directory, the *TokuDB* data directory, and the *TokuDB* log directory can be made. In the simplest configuration, the *TokuDB* files are stored in the *MySQL* data directory with all of other *MySQL* files. One merely has to back up this directory.
-
-.. rubric:: Hot Backup using mylvmbackup
-
-The :program:`mylvmbackup` utility, located on `Launchpad <https://launchpad.net/>`_, works with *TokuDB*. It does all of the magic required to get consistent copies of all of the *MySQL* tables, including *MyISAM* tables, *InnoDB* tables, etc., creates the LVM snapshots, and backs up the snapshots.
-
-.. rubric:: Logical Snapshots
-
-A logical snapshot of the databases uses a SQL statements to retrieve table rows and restore them. When used within a transaction, a consistent snapshot of the database can be taken. This method can be used to export tables from one database server and import them into another server.
-
-The ``SELECT INTO OUTFILE`` statement is used to take a logical snapshot of a database. The ``LOAD DATA INFILE`` statement is used to load the table data. Please see the *MySQL* 5.6 reference manual for details.
-
-.. note:: Please do not use the :program:`mysqlhotcopy` to back up *TokuDB* tables. This script is incompatible with *TokuDB*.
-
-Missing Log Files
------------------
-
-.. rubric:: What do I do if I delete my logs files or they are otherwise missing?
-
-You'll need to recover from a backup. It is essential that the log files be present in order to restart the database.
-
-Isolation Levels
-----------------
-
-.. rubric:: What is the default isolation level for TokuDB?
-
-It is repeatable-read (MVCC).
-
-.. rubric:: How can I change the isolation level?
-
-*TokuDB* supports repeatable-read, serializable, read-uncommitted and read-committed isolation levels (other levels are not supported). *TokuDB* employs pessimistic locking, and aborts a transaction when a lock conflict is detected.
-
-To guarantee that lock conflicts do not occur, use repeatable-read, read-uncommitted or read- committed isolation level.
-
-Lock Wait Timeout Exceeded
---------------------------
-
-.. rubric:: Why do my *MySQL* clients get lock timeout errors for my update queries? And what should my application do when it gets these errors?
-
-Updates can get lock timeouts if some other transaction is holding a lock on the rows being updated for longer than the *TokuDB* lock timeout. You may want to increase the this timeout.
-
-If an update deadlocks, then the transaction should abort and retry.
-
-For more information on diagnosing locking issues, see :ref:`Lock Visualization in TokuDB <tokudb_lock_visualization>`.
-
-Row Size
---------
-
-.. rubric:: What is the maximum row size?
-
-The maximum row size is 32 MiB.
-
-NFS & CIFS
-----------
-
-.. rubric:: Can the data directories reside on a disk that is NFS or CIFS mounted?
-
-Yes, we do have customers in production with NFS & CIFS volumes today. However, both of these disk types can pose a challenge to performance and data integrity due to their complexity. If you're seeking performance, the switching infrastructure and protocols of a traditional network were not conceptualized for low response times and can be very difficult to troubleshoot. If you're concerned with data integrity, the possible data caching at the NFS level can cause inconsistencies between the logs and data files that may never be detected in the event of a crash. If you are thinking of using a NFS or CIFS mount, we would recommend that you use synchronous mount options, which are available from the NFS mount man page, but these settings may decrease performance. For further discussion please look `here <http://www.mysqlperformanceblog.com/2010/07/30/storing-mysql-binary-logs-on-nfs-volume/>`_.
-
-Using Other Storage Engines
----------------------------
-
-.. rubric:: Can the MyISAM and InnoDB Storage Engines be used?
-
-*MyISAM* and *InnoDB* can be used directly in conjunction with *TokuDB*. Please note that you should not overcommit memory between *InnoDB* and *TokuDB*. The total memory assigned to both caches must be less than physical memory.
-
-.. rubric:: Can the Federated Storage Engines be used?
-
-The Federated Storage Engine can also be used, however it is disabled by default in *MySQL*. It can be enabled by either running mysqld with ``--federated`` as a command line parameter, or by putting ``federated`` in the ``[mysqld]`` section of the :file:`my.cnf` file.
-
-For more information see the *MySQL* 5.6 Reference Manual: `FEDERATED Storage Engine <http://dev.mysql.com/doc/refman/5.6/en/federated-storage-engine.html>`_.
-
-Using MySQL Patches with TokuDB
--------------------------------
-
-.. rubric:: Can I use MySQL source code patches with TokuDB?
-
-Yes, but you need to apply Percona patches as well as your patches to *MySQL* to build a binary that works with the Percona Fractal Tree library. 
-
-Truncate Table vs Delete from Table
------------------------------------
-
-.. rubric:: Which is faster, TRUNCATE TABLE or DELETE FROM TABLE?
-
-Use ``TRUNCATE TABLE`` whenever possible. A table truncation runs in constant time, whereas a ``DELETE FROM TABLE`` requires a row-by-row deletion and thus runs in time linear to the table size.
-
-Foreign Keys
-------------
-
-.. rubric:: Does TokuDB enforce foreign key constraints?
-
-No, *TokuDB* ignores foreign key declarations.
-
-Dropping Indexes
-----------------
-
-.. rubric:: Is dropping an index in TokuDB hot?
-
-No, the table is locked for the amount of time it takes the file system to delete the file associated with the index.
diff --git a/doc/source/tokudb/tokudb_file_management.rst b/doc/source/tokudb/tokudb_file_management.rst
deleted file mode 100644
index 04dd2409bb9d..000000000000
--- a/doc/source/tokudb/tokudb_file_management.rst
+++ /dev/null
@@ -1,319 +0,0 @@
-.. _tokudb_file_management:
-
-======================
-TokuDB file management
-======================
-
-.. Important:: 
-
-   Starting with :ref:`8.0.28-19`, the TokuDB storage engine is no longer supported. We have removed the storage engine from the installation packages and disabled the storage engine in our binary builds.
-
-   Starting with :ref:`8.0.26-16`, the binary builds and packages include but disable the TokuDB storage engine plugins. The ``tokudb_enabled`` option and the ``tokudb_backup_enabled`` option control the state of the plugins and have a default setting of ``FALSE``. The result of attempting to load the plugins are the plugins fail to initialize and print a deprecation message.
-
-   We recommend :ref:`migrate-myrocks`. To enable the plugins to migrate to another storage engine, set the ``tokudb_enabled`` and ``tokudb_backup_enabled`` options to ``TRUE`` in your ``my.cnf`` file and restart your server instance. Then, you can load the plugins.
-
-   The TokuDB Storage Engine was `declared as deprecated <https://www.percona.com/doc/percona-server/8.0/release-notes/Percona-Server-8.0.13-3.html>`__ in Percona Server for MySQL 8.0. For more information, see the Percona blog post: `Heads-Up: TokuDB Support Changes and Future Removal from Percona Server for MySQL 8.0 <https://www.percona.com/blog/2021/05/21/tokudb-support-changes-and-future-removal-from-percona-server-for-mysql-8-0/>`__.
-
-As mentioned in the :ref:`tokudb_files_and_file_types` *Percona FT* is
-extremely pedantic about validating its data set. If a file goes missing or
-can't be accessed, or seems to contain some nonsensical data, it will
-assert, abort or fail to start. It does this not to annoy you, but to try to
-protect you from doing any further damage to your data.
-
-This document contains examples of common file maintenance operations and
-instructions on how to safely execute these operations.
-
-The :ref:`tokudb_dir_per_db` option addressed two shortcomings the :ref:`renaming of data files
-<improved_table_renaming_functionality>` on table/index rename, and the ability
-to :ref:`group data files together <improved_directory_layout_functionality>`
-within a directory that represents a single database. This feature is enabled
-by default.
-
-The :ref:`tokudb_dir_cmd` variable can be used to edit the contents of the TokuDB/PerconaFT directory map.
-
-Moving TokuDB data files to a location outside of the default MySQL datadir
----------------------------------------------------------------------------
-
-*TokuDB* uses the location specified by the :ref:`tokudb_data_dir`
-variable for all of its data files. If the :ref:`tokudb_data_dir` variable
-is not explicitly set, *TokuDB* will use the location specified by the servers
-`datadir` for these files.
-
-The *TokuDB* data files are protected from concurrent process access by the
-``__tokudb_lock_dont_delete_me_data`` file that is located in the same
-directory as the *TokuDB* data files.
-
-*TokuDB* data files may be moved to other locations with symlinks left behind
-in their place. If those symlinks refer to files on other physical data
-volumes, the :ref:`tokudb_fs_reserve_percent` monitor will not traverse
-the symlink and monitor the real location for adequate space in the file
-system.
-
-To safely move your TokuDB data files:
-
-1. Shut the server down cleanly.
-
-#. Change the :ref:`tokudb_data_dir` in your :file:`my.cnf` configuration
-   file to the location where you wish to store your *TokuDB* data files.
-
-#. Create your new target directory.
-
-#. Move your ``*.tokudb`` files and your ``__tokudb_lock_dont_delete_me_data``
-   from the current location to the new location.
-
-#. Restart your server.
-
-Moving TokuDB temporary files to a location outside of the default MySQL datadir
---------------------------------------------------------------------------------
-
-*TokuDB* will use the location specified by the :ref:`tokudb_tmp_dir`
-variable for all of its temporary files. If :ref:`tokudb_tmp_dir` variable
-is not explicitly set, *TokuDB* will use the location specified by the
-:ref:`tokudb_data_dir` variable. If the :ref:`tokudb_data_dir`
-variable is also not explicitly set, *TokuDB* will use the location specified
-by the servers `datadir` for these files.
-
-*TokuDB* temporary files are protected from concurrent process access by the
-``__tokudb_lock_dont_delete_me_temp`` file that is located in the same
-directory as the *TokuDB* temporary files.
-
-If you locate your *TokuDB* temporary files on a physical volume that is
-different from where your *TokuDB* data files or recovery log files are
-located, the :ref:`tokudb_fs_reserve_percent` monitor will not monitor their location for adequate space in the file system.
-
-To safely move your *TokuDB* temporary files:
-
-1. Shut the server down cleanly. A clean shutdown will ensure that there are no
-   temporary files that need to be relocated.
-
-#. Change the :ref:`tokudb_tmp_dir` variable in your :file:`my.cnf`
-   configuration file to the location where you wish to store your new *TokuDB* temporary files.
-
-#. Create your new target directory.
-
-#. Move your ``__tokudb_lock_dont_delete_me_temp`` file from the current
-   location to the new location.
-
-#. Restart your server.
-
-Moving TokuDB recovery log files to a location outside of the default MySQL datadir
------------------------------------------------------------------------------------
-
-TokuDB will use the location specified by the :ref:`tokudb_log_dir`
-variable for all of its recovery log files. If the :ref:`tokudb_log_dir`
-variable is not explicitly set, TokuDB will use the location specified by the
-servers source/glossary.rst`datadir` for these files.
-
-The *TokuDB* recovery log files are protected from concurrent process access by
-the ``__tokudb_lock_dont_delete_me_logs`` file that is located in the same
-directory as the *TokuDB* recovery log files.
-
-TokuDB recovery log files may be moved to another location with symlinks left
-behind in place of the :ref:`tokudb_log_dir`. If that symlink refers to a directory on another physical data volume, the
-:ref:`tokudb_fs_reserve_percent` monitor will not traverse the symlink and
-monitor the real location for adequate space in the file system.
-
-To safely move your *TokuDB* recovery log files:
-
-1. Shut the server down cleanly.
-
-#. Change the :ref:`tokudb_log_dir` in your :file:`my.cnf` configuration
-   file to the location where you wish to store your TokuDB recovery log files.
-
-#. Create your new target directory.
-
-#. Move your ``log*.tokulog*`` files and your
-   ``__tokudb_lock_dont_delete_me_logs`` file from the current location to the
-   new location.
-
-#. Restart your server.
-
-.. _improved_table_renaming_functionality:
-
-Improved table renaming functionality
--------------------------------------
-
-When you rename a *TokuDB* table via SQL, the data files on disk keep their
-original names and only the mapping in the *Percona FT* directory file is
-changed to map the new dictionary name to the original internal file names.
-This makes it difficult to quickly match database/table/index names to their
-actual files on disk, requiring you to use the
-:ref:`refTOKUDB_FILE_MAP` table to cross reference.
-
-The :ref:`tokudb_dir_per_db` variable is implemented to address this issue.
-
-When :ref:`tokudb_dir_per_db` is enabled (``ON`` by default), this is no
-longer the case. When you rename a table, the mapping in the *Percona FT*
-directory file will be updated and the files will be renamed on disk to reflect
-the new table name.
-
-.. _improved_directory_layout_functionality:
-
-Improved directory layout functionality
----------------------------------------
-
-Many users have had issues with managing the huge volume of individual files
-that *TokuDB* and *Percona FT* use. The :ref:`tokudb_dir_per_db` variable
-addresses this issue.
-
-When :ref:`tokudb_dir_per_db` variable is enabled (``ON`` by default),
-all new tables and indices will be placed within their corresponding database
-directory within the :file:`tokudb_data_dir` or server `datadir`.
-
-If you have :ref:`tokudb_data_dir` variable set to something other than
-the server `datadir`, *TokuDB* will create a directory matching the name
-of the database, but upon dropping of the database, this directory will remain
-behind.
-
-Existing table files will not be automatically relocated to their corresponding
-database directory.
-
-You can easily move a tables data files into the new scheme and proper database
-directory with a few steps:
-
-.. code-block:: mysql
-
-  mysql> SET GLOBAL tokudb_dir_per_db=true;
-  mysql> RENAME TABLE <table> TO <tmp_table>;
-  mysql> RENAME TABLE <tmp_table> TO <table>;
-
-.. note::
-
-  Two renames are needed because *MySQL* doesn't allow you to rename a table to
-  itself. The first rename, renames the table to the temporary name and moves
-  the table files into the owning database directory. The second rename sets the
-  table name back to the original name. Tables can also be renamed/moved across
-  databases and will be placed correctly into the corresponding database
-  directory.
-
-.. warning::
-
-  You must be careful with renaming tables in case you have used any tricks to
-  create symlinks of the database directories on different storage volumes, the
-  move is not a simple directory move on the same volume but a physical copy
-  across volumes. This can take quite some time and prevent access to the table
-  being moved during the copy.
-
-System Variables
-================
-
-.. _tokudb_dir_cmd:
-
-.. rubric:: ``tokudb_dir_cmd``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - Yes
-   * - Config file
-     - Yes
-   * - Scope
-     - Global
-   * - Dynamic
-     - Yes
-   * - Data type
-     - String
-
-This variable is used to send commands to edit *TokuDB* directory files.
-
-.. warning::
-
-  Use this variable only if you know what you are doing otherwise it
-  **WILL** lead to data loss.
-
-Status Variables
-================
-
-.. _tokudb_dir_cmd_last_error:
-
-.. rubric:: ``tokudb_dir_cmd_last_error``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Scope
-     - Global
-   * - Data type
-     - Numeric
-
-This variable contains the error number of the last executed command by using
-the :ref:`tokudb_dir_cmd` variable.
-
-.. _tokudb_dir_cmd_last_error_string:
-
-.. rubric:: ``tokudb_dir_cmd_last_error_string``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Scope
-     - Global
-   * - Data type
-     - Numeric
-
-This variable contains the error string of the last executed command by using
-the :ref:`tokudb_dir_cmd` variable.
-
-
-..
-  .. _editing_tokudb_files_with_tokudb_dir_cmd:
-
-  Editing *TokuDB* directory map with :ref:`tokudb_dir_cmd`
-  --------------------------------------------------------------
-
-  .. note::
-
-    This feature is currently considered *Experimental*.
-
-  The :ref:`tokudb_dir_cmd` variable can be used to edit the *TokuDB*
-  directory map.  **WARNING:** Use this variable only if you know what you're
-  doing otherwise it **WILL** lead to data loss.
-
-  This method can be used if any kind of system issue causes the loss of specific
-  :file:`.tokudb` files for a given table, because the *TokuDB* tablespace file
-  mapping will then contain invalid (nonexistent) entries, visible in
-  :table:`INFORMATION_SCHEMA.TokuDB_file_map` table.
-
-  This variable is used to send commands to edit directory file. The format of
-  the command line is the following:
-
-  .. code-block:: text
-
-    command arg1 arg2 .. argn
-
-  I.e, if we want to execute some command the following statement can be used:
-
-  .. code-block:: mysql
-
-    SET tokudb_dir_cmd = "command arg1 ... argn"
-
-  Currently the following commands are available:
-
-  * ``attach dictionary_name internal_file_name`` - attach internal_file_name to
-    a dictionary_name, if the dictionary_name exists override the previous value,
-    add new record otherwise
-  * ``detach dictionary_name`` - remove record with corresponding
-    dictionary_name, the corresponding internal_file_name file stays untouched
-  * ``move old_dictionary_name new_dictionary_name`` - rename (only)
-    dictionary_name from old_dictionary_name to new_dictionary_name
-
-  Information about the dictionary_name and internal_file_name can be found in
-  the :table:`TokuDB_file_map` table:
-
-  .. code-block:: mysql
-
-    mysql> SELECT dictionary_name, internal_file_name FROM INFORMATION_SCHEMA.TokuDB_file_map;
-    +------------------------------+---------------------------------------------------------+
-    | dictionary_name              | internal_file_name                                      |
-    +------------------------------+---------------------------------------------------------+
-    | ./world/City-key-CountryCode | ./_world_sql_340a_39_key_CountryCode_12_1_1d_B_1.tokudb |
-    | ./world/City-main            | ./_world_sql_340a_39_main_12_1_1d_B_0.tokudb            |
-    | ./world/City-status          | ./_world_sql_340a_39_status_f_1_1d.tokudb               |
-    +------------------------------+---------------------------------------------------------+
diff --git a/doc/source/tokudb/tokudb_files_and_file_types.rst b/doc/source/tokudb/tokudb_files_and_file_types.rst
deleted file mode 100644
index 3fd17f6c88de..000000000000
--- a/doc/source/tokudb/tokudb_files_and_file_types.rst
+++ /dev/null
@@ -1,157 +0,0 @@
-.. _tokudb_files_and_file_types:
-
-===========================
-TokuDB files and file types
-===========================
-
-.. Important:: 
-
-   Starting with :ref:`8.0.28-19`, the TokuDB storage engine is no longer supported. We have removed the storage engine from the installation packages and disabled the storage engine in our binary builds.
-
-   Starting with :ref:`8.0.26-16`, the binary builds and packages include but disable the TokuDB storage engine plugins. The ``tokudb_enabled`` option and the ``tokudb_backup_enabled`` option control the state of the plugins and have a default setting of ``FALSE``. The result of attempting to load the plugins are the plugins fail to initialize and print a deprecation message.
-
-   We recommend :ref:`migrate-myrocks`. To enable the plugins to migrate to another storage engine, set the ``tokudb_enabled`` and ``tokudb_backup_enabled`` options to ``TRUE`` in your ``my.cnf`` file and restart your server instance. Then, you can load the plugins.
-
-   The TokuDB Storage Engine was `declared as deprecated <https://www.percona.com/doc/percona-server/8.0/release-notes/Percona-Server-8.0.13-3.html>`__ in Percona Server for MySQL 8.0. For more information, see the Percona blog post: `Heads-Up: TokuDB Support Changes and Future Removal from Percona Server for MySQL 8.0 <https://www.percona.com/blog/2021/05/21/tokudb-support-changes-and-future-removal-from-percona-server-for-mysql-8-0/>`__.
-
-The *TokuDB* file set consists of many different files that all serve various
-purposes.
-
-If you have any *TokuDB* data your data directory should look similar to this:
-
-.. code-block:: bash
-
-  root@server:/var/lib/mysql# ls -lah
-  ...
-  -rw-rw----  1 mysql mysql  76M Oct 13 18:45 ibdata1
-  ...
-  -rw-rw----  1 mysql mysql  16K Oct 13 15:52 tokudb.directory
-  -rw-rw----  1 mysql mysql  16K Oct 13 15:52 tokudb.environment
-  -rw-------  1 mysql mysql    0 Oct 13 15:52 __tokudb_lock_dont_delete_me_data
-  -rw-------  1 mysql mysql    0 Oct 13 15:52 __tokudb_lock_dont_delete_me_environment
-  -rw-------  1 mysql mysql    0 Oct 13 15:52 __tokudb_lock_dont_delete_me_logs
-  -rw-------  1 mysql mysql    0 Oct 13 15:52 __tokudb_lock_dont_delete_me_recovery
-  -rw-------  1 mysql mysql    0 Oct 13 15:52 __tokudb_lock_dont_delete_me_temp
-  -rw-rw----  1 mysql mysql  16K Oct 13 15:52 tokudb.rollback
-  ...
-
-This document lists the different types of *TokuDB* and *Percona Fractal Tree*
-files, explains their purpose, shows their location and how to move them
-around.
-
-tokudb.environment
-------------------
-
-This file is the root of the *Percona FT* file set and contains various bits of
-metadata about the system, such as creation times, current file format
-versions, etc.
-
-*Percona FT* will create/expect this file in the directory specified by the
-*MySQL* `datadir`.
-
-tokudb.rollback
----------------
-
-Every transaction within *Percona FT* maintains its own transaction rollback
-log. These logs are stored together within a single *Percona FT* dictionary
-file and take up space within the *Percona FT* cachetable (just like any other
-*Percona FT* dictionary).
-
-The transaction rollback logs will ``undo`` any changes made by a transaction
-if the transaction is explicitly rolled back, or rolled back via recovery as a
-result of an uncommitted transaction when a crash occurs.
-
-*Percona FT* will create/expect this file in the directory specified by the
-*MySQL* `datadir`.
-
-tokudb.directory
-----------------
-
-*Percona FT* maintains a mapping of a dictionary name (example:
-``sbtest.sbtest1.main``) to an internal file name (example:
-``_sbtest_sbtest1_main_xx_x_xx.tokudb``). This mapping is stored within this
-single *Percona FT* dictionary file and takes up space within the *Percona FT*
-cachetable just like any other *Percona FT* dictionary.
-
-*Percona FT* will create/expect this file in the directory specified by the
-*MySQL* `datadir`.
-
-Dictionary files
-----------------
-
-*TokuDB* dictionary (data) files store actual user data. For each *MySQL*
-table there will be:
-
-* One ``status`` dictionary that contains metadata about the table.
-
-* One ``main`` dictionary that stores the full primary key (an imaginary key is
-  used if one was not explicitly specified) and full row data.
-
-* One ``key`` dictionary for each additional key/index on the table.
-
-These are typically named:
-``_<database>_<table>_<key>_<internal_txn_id>.tokudb``
-
-*Percona FT* creates/expects these files in the directory specified by
-:ref:`tokudb_data_dir` if set, otherwise the *MySQL* ``datadir`` is used.
-
-Recovery log files
-------------------
-
-The *Percona FT* recovery log records every operation that modifies a
-*Percona FT* dictionary. Periodically, the system will take a snapshot of the
-system called a checkpoint. This checkpoint ensures that the modifications
-recorded within the *Percona FT* recovery logs have been applied to the
-appropriate dictionary files up to a known point in time and synced to disk.
-
-These files have a rolling naming convention, but use:
-``log<log_file_number>.tokulog<log_file_format_version>``.
-
-*Percona FT* creates/expects these files in the directory specified by
-:ref:`tokudb_log_dir` if set, otherwise the *MySQL* `datadir` is used.
-
-*Percona FT* does not track what log files should or shouldn't be present. Upon
-startup, it discovers the logs in the log directory, and replays them in order.
-If the wrong logs are present, the recovery aborts and possibly damages the
-dictionaries.
-
-Temporary files
----------------
-
-*Percona FT* might need to create some temporary files in order to perform some
-operations. When the bulk loader is active, these temporary files might grow to
-be quite large.
-
-As different operations start and finish, the files will come and go.
-
-There are no temporary files left behind upon a clean shutdown,
-
-*Percona FT* creates/expects these files in the directory specified by
-:ref:`tokudb_tmp_dir` if set. If not, the :ref:`tokudb_data_dir` is
-used if set, otherwise the *MySQL* `datadir` is used.
-
-Lock files
-----------
-
-*Percona FT* uses lock files to prevent multiple processes from accessing and
-writing to the files in the assorted *Percona FT* functionality areas. Each
-lock file will be in the same directory as the file(s) that it is protecting.
-
-These empty files are only used as semaphores across processes. They are safe
-to delete/ignore as long as no server instances are currently running and using
-the data set.
-
-``__tokudb_lock_dont_delete_me_environment``
-
-``__tokudb_lock_dont_delete_me_recovery``
-
-``__tokudb_lock_dont_delete_me_logs``
-
-``__tokudb_lock_dont_delete_me_data``
-
-``__tokudb_lock_dont_delete_me_temp``
-
-*Percona FT* is extremely pedantic about validating its data set. If a file
-goes missing or unfound, or seems to contain some nonsensical data, it will
-assert, abort or fail to start. It does this not to annoy you, but to try to
-protect you from doing any further damage to your data.
diff --git a/doc/source/tokudb/tokudb_fractal_tree_indexing.rst b/doc/source/tokudb/tokudb_fractal_tree_indexing.rst
deleted file mode 100644
index 2f5451df383b..000000000000
--- a/doc/source/tokudb/tokudb_fractal_tree_indexing.rst
+++ /dev/null
@@ -1,60 +0,0 @@
-.. _tokudb_fractal_tree_indexing:
-
-=============================
-TokuDB Fractal Tree Indexing
-=============================
-
-.. Important:: 
-
-   Starting with :ref:`8.0.28-19`, the TokuDB storage engine is no longer supported. We have removed the storage engine from the installation packages and disabled the storage engine in our binary builds.
-
-   Starting with :ref:`8.0.26-16`, the binary builds and packages include but disable the TokuDB storage engine plugins. The ``tokudb_enabled`` option and the ``tokudb_backup_enabled`` option control the state of the plugins and have a default setting of ``FALSE``. The result of attempting to load the plugins are the plugins fail to initialize and print a deprecation message.
-
-   We recommend :ref:`migrate-myrocks`. To enable the plugins to migrate to another storage engine, set the ``tokudb_enabled`` and ``tokudb_backup_enabled`` options to ``TRUE`` in your ``my.cnf`` file and restart your server instance. Then, you can load the plugins.
-
-   The TokuDB Storage Engine was `declared as deprecated <https://www.percona.com/doc/percona-server/8.0/release-notes/Percona-Server-8.0.13-3.html>`__ in Percona Server for MySQL 8.0. For more information, see the Percona blog post: `Heads-Up: TokuDB Support Changes and Future Removal from Percona Server for MySQL 8.0 <https://www.percona.com/blog/2021/05/21/tokudb-support-changes-and-future-removal-from-percona-server-for-mysql-8-0/>`__.
-
-Fractal Tree indexing is the technology behind TokuDB and is
-protected by multiple patents. This type of index enhances the tradional B-tree
-data structure used in other database engines, and optimizes performance for
-modern hardware and data sets.
-
-Background
------------------
-
-The B-tree data structure was optimized for large blocks of data but the
-performance is limited by I/O bandwidth. The size of a production database
-generally exceeds available main memory. Most leaves in a tree are stored on
-disk, not in RAM. If a leaf is not in main memory inserting information requires
-a disk I/O operation. Continually adding RAM to keep pace with data's
-growth is too expensive.
-
-Buffers
------------
-
-Like a B-tree structure, a fractal tree index is a tree data structure, but each
-node has buffers that allow messages to be stored. Insertions, deletions, and
-updates are inserted into the buffers as messages.
-Buffers let each disk operation be more efficient by writing large amounts of
-data. Buffers also avoid the common B-tree scenario when disk writes change only
-a small amount of data.
-
-In fractal tree indexes, non-leaf (internal) nodes have child nodes. The
-number of child nodes is variable and based on a pre-defined range. When data is
-inserted or deleted from a node, the number of child nodes changes. Internal nodes may
-join or split to maintain the defined range. When the buffer is full, the
-mesages are flushed to children nodes.
-
-Fractal tree index data structure involves the same algorithmic complexity as
-B-tree queries. There is no data loss because the queries follow the path from
-the root to leaf and pass through all messages. A query knows the current state
-of data even if changes have not been propagated to the corresponding leaves.
-
-Each message is stamped with a unique message sequence number (MSN) when the
-message is stored in a non-leaf node message buffer. The MSN maintains the order
-of messages and ensures the messages are only applied once to leaf nodes when
-the leaf node is updated by messages.
-
-Buffers are also serialized to disk, messages in internal nodes are not lost in
-the case of a crash or outage. If a write happened after a checkpoint, but
-before a crash, recovery replays the operation from the log.
diff --git a/doc/source/tokudb/tokudb_installation.rst b/doc/source/tokudb/tokudb_installation.rst
deleted file mode 100644
index 04303db556cb..000000000000
--- a/doc/source/tokudb/tokudb_installation.rst
+++ /dev/null
@@ -1,263 +0,0 @@
-.. _tokudb_installation:
-
-================================================================================
- TokuDB Installation
-================================================================================
-
-.. Important:: 
-
-   Starting with :ref:`8.0.28-19`, the TokuDB storage engine is no longer supported. We have removed the storage engine from the installation packages and disabled the storage engine in our binary builds.
-
-   Starting with :ref:`8.0.26-16`, the binary builds and packages include but disable the TokuDB storage engine plugins. The ``tokudb_enabled`` option and the ``tokudb_backup_enabled`` option control the state of the plugins and have a default setting of ``FALSE``. The result of attempting to load the plugins are the plugins fail to initialize and print a deprecation message.
-
-   We recommend :ref:`migrate-myrocks`. To enable the plugins to migrate to another storage engine, set the ``tokudb_enabled`` and ``tokudb_backup_enabled`` options to ``TRUE`` in your ``my.cnf`` file and restart your server instance. Then, you can load the plugins.
-
-   The TokuDB Storage Engine was `declared as deprecated <https://www.percona.com/doc/percona-server/8.0/release-notes/Percona-Server-8.0.13-3.html>`__ in Percona Server for MySQL 8.0. For more information, see the Percona blog post: `Heads-Up: TokuDB Support Changes and Future Removal from Percona Server for MySQL 8.0 <https://www.percona.com/blog/2021/05/21/tokudb-support-changes-and-future-removal-from-percona-server-for-mysql-8-0/>`__.
-
-*Percona Server for MySQL* is compatible with the separately available *TokuDB* storage
-engine package. The *TokuDB* engine must be separately downloaded and then
-enabled as a plug-in component. This package can be installed alongside with
-standard *Percona Server for MySQL* 8.0 releases and does not require any specially
-adapted version of *Percona Server for MySQL*.
-
-The *TokuDB* storage engine is a scalable, ACID and MVCC compliant storage
-engine that provides indexing-based query improvements, offers online schema
-modifications, and reduces replica lag for both hard disk drives and flash
-memory. This storage engine is specifically designed for high performance on
-write-intensive workloads which is achieved with Fractal Tree indexing. To learn
-more about Fractal Tree indexing, you can visit the following `Wikipedia page
-<http://en.wikipedia.org/wiki/Fractal_tree_index>`_.
-
-.. warning::
-
-   Only the `Percona supplied
-   <http://www.percona.com/downloads/Percona-Server-8.0/LATEST/>`_
-   *TokuDB* engine should be used with *Percona Server for MySQL* 8.0. A *TokuDB*
-   engine downloaded from other sources is not compatible. *TokuDB*
-   file formats are not the same across *MySQL* variants. Migrating
-   from one variant to any other variant requires a logical data dump
-   and reload.
-
-Prerequisites
-================================================================================
-
-``libjemalloc`` library
---------------------------------------------------------------------------------
-
-*TokuDB* storage engine requires ``libjemalloc`` library 3.3.0 or
-greater. If the version in the distribution repository is lower than
-that you can use one from :ref:`Percona Software Repositories
-<installation>` or download it from somewhere else.
-
-If the ``libjemalloc`` wasn't installed and enabled before it will be
-automatically installed when installing the *TokuDB* storage engine
-package by using the :program:`apt`` or :program:`yum` package
-manager, but *Percona Server for MySQL* instance should be restarted for
-``libjemalloc`` to be loaded. This way ``libjemalloc`` will be loaded
-with ``LD_PRELOAD``. You can also enable ``libjemalloc`` by specifying
-:ref:`malloc-lib` variable in the ``[mysqld_safe]`` section of
-the :file:`my.cnf` file: ::
-
-  [mysqld_safe]
-  malloc-lib= /path/to/jemalloc
-
-Transparent huge pages
---------------------------------------------------------------------------------
-
-*TokuDB* won't be able to start if the transparent huge pages are
-enabled. `Transparent huge pages
-<https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Performance_Tuning_Guide/s-memory-transhuge.html>`_
-is feature available in the newer kernel versions. You can check if
-the Transparent huge pages are enabled with: :bash:`cat /sys/kernel/mm/transparent_hugepage/enabled`
-
-.. admonition:: Output
-
-   .. code-block:: bash
-
-      [always] madvise never
-
-If transparent huge pages are enabled and you try to start the TokuDB
-engine you'll get the following message in you :file:`error.log`: ::
-
- Transparent huge pages are enabled, according to /sys/kernel/mm/redhat_transparent_hugepage/enabled
- Transparent huge pages are enabled, according to /sys/kernel/mm/transparent_hugepage/enabled
-
-You can `disable
-<https://access.redhat.com/solutions/46111>`_
-transparent huge pages permanently by passing
-``transparent_hugepage=never`` to the kernel in your bootloader
-(**NOTE**: For this change to take an effect you'll need to reboot
-your server).
-
-You can disable the transparent huge pages by running the following
-command as root (**NOTE**: Setting this will last only until the
-server is rebooted):
-
-.. code-block:: bash
-
-   echo never > /sys/kernel/mm/transparent_hugepage/enabled
-   echo never > /sys/kernel/mm/transparent_hugepage/defrag
-
-Installation
-================================================================================
-
-The *TokuDB* storage engine for *Percona Server for MySQL* is currently
-available in our :ref:`apt <apt_repo>` and :ref:`yum <yum_repo>`
-repositories.
-
-You can install the *Percona Server for MySQL* with the *TokuDB* engine by using
-the respective package manager:
-
-:program:`yum`
-   :bash:`yum install percona-server-tokudb.x86_64`
-:program:`apt`
-   :bash:`apt install percona-server-tokudb`
-
-.. _tokudb_quick_install:
-
-Enabling the TokuDB Storage Engine
-================================================================================
-
-Once the *TokuDB* server package is installed, the following output is shown:
-
-.. admonition:: Output
-
-   * This release of Percona Server is distributed with TokuDB storage engine.
-     * Run the following script to enable the TokuDB storage engine in Percona Server:
-
-       :bash:`ps-admin --enable-tokudb -u <mysql_admin_user> -p[mysql_admin_pass] [-S <socket>] [-h <host> -P <port>]`
-
-     * See http://www.percona.com/doc/percona-server/8.0/tokudb/tokudb_installation.html for more installation details
-
-     * See http://www.percona.com/doc/percona-server/8.0/tokudb/tokudb_intro.html for an introduction to TokuDB
-
-*Percona Server for MySQL* has implemented :program:`ps-admin` to make the enabling the
-*TokuDB* storage engine easier. This script will automatically disable
-Transparent huge pages, if they're enabled, and install and enable the
-*TokuDB* storage engine with all the required plugins. You need to run
-this script as root or with :program:`sudo`. The script should only
-be used for local installations and should not be used to install
-TokuDB to a remote server. After you run the script
-with required parameters:
-
-*Percona Server for MySQL* has implemented ``ps_tokudb_admin`` script to make the enabling the *TokuDB* storage engine easier. This script will automatically disable Transparent huge pages, if they're enabled, and install and enable the *TokuDB* storage engine with all the required plugins. You need to run this script as root or with :program:`sudo`. The script should only be used for local installations and should not be used to install TokuDB to a remote server. After you run the script with required parameters:
-
-.. code-block:: bash
-
-   $ ps-admin --enable-tokudb -uroot -pPassw0rd
-
-Following output will be displayed:
-
-.. code-block:: bash
-
-   Checking if Percona server is running with jemalloc enabled...
-   >> Percona server is running with jemalloc enabled.
-
-   Checking transparent huge pages status on the system...
-   >> Transparent huge pages are currently disabled on the system.
-
-   Checking if thp-setting=never option is already set in config file...
-   >> Option thp-setting=never is not set in the config file.
-   >> (needed only if THP is not disabled permanently on the system)
-
-   Checking TokuDB plugin status...
-   >> TokuDB plugin is not installed.
-
-   Adding thp-setting=never option into /etc/mysql/my.cnf
-   >> Successfuly added thp-setting=never option into /etc/mysql/my.cnf
-
-   Installing TokuDB engine...
-   >> Successfuly installed TokuDB plugin.
-
-If the script returns no errors, *TokuDB* storage engine should be successfully enabled on your server. You can check it out by running :mysql:`SHOW ENGINES;`
-
-.. admonition:: Output
-
-   .. code-block:: mysql
-
-      ...
-      | TokuDB | YES | Tokutek TokuDB Storage Engine with Fractal Tree(tm) Technology | YES | YES | YES |
-      ...
-
-Enabling the TokuDB Storage Engine Manually
-===========================================
-
-If you don't want to use :program:`ps-admin` you'll need to manually install
-the storage engine ad required plugins.
-
-.. code-block:: mysql
-
-   INSTALL PLUGIN tokudb SONAME 'ha_tokudb.so';
-   INSTALL PLUGIN tokudb_file_map SONAME 'ha_tokudb.so';
-   INSTALL PLUGIN tokudb_fractal_tree_info SONAME 'ha_tokudb.so';
-   INSTALL PLUGIN tokudb_fractal_tree_block_map SONAME 'ha_tokudb.so';
-   INSTALL PLUGIN tokudb_trx SONAME 'ha_tokudb.so';
-   INSTALL PLUGIN tokudb_locks SONAME 'ha_tokudb.so';
-   INSTALL PLUGIN tokudb_lock_waits SONAME 'ha_tokudb.so';
-   INSTALL PLUGIN tokudb_background_job_status SONAME 'ha_tokudb.so';
-
-After the engine has been installed it should be present in the
-engines list. To check if the engine has been correctly installed and
-active: :mysql:`SHOW ENGINES;`
-
-.. admonition:: Output
-
-   .. code-block:: mysql
-
-      ...
-      | TokuDB | YES | Tokutek TokuDB Storage Engine with Fractal Tree(tm) Technology | YES | YES | YES |
-      ...
-
-To check if all the *TokuDB* plugins have been installed correctly you should run: :mysql:`SHOW PLUGINS;`
-
-.. admonition:: Output
-
-   .. code-block:: mysql
-
-      ...
-      | TokuDB                        | ACTIVE   | STORAGE ENGINE     | ha_tokudb.so | GPL     |
-      | TokuDB_file_map               | ACTIVE   | INFORMATION SCHEMA | ha_tokudb.so | GPL     |
-      | TokuDB_fractal_tree_info      | ACTIVE   | INFORMATION SCHEMA | ha_tokudb.so | GPL     |
-      | TokuDB_fractal_tree_block_map | ACTIVE   | INFORMATION SCHEMA | ha_tokudb.so | GPL     |
-      | TokuDB_trx                    | ACTIVE   | INFORMATION SCHEMA | ha_tokudb.so | GPL     |
-      | TokuDB_locks                  | ACTIVE   | INFORMATION SCHEMA | ha_tokudb.so | GPL     |
-      | TokuDB_lock_waits             | ACTIVE   | INFORMATION SCHEMA | ha_tokudb.so | GPL     |
-      | TokuDB_background_job_status  | ACTIVE   | INFORMATION SCHEMA | ha_tokudb.so | GPL     |
-      ...
-
-TokuDB Version
-==============
-
-*TokuDB* storage engine version can be checked with: :mysql:`SELECT @@tokudb_version;`
-
-.. admonition:: Output
-
-   .. code-block:: mysql
-
-      +------------------+
-      | @@tokudb_version |
-      +------------------+
-      | 8.0.13-3         |
-      +------------------+
-      1 row in set (0.00 sec)
-
-
-Upgrade
-=======
-
-Before upgrading to *Percona Server for MySQL* 8.0, make sure that your system is ready by
-running :program:`mysqlcheck`: :bash:`mysqlcheck -u root -p --all-databases
---check-upgrade`
-
-.. warning::
-
-   With partitioned tables that use the *TokuDB* or *MyRocks* storage engine, the
-   upgrade only works with native partitioning.
-
-.. seealso::
-
-   *MySQL* Documentation: Preparing Your Installation for Upgrade
-      https://dev.mysql.com/doc/refman/8.0/en/upgrade-prerequisites.html
-
-.. include:: ../.res/replace.txt
-.. include:: ../.res/replace.program.txt
diff --git a/doc/source/tokudb/tokudb_intro.rst b/doc/source/tokudb/tokudb_intro.rst
deleted file mode 100644
index 6d58dbbcd981..000000000000
--- a/doc/source/tokudb/tokudb_intro.rst
+++ /dev/null
@@ -1,172 +0,0 @@
-.. _tokudb_intro:
-
-================================================================================
-TokuDB Introduction
-================================================================================
-
-.. Important:: 
-
-   Starting with :ref:`8.0.28-19`, the TokuDB storage engine is no longer supported. We have removed the storage engine from the installation packages and disabled the storage engine in our binary builds.
-
-   Starting with :ref:`8.0.26-16`, the binary builds and packages include but disable the TokuDB storage engine plugins. The ``tokudb_enabled`` option and the ``tokudb_backup_enabled`` option control the state of the plugins and have a default setting of ``FALSE``. The result of attempting to load the plugins are the plugins fail to initialize and print a deprecation message.
-
-   We recommend :ref:`migrate-myrocks`. To enable the plugins to migrate to another storage engine, set the ``tokudb_enabled`` and ``tokudb_backup_enabled`` options to ``TRUE`` in your ``my.cnf`` file and restart your server instance. Then, you can load the plugins.
-
-   The TokuDB Storage Engine was `declared as deprecated <https://www.percona.com/doc/percona-server/8.0/release-notes/Percona-Server-8.0.13-3.html>`__ in Percona Server for MySQL 8.0. For more information, see the Percona blog post: `Heads-Up: TokuDB Support Changes and Future Removal from Percona Server for MySQL 8.0 <https://www.percona.com/blog/2021/05/21/tokudb-support-changes-and-future-removal-from-percona-server-for-mysql-8-0/>`__.
-
-*TokuDB* is a highly scalable, zero-maintenance downtime MySQL storage engine
-that delivers indexing-based query acceleration, improved replication
-performance, unparalleled compression, and live schema modification. The
-*TokuDB* storage engine is a scalable, ACID and MVCC compliant storage engine
-that provides indexing-based query improvements, offers online schema
-modifications, and reduces replica lag for both hard disk drives and flash
-memory. This storage engine is specifically designed for high performance on
-write-intensive workloads which is achieved with Fractal Tree indexing.
-
-*Percona Server for MySQL* is compatible with the separately available *TokuDB* storage
-engine package. The *TokuDB* engine must be separately downloaded and then
-enabled as a plug-in component. This package can be installed alongside with
-standard *Percona Server for MySQL* releases and does not require any specially adapted
-version of *Percona Server for MySQL*.
-
-.. warning::
-
-   Only the `Percona supplied
-   <http://www.percona.com/downloads/Percona-Server-8.0/LATEST/>`_ *TokuDB*
-   engine should be used with *Percona Server for MySQL*. A *TokuDB* engine downloaded
-   from other sources is not compatible. *TokuDB* file formats are not the same
-   across MySQL variants. Migrating from one variant to any other variant
-   requires a logical data dump and reload.
-
-Additional features unique to *TokuDB* include:
-
-- Up to 25x Data Compression
-- Fast Inserts
-- Eliminates Replica Lag with :ref:`Read Free Replication <tokudb_read_free_replication>`
-- Hot Schema Changes
-- Hot Index Creation - *TokuDB* tables support insertions, deletions and queries
-  with no down time while indexes are being added to that table
-- Hot column addition, deletion, expansion, and rename - *TokuDB* tables support
-  insertions, deletions and queries without down-time when an alter table adds,
-  deletes, expands, or renames columns
-- On-line Backup
-
-.. note::
-
-   The *TokuDB* storage engine does not support the ``nowait`` and
-   ``skip locked`` modifiers introduced in the *InnoDB* storage
-   engine with *MySQL* 8.0.
-
-For more information on installing and using *TokuDB* click on the following
-links:
-
-.. toctree::
-   :maxdepth: 1
-
-   tokudb_installation
-   using_tokudb
-   tokudb_quickstart
-   tokudb_variables
-   toku_backup
-   tokudb_troubleshooting
-   tokudb_faq
-   removing_tokudb
-
-Getting the Most from TokuDB
-----------------------------
-
-Compression
-   *TokuDB* compresses all data on disk, including indexes. Compression
-   lowers cost by reducing the amount of storage required and frees up disk
-   space for additional indexes to achieve improved query performance. Depending
-   on the compressibility of the data, we have seen compression ratios up to 25x
-   for high compression. Compression can also lead to improved performance since
-   less data needs to be read from and written to disk.
-
-Fast Insertions and Deletions
-   TokuDB's Fractal Tree technology enables fast
-   indexed insertions and deletions. Fractal Trees match B-trees in their
-   indexing sweet spot (sequential data) and are up to two orders of magnitude
-   faster for random data with high cardinality.
-
-Eliminates Replica Lag
-   *TokuDB* replication replicas can be configured to process
-   the replication stream with virtually no read IO. Uniqueness checking is
-   performed on the *TokuDB* source and can be skipped on all *TokuDB*
-   replica. Also, row based replication ensures that all before and after row
-   images are captured in the binary logs, so the *TokuDB* replicas can harness
-   the power of Fractal Tree indexes and bypass traditional read-modify-write
-   behavior. This "Read Free Replication" ensures that replication replicas do not
-   fall behind the source and can be used for read scaling, backups, and
-   disaster recovery, without sharding, expensive hardware, or limits on what
-   can be replicated.
-
-Hot Index Creation
-   *TokuDB* allows the addition of indexes to an existing table
-   while inserts and queries are being performed on that table. This means that
-   *MySQL* can be run continuously with no blocking of queries or insertions
-   while indexes are added and eliminates the down-time that index changes would
-   otherwise require.
-
-Hot Column Addition, Deletion, Expansion and Rename
-   *TokuDB* allows the addition
-   of new columns to an existing table, the deletion of existing columns from an
-   existing table, the expansion of ``char``, ``varchar``, ``varbinary``, and
-   ``integer`` type columns in an existing table, and the renaming of an
-   existing column while inserts and queries are being performed on that table.
-
-Online (Hot) Backup
-   The *TokuDB* can create backups of online database servers without downtime.
-
-Fast Indexing
-   In practice, slow indexing often leads users to choose a smaller
-   number of sub-optimal indexes in order to keep up with incoming data
-   rates. These sub-optimal indexes result in disproportionately slower queries,
-   since the difference in speed between a query with an index and the same
-   query when no index is available can be many orders of magnitude. Thus, fast
-   indexing means fast queries.
-
-Clustering Keys and Other Indexing Improvements
-   *TokuDB* tables are clustered on
-   the primary key. *TokuDB* also supports clustering secondary keys, providing
-   better performance on a broader range of queries. A clustering key includes
-   (or clusters) all of the columns in a table along with the key. As a result,
-   one can efficiently retrieve any column when doing a range query on a
-   clustering key. Also, with *TokuDB*, an auto-increment column can be used in
-   any index and in any position within an index. Lastly, *TokuDB* indexes can
-   include up to 32 columns.
-
-Less Aging/Fragmentation
-   *TokuDB* can run much longer, likely indefinitely,
-   without the need to perform the customary practice of dump/reload or
-   ``OPTIMIZE TABLE`` to restore database performance. The key is the
-   fundamental difference with which the Fractal Tree stores data on
-   disk. Since, by default, the Fractal Tree will store data in 4MB chunks
-   (pre-compression), as compared to InnoDB's 16KB, *TokuDB* has the ability to
-   avoid "database disorder" up to 250x better than InnoDB.
-
-Bulk Loader
-   *TokuDB* uses a parallel loader to create tables and offline
-   indexes. This parallel loader will use multiple cores for fast offline table
-   and index creation.
-
-Full-Featured Database
-   *TokuDB* supports fully ACID-compliant transactions, MVCC
-   (Multi-Version Concurrency Control), serialized isolation levels, row-level
-   locking, and XA. *TokuDB* scales with high number of client connections, even
-   for large tables.
-
-Lock Diagnostics
-   *TokuDB* provides users with the tools to diagnose locking and
-   deadlock issues. For more information, see :ref:`Lock Visualization in TokuDB
-   <tokudb_lock_visualization>`.
-
-Progress Tracking
-   Running ``SHOW PROCESSLIST`` when adding indexes provides
-   status on how many rows have been processed. Running ``SHOW PROCESSLIST``
-   also shows progress on queries, as well as insertions, deletions and
-   updates. This information is helpful for estimating how long operations will
-   take to complete.
-
-Fast Recovery
-   *TokuDB* supports very fast recovery, typically less than a minute.
diff --git a/doc/source/tokudb/tokudb_performance_schema.rst b/doc/source/tokudb/tokudb_performance_schema.rst
deleted file mode 100644
index c9d58dcdd227..000000000000
--- a/doc/source/tokudb/tokudb_performance_schema.rst
+++ /dev/null
@@ -1,131 +0,0 @@
-.. _tokudb_performance_schema:
-
-=======================================
-TokuDB Performance Schema Integration
-=======================================
-
-.. Important:: 
-
-   Starting with :ref:`8.0.28-19`, the TokuDB storage engine is no longer supported. We have removed the storage engine from the installation packages and disabled the storage engine in our binary builds.
-
-   Starting with :ref:`8.0.26-16`, the binary builds and packages include but disable the TokuDB storage engine plugins. The ``tokudb_enabled`` option and the ``tokudb_backup_enabled`` option control the state of the plugins and have a default setting of ``FALSE``. The result of attempting to load the plugins are the plugins fail to initialize and print a deprecation message.
-
-   We recommend :ref:`migrate-myrocks`. To enable the plugins to migrate to another storage engine, set the ``tokudb_enabled`` and ``tokudb_backup_enabled`` options to ``TRUE`` in your ``my.cnf`` file and restart your server instance. Then, you can load the plugins.
-
-   The TokuDB Storage Engine was `declared as deprecated <https://www.percona.com/doc/percona-server/8.0/release-notes/Percona-Server-8.0.13-3.html>`__ in Percona Server for MySQL 8.0. For more information, see the Percona blog post: `Heads-Up: TokuDB Support Changes and Future Removal from Percona Server for MySQL 8.0 <https://www.percona.com/blog/2021/05/21/tokudb-support-changes-and-future-removal-from-percona-server-for-mysql-8-0/>`__.
-
-*TokuDB* is integrated with `Performance Schema
-<https://dev.mysql.com/doc/refman/8.0/en/innodb-performance-schema.html>`_
-
-This integration can be used for profiling additional *TokuDB* operations.
-
-*TokuDB* instruments available in Performance Schema can be seen in
-:ref:`PERFORMANCE_SCHEMA.SETUP_INSTRUMENTS` table:
-
-.. code-block:: mysql
-
-  mysql> SELECT * FROM performance_schema.setup_instruments WHERE NAME LIKE "%/fti/%";
-  +------------------------------------------------------------+---------+-------+
-  | NAME                                                       | ENABLED | TIMED |
-  +------------------------------------------------------------+---------+-------+
-  | wait/synch/mutex/fti/kibbutz_mutex                         | NO      | NO    |
-  | wait/synch/mutex/fti/minicron_p_mutex                      | NO      | NO    |
-  | wait/synch/mutex/fti/queue_result_mutex                    | NO      | NO    |
-  | wait/synch/mutex/fti/tpool_lock_mutex                      | NO      | NO    |
-  | wait/synch/mutex/fti/workset_lock_mutex                    | NO      | NO    |
-  | wait/synch/mutex/fti/bjm_jobs_lock_mutex                   | NO      | NO    |
-  | wait/synch/mutex/fti/log_internal_lock_mutex               | NO      | NO    |
-  | wait/synch/mutex/fti/cachetable_ev_thread_lock_mutex       | NO      | NO    |
-  | wait/synch/mutex/fti/cachetable_disk_nb_mutex              | NO      | NO    |
-  | wait/synch/mutex/fti/safe_file_size_lock_mutex             | NO      | NO    |
-  | wait/synch/mutex/fti/cachetable_m_mutex_key                | NO      | NO    |
-  | wait/synch/mutex/fti/checkpoint_safe_mutex                 | NO      | NO    |
-  | wait/synch/mutex/fti/ft_ref_lock_mutex                     | NO      | NO    |
-  | wait/synch/mutex/fti/ft_open_close_lock_mutex              | NO      | NO    |
-  | wait/synch/mutex/fti/loader_error_mutex                    | NO      | NO    |
-  | wait/synch/mutex/fti/bfs_mutex                             | NO      | NO    |
-  | wait/synch/mutex/fti/loader_bl_mutex                       | NO      | NO    |
-  | wait/synch/mutex/fti/loader_fi_lock_mutex                  | NO      | NO    |
-  | wait/synch/mutex/fti/loader_out_mutex                      | NO      | NO    |
-  | wait/synch/mutex/fti/result_output_condition_lock_mutex    | NO      | NO    |
-  | wait/synch/mutex/fti/block_table_mutex                     | NO      | NO    |
-  | wait/synch/mutex/fti/rollback_log_node_cache_mutex         | NO      | NO    |
-  | wait/synch/mutex/fti/txn_lock_mutex                        | NO      | NO    |
-  | wait/synch/mutex/fti/txn_state_lock_mutex                  | NO      | NO    |
-  | wait/synch/mutex/fti/txn_child_manager_mutex               | NO      | NO    |
-  | wait/synch/mutex/fti/txn_manager_lock_mutex                | NO      | NO    |
-  | wait/synch/mutex/fti/treenode_mutex                        | NO      | NO    |
-  | wait/synch/mutex/fti/locktree_request_info_mutex           | NO      | NO    |
-  | wait/synch/mutex/fti/locktree_request_info_retry_mutex_key | NO      | NO    |
-  | wait/synch/mutex/fti/manager_mutex                         | NO      | NO    |
-  | wait/synch/mutex/fti/manager_escalation_mutex              | NO      | NO    |
-  | wait/synch/mutex/fti/db_txn_struct_i_txn_mutex             | NO      | NO    |
-  | wait/synch/mutex/fti/manager_escalator_mutex               | NO      | NO    |
-  | wait/synch/mutex/fti/indexer_i_indexer_lock_mutex          | NO      | NO    |
-  | wait/synch/mutex/fti/indexer_i_indexer_estimate_lock_mutex | NO      | NO    |
-  | wait/synch/mutex/fti/fti_probe_1                           | NO      | NO    |
-  | wait/synch/rwlock/fti/multi_operation_lock                 | NO      | NO    |
-  | wait/synch/rwlock/fti/low_priority_multi_operation_lock    | NO      | NO    |
-  | wait/synch/rwlock/fti/cachetable_m_list_lock               | NO      | NO    |
-  | wait/synch/rwlock/fti/cachetable_m_pending_lock_expensive  | NO      | NO    |
-  | wait/synch/rwlock/fti/cachetable_m_pending_lock_cheap      | NO      | NO    |
-  | wait/synch/rwlock/fti/cachetable_m_lock                    | NO      | NO    |
-  | wait/synch/rwlock/fti/result_i_open_dbs_rwlock             | NO      | NO    |
-  | wait/synch/rwlock/fti/checkpoint_safe_rwlock               | NO      | NO    |
-  | wait/synch/rwlock/fti/cachetable_value                     | NO      | NO    |
-  | wait/synch/rwlock/fti/safe_file_size_lock_rwlock           | NO      | NO    |
-  | wait/synch/rwlock/fti/cachetable_disk_nb_rwlock            | NO      | NO    |
-  | wait/synch/cond/fti/result_state_cond                      | NO      | NO    |
-  | wait/synch/cond/fti/bjm_jobs_wait                          | NO      | NO    |
-  | wait/synch/cond/fti/cachetable_p_refcount_wait             | NO      | NO    |
-  | wait/synch/cond/fti/cachetable_m_flow_control_cond         | NO      | NO    |
-  | wait/synch/cond/fti/cachetable_m_ev_thread_cond            | NO      | NO    |
-  | wait/synch/cond/fti/bfs_cond                               | NO      | NO    |
-  | wait/synch/cond/fti/result_output_condition                | NO      | NO    |
-  | wait/synch/cond/fti/manager_m_escalator_done               | NO      | NO    |
-  | wait/synch/cond/fti/lock_request_m_wait_cond               | NO      | NO    |
-  | wait/synch/cond/fti/queue_result_cond                      | NO      | NO    |
-  | wait/synch/cond/fti/ws_worker_wait                         | NO      | NO    |
-  | wait/synch/cond/fti/rwlock_wait_read                       | NO      | NO    |
-  | wait/synch/cond/fti/rwlock_wait_write                      | NO      | NO    |
-  | wait/synch/cond/fti/rwlock_cond                            | NO      | NO    |
-  | wait/synch/cond/fti/tp_thread_wait                         | NO      | NO    |
-  | wait/synch/cond/fti/tp_pool_wait_free                      | NO      | NO    |
-  | wait/synch/cond/fti/frwlock_m_wait_read                    | NO      | NO    |
-  | wait/synch/cond/fti/kibbutz_k_cond                         | NO      | NO    |
-  | wait/synch/cond/fti/minicron_p_condvar                     | NO      | NO    |
-  | wait/synch/cond/fti/locktree_request_info_retry_cv_key     | NO      | NO    |
-  | wait/io/file/fti/tokudb_data_file                          | YES     | YES   |
-  | wait/io/file/fti/tokudb_load_file                          | YES     | YES   |
-  | wait/io/file/fti/tokudb_tmp_file                           | YES     | YES   |
-  | wait/io/file/fti/tokudb_log_file                           | YES     | YES   |
-  +------------------------------------------------------------+---------+-------+
-
-For *TokuDB*-related objects, following clauses can be used when querying
-Performance Schema tables:
-
- * ``WHERE EVENT_NAME LIKE '%fti%'`` or
- * ``WHERE NAME LIKE '%fti%'``
-
-For example, to get the information about *TokuDB* related events you can query
-:ref:`PERFORMANCE_SCHEMA.events_waits_summary_global_by_event_name` like:
-
-.. code-block:: mysql
-
-  mysql> SELECT * FROM performance_schema.events_waits_summary_global_by_event_name WHERE EVENT_NAME LIKE '%fti%';
-
-  +-----------------------------------------+------------+----------------+----------------+----------------+----------------+
-  | EVENT_NAME                              | COUNT_STAR | SUM_TIMER_WAIT | MIN_TIMER_WAIT | AVG_TIMER_WAIT | MAX_TIMER_WAIT |
-  +-----------------------------------------+------------+----------------+----------------+----------------+----------------+
-  | wait/synch/mutex/fti/kibbutz_mutex      |          0 |              0 |              0 |              0 |              0 |
-  | wait/synch/mutex/fti/minicron_p_mutex   |          0 |              0 |              0 |              0 |              0 |
-  | wait/synch/mutex/fti/queue_result_mutex |          0 |              0 |              0 |              0 |              0 |
-  | wait/synch/mutex/fti/tpool_lock_mutex   |          0 |              0 |              0 |              0 |              0 |
-  | wait/synch/mutex/fti/workset_lock_mutex |          0 |              0 |              0 |              0 |              0 |
-  ...
-  | wait/io/file/fti/tokudb_data_file       |         30 |      179862410 |              0 |        5995080 |       68488420 |
-  | wait/io/file/fti/tokudb_load_file       |          0 |              0 |              0 |              0 |              0 |
-  | wait/io/file/fti/tokudb_tmp_file        |          0 |              0 |              0 |              0 |              0 |
-  | wait/io/file/fti/tokudb_log_file        |       1367 |  2925647870145 |              0 |     2140195785 |    12013357720 |
-  +-----------------------------------------+------------+----------------+----------------+----------------+----------------+
-  71 rows in set (0.02 sec)
diff --git a/doc/source/tokudb/tokudb_quickstart.rst b/doc/source/tokudb/tokudb_quickstart.rst
deleted file mode 100644
index dbdda52e4204..000000000000
--- a/doc/source/tokudb/tokudb_quickstart.rst
+++ /dev/null
@@ -1,248 +0,0 @@
-.. _tokudb_quickstart:
-
-================================================================================
-Getting Started with TokuDB
-================================================================================
-
-.. Important:: 
-
-   Starting with :ref:`8.0.28-19`, the TokuDB storage engine is no longer supported. We have removed the storage engine from the installation packages and disabled the storage engine in our binary builds.
-
-   Starting with :ref:`8.0.26-16`, the binary builds and packages include but disable the TokuDB storage engine plugins. The ``tokudb_enabled`` option and the ``tokudb_backup_enabled`` option control the state of the plugins and have a default setting of ``FALSE``. The result of attempting to load the plugins are the plugins fail to initialize and print a deprecation message.
-
-   We recommend :ref:`migrate-myrocks`. To enable the plugins to migrate to another storage engine, set the ``tokudb_enabled`` and ``tokudb_backup_enabled`` options to ``TRUE`` in your ``my.cnf`` file and restart your server instance. Then, you can load the plugins.
-
-   The TokuDB Storage Engine was `declared as deprecated <https://www.percona.com/doc/percona-server/8.0/release-notes/Percona-Server-8.0.13-3.html>`__ in Percona Server for MySQL 8.0. For more information, see the Percona blog post: `Heads-Up: TokuDB Support Changes and Future Removal from Percona Server for MySQL 8.0 <https://www.percona.com/blog/2021/05/21/tokudb-support-changes-and-future-removal-from-percona-server-for-mysql-8-0/>`__.
-
-:Operating Systems: *TokuDB* is currently supported on 64-bit Linux only.
-:Memory: *TokuDB* requires at least 1GB of main memory.
-
-	 For the best results, run with at least 2GB of main memory.
-:Disk space and configuration:
-   Make sure to allocate enough disk space for data, indexes and logs.
-
-   | Due to high compression, *TokuDB* may achieve up to 25x space savings on data
-   | and indexes over *InnoDB*.
-
-Creating Tables and Loading Data 
-================================================================================
-
-*TokuDB* tables are created the same way as other tables in *MySQL* by
-specifying :mysql:`ENGINE=TokuDB` in the table definition. For example, the
-following command creates a table with a single column and uses the *TokuDB*
-storage engine to store its data:
-
-.. code-block:: mysql
-
-   CREATE TABLE table (
-   id INT(11) NOT NULL) ENGINE=TokuDB;
-
-.. rubric:: Loading data
-	    
-Once *TokuDB* tables have been created, data can be inserted or loaded using
-standard *MySQL* insert or bulk load operations. For example, the following
-command loads data from a file into the table:
-
-.. code-block:: sql
-
-   LOAD DATA INFILE file
-   INTO TABLE table;
-
-.. note:: 
-
-   For more information about loading data, see the MySQL 8.0 reference
-   manual.
-
-Migrating Data from an Existing Database
-================================================================================
-
-Use the following command to convert an existing table for the *TokuDB* storage
-engine:
-
-.. code-block:: mysql
-
-   ALTER TABLE table
-   ENGINE=TokuDB;
-
-.. rubric:: Bulk Loading Data
-
-The *TokuDB* bulk loader imports data much faster than regular *MySQL* with
-*InnoDB*. To make use of the loader you need flat files in either comma
-separated or tab separated format. The *MySQL* :mysql:`LOAD DATA INFILE`
-statement will invoke the bulk loader if the table is empty. Keep in mind that
-while this is the most convenient and, in most cases, the fastest way to
-initialize a *TokuDB* table, it may not be replication safe if applied to the
-source.
-
-.. seealso::
-
-   MySQL Documentation: :mysql:`LOAD DATA INFILE`
-      http://dev.mysql.com/doc/refman/8.0/en/load-data.html
-
-To obtain the logical backup and then bulk load into *TokuDB*, follow these
-steps:
-
-1. *Create a logical backup of the original table.* The easiest way to achieve
-   this is using :mysql:`SELECT ... INTO OUTFILE`. Keep in mind that the file will be
-   created on the server:  :mysql:`SELECT * FROM table INTO OUTFILE 'file.csv';`
-
-#. *Copy the output file* either to the destination server or the client machine
-   from which you plan to load it.
-
-#. *Load the data into the server* using :mysql:`LOAD DATA INFILE`. If loading from
-   a machine other than the server use the keyword ``LOCAL`` to point to the
-   file on local machine. Keep in mind that you will need enough disk space on
-   the temporary directory on the server since the local file will be copied
-   onto the server by the *MySQL* client utility:
-   :mysql:`LOAD DATA [LOCAL] INFILE 'file.csv';`
-
-It is possible to create the CSV file using either :program:`mysqldump` or the
-*MySQL* client utility as well, in which case the resulting file will reside on
-a local directory. In these 2 cases you have to make sure to use the correct
-command line options to create a file compatible with :mysql:`LOAD DATA INFILE`.
-
-The bulk loader will use more space than normal for logs and temporary files
-while running, make sure that your file system has enough disk space to process
-your load. As a rule of thumb, it should be approximately 1.5 times the size of
-the raw data.
-
-.. note::
-
-   Please read the original MySQL Documentation to understand the needed privileges and
-   replication issues around :mysql:`LOAD DATA INFILE`.
-
-Considerations to Run TokuDB in Production
-================================================================================
-
-In most cases, the default options should be left in-place to run *TokuDB*,
-however it is a good idea to review some of the configuration parameters.
-
-.. rubric:: Memory allocation
-
-*TokuDB* will allocate 50% of the installed RAM for its own cache (global
-variable :ref:`tokudb_cache_size`). While this is optimal in most
-situations, there are cases where it may lead to memory over allocation. If the
-system tries to allocate more memory than is available, the machine will begin
-swapping and run much slower than normal.
-
-It is necessary to set the :ref:`tokudb_cache_size` to a value other than
-the default in the following cases:
-
-Running other memory heavy processes on the same server as TokuDB
-   In many cases, the database process needs to share the system with other
-   server processes like additional database instances, http server, application
-   server, e-mail server, monitoring systems and others. In order to properly
-   configure TokuDB's memory consumption, it's important to understand how much
-   free memory will be left and assign a sensible value for *TokuDB*. There is
-   no fixed rule, but a conservative choice would be 50% of available RAM while
-   all the other processes are running. If the result is under 2 GB, you should
-   consider moving some of the other processes to a different system or using a
-   dedicated database server.
-
-   :ref:`tokudb_cache_size` is a static variable, so it needs to be set
-   before starting the server and cannot be changed while the server is
-   running. For example, to set up TokuDB's cache to 4G, add the following line
-   to your :file:`my.cnf` file:
-
-   .. code-block:: bash
-
-      tokudb_cache_size = 4G
-
-System using *InnoDB* and *TokuDB*
-   When using both the *TokuDB* and *InnoDB* storage engines, you need to manage
-   the cache size for each. For example, on a server with 16 GB of RAM you could
-   use the following values in your configuration file:
- 
-   .. code-block:: bash
-
-      innodb_buffer_pool_size = 2G
-      tokudb_cache_size = 8G
-
-Using *TokuDB* with Federated or FederatedX tables
-   The Federated engine in *MySQL* and FederatedX in *MariaDB* allow you to
-   connect to a table on a remote server and query it as if it were a local
-   table (please see the MySQL Documentation: 14.11. The FEDERATED Storage
-   Engine for details). When accessing the remote table, these engines could
-   import the complete table contents to the local server to execute a query. In
-   this case, you will have to make sure that there is enough free memory on the
-   server to handle these remote tables. For example, if your remote table is 8
-   GB in size, the server has to have more than 8 GB of free RAM to process
-   queries against that table without going into swapping or causing a kernel
-   panic and crash the *MySQL* process. There are no parameters to limit the
-   amount of memory that the Federated or FederatedX engine will allocate while
-   importing the remote dataset.
-
-Specifying the Location for Files
-================================================================================
-
-As with *InnoDB*, it is possible to specify different locations than the default
-for TokuDB's data, log and temporary files. This way you may distribute the load
-and control the disk space. The following variables control file location:
-
-* :ref:`tokudb_data_dir`: This variable defines the directory where the TokuDB tables are stored. The default location for TokuDB's data files is the MySQL data directory.
-
-* :ref:`tokudb_log_dir`: This variable defines the directory where the TokuDB log files are stored. The default location for TokuDB's log files is the MySQL data directory. Configuring a separate log directory is somewhat involved and should be done only if absolutely necessary. We recommend to keep the data and log files under the same directory.
-
-* :ref:`tokudb_tmp_dir`: This variable defines the directory where the TokuDB bulk loader stores temporary files. The bulk loader can create large temporary files while it is loading a table, so putting these temporary files on a disk separate from the data directory can be useful. For example, it can make sense to use a high-performance disk for the data directory and a very inexpensive disk for the temporary directory. The default location for TokuDB's temporary files is the MySQL data directory.
-
-Table Maintenance
-================================================================================
-
-The fractal tree provides fast performance by inserting small messages in the
-buffers in the fractal trees instead of requiring a potential IO for an update
-on every row in the table as required by a B-tree. Additional background
-information on how fractal trees operate can be found here. For tables whose
-workload pattern is a high number of sequential deletes, it may be beneficial to
-flush these delete messages down to the basement nodes in order to allow for
-faster access. The way to perform this operation is via the ``OPTIMIZE``
-command.
-
-The following extensions to the ``OPTIMIZE`` command have been added in *TokuDB*
-version 7.5.5:
-
-.. contents::
-   :local:
-
-Hot Optimize Throttling
---------------------------------------------------------------------------------
-
-By default, table optimization will run with all available resources. To limit
-the amount of resources, it is possible to limit the speed of table
-optimization.  The :ref:`tokudb_optimize_throttle` session variable
-determines an upper bound on how many fractal tree leaf nodes per second are
-optimized.  The default is 0 (no upper bound) with a valid range of
-[0,1000000]. For example, to limit the table optimization to 1 leaf node per
-second, use the following setting: :mysql:`SET tokudb_optimize_throttle=1;`
-
-Optimize a Single Index of a Table
---------------------------------------------------------------------------------
-
-To optimize a single index in a table, the
-:ref:`tokudb_optimize_index_name` session variable can be set to select the
-index by name. For example, to optimize the primary key of a table:
-
-.. code-block:: mysql
-
-   SET tokudb_optimize_index_name='primary'; 
-   OPTIMIZE TABLE t;
-
-Optimize a Subset of a Fractal Tree Index
---------------------------------------------------------------------------------
-
-For patterns where the left side of the tree has many deletions (a common
-pattern with increasing id or date values), it may be useful to delete a
-percentage of the tree. In this case, it is possible to optimize a subset of a
-fractal tree starting at the left side. The
-:ref:`tokudb_optimize_index_fraction` session variable controls the size of
-the sub tree. Valid values are in the range [0.0,1.0] with default 1.0 (optimize
-the whole tree). For example, to optimize the leftmost 10% of the primary key:
-
-.. code-block:: mysql
-
-   SET tokudb_optimize_index_name='primary'; 
-   SET tokudb_optimize_index_fraction=0.1;
-   OPTIMIZE TABLE t;
-
-.. include:: ../.res/replace.txt
-.. include:: ../.res/replace.program.txt
-.. include:: ../.res/replace.concept.txt
diff --git a/doc/source/tokudb/tokudb_status_variables.rst b/doc/source/tokudb/tokudb_status_variables.rst
deleted file mode 100644
index 45ad197077b4..000000000000
--- a/doc/source/tokudb/tokudb_status_variables.rst
+++ /dev/null
@@ -1,2440 +0,0 @@
-.. _tokudb_status_variables:
-
-=======================
-TokuDB Status Variables
-=======================
-
-.. Important:: 
-
-   Starting with :ref:`8.0.28-19`, the TokuDB storage engine is no longer supported. We have removed the storage engine from the installation packages and disabled the storage engine in our binary builds.
-
-   Starting with :ref:`8.0.26-16`, the binary builds and packages include but disable the TokuDB storage engine plugins. The ``tokudb_enabled`` option and the ``tokudb_backup_enabled`` option control the state of the plugins and have a default setting of ``FALSE``. The result of attempting to load the plugins are the plugins fail to initialize and print a deprecation message.
-
-   We recommend :ref:`migrate-myrocks`. To enable the plugins to migrate to another storage engine, set the ``tokudb_enabled`` and ``tokudb_backup_enabled`` options to ``TRUE`` in your ``my.cnf`` file and restart your server instance. Then, you can load the plugins.
-
-   The TokuDB Storage Engine was `declared as deprecated <https://www.percona.com/doc/percona-server/8.0/release-notes/Percona-Server-8.0.13-3.html>`__ in Percona Server for MySQL 8.0. For more information, see the Percona blog post: `Heads-Up: TokuDB Support Changes and Future Removal from Percona Server for MySQL 8.0 <https://www.percona.com/blog/2021/05/21/tokudb-support-changes-and-future-removal-from-percona-server-for-mysql-8-0/>`__.
-
-*TokuDB* status variables provide details about the inner workings of *TokuDB*
-storage engine and they can be useful in tuning the storage engine to a
-particular environment. 
-
-You can view these variables and their values by running:
-
-.. code-block:: mysql
-
-  mysql> SHOW STATUS LIKE 'tokudb%';
-
-TokuDB Status Variables Summary
--------------------------------
-
-The following global status variables are available:
-
-.. tabularcolumns:: |p{9cm}|p{6cm}|
-
-.. list-table::
-   :header-rows: 1
-
-   * - Name
-     - Var Type
-   * - :ref:`Tokudb_DB_OPENS`
-     - integer 
-   * - :ref:`Tokudb_DB_CLOSES`
-     - integer
-   * - :ref:`Tokudb_DB_OPEN_CURRENT`
-     - integer
-   * - :ref:`Tokudb_DB_OPEN_MAX`
-     - integer
-   * - :ref:`Tokudb_LEAF_ENTRY_MAX_COMMITTED_XR`
-     - integer
-   * - :ref:`Tokudb_LEAF_ENTRY_MAX_PROVISIONAL_XR`
-     - integer
-   * - :ref:`Tokudb_LEAF_ENTRY_EXPANDED`
-     - integer
-   * - :ref:`Tokudb_LEAF_ENTRY_MAX_MEMSIZE`
-     - integer
-   * - :ref:`Tokudb_LEAF_ENTRY_APPLY_GC_BYTES_IN`
-     - integer
-   * - :ref:`Tokudb_LEAF_ENTRY_APPLY_GC_BYTES_OUT`
-     - integer
-   * - :ref:`Tokudb_LEAF_ENTRY_NORMAL_GC_BYTES_IN`
-     - integer
-   * - :ref:`Tokudb_LEAF_ENTRY_NORMAL_GC_BYTES_OUT`
-     - integer
-   * - :ref:`Tokudb_CHECKPOINT_PERIOD`
-     - integer
-   * - :ref:`Tokudb_CHECKPOINT_FOOTPRINT`
-     - integer
-   * - :ref:`Tokudb_CHECKPOINT_LAST_BEGAN`
-     - datetime
-   * - :ref:`Tokudb_CHECKPOINT_LAST_COMPLETE_BEGAN`
-     - datetime
-   * - :ref:`Tokudb_CHECKPOINT_LAST_COMPLETE_ENDED`
-     - datetime
-   * - :ref:`Tokudb_CHECKPOINT_DURATION`
-     - integer
-   * - :ref:`Tokudb_CHECKPOINT_DURATION_LAST`
-     - integer
-   * - :ref:`Tokudb_CHECKPOINT_LAST_LSN`
-     - integer
-   * - :ref:`Tokudb_CHECKPOINT_TAKEN`
-     - integer
-   * - :ref:`Tokudb_CHECKPOINT_FAILED`
-     - integer
-   * - :ref:`Tokudb_CHECKPOINT_WAITERS_NOW`
-     - integer
-   * - :ref:`Tokudb_CHECKPOINT_WAITERS_MAX`
-     - integer
-   * - :ref:`Tokudb_CHECKPOINT_CLIENT_WAIT_ON_MO`
-     - integer
-   * - :ref:`Tokudb_CHECKPOINT_CLIENT_WAIT_ON_CS`
-     - integer
-   * - :ref:`Tokudb_CHECKPOINT_BEGIN_TIME`
-     - integer
-   * - :ref:`Tokudb_CHECKPOINT_LONG_BEGIN_TIME`
-     - integer
-   * - :ref:`Tokudb_CHECKPOINT_LONG_BEGIN_COUNT`
-     - integer
-   * - :ref:`Tokudb_CHECKPOINT_END_TIME`
-     - integer
-   * - :ref:`Tokudb_CHECKPOINT_LONG_END_TIME`
-     - integer
-   * - :ref:`Tokudb_CHECKPOINT_LONG_END_COUNT`
-     - integer
-   * - :ref:`Tokudb_CACHETABLE_MISS`
-     - integer
-   * - :ref:`Tokudb_CACHETABLE_MISS_TIME`
-     - integer
-   * - :ref:`Tokudb_CACHETABLE_PREFETCHES`
-     - integer
-   * - :ref:`Tokudb_CACHETABLE_SIZE_CURRENT`
-     - integer
-   * - :ref:`Tokudb_CACHETABLE_SIZE_LIMIT`
-     - integer
-   * - :ref:`Tokudb_CACHETABLE_SIZE_WRITING`
-     - integer
-   * - :ref:`Tokudb_CACHETABLE_SIZE_NONLEAF`
-     - integer
-   * - :ref:`Tokudb_CACHETABLE_SIZE_LEAF`
-     - integer
-   * - :ref:`Tokudb_CACHETABLE_SIZE_ROLLBACK`
-     - integer
-   * - :ref:`Tokudb_CACHETABLE_SIZE_CACHEPRESSURE`
-     - integer
-   * - :ref:`Tokudb_CACHETABLE_SIZE_CLONED`
-     - integer
-   * - :ref:`Tokudb_CACHETABLE_EVICTIONS`
-     - integer
-   * - :ref:`Tokudb_CACHETABLE_CLEANER_EXECUTIONS`
-     - integer
-   * - :ref:`Tokudb_CACHETABLE_CLEANER_PERIOD`
-     - integer
-   * - :ref:`Tokudb_CACHETABLE_CLEANER_ITERATIONS`
-     - integer
-   * - :ref:`Tokudb_CACHETABLE_WAIT_PRESSURE_COUNT`
-     - integer
-   * - :ref:`Tokudb_CACHETABLE_WAIT_PRESSURE_TIME`
-     - integer
-   * - :ref:`Tokudb_CACHETABLE_LONG_WAIT_PRESSURE_COUNT`
-     - integer
-   * - :ref:`Tokudb_CACHETABLE_LONG_WAIT_PRESSURE_TIME`
-     - integer
-   * - :ref:`Tokudb_CACHETABLE_POOL_CLIENT_NUM_THREADS`
-     - integer
-   * - :ref:`Tokudb_CACHETABLE_POOL_CLIENT_NUM_THREADS_ACTIVE`
-     - integer
-   * - :ref:`Tokudb_CACHETABLE_POOL_CLIENT_QUEUE_SIZE`
-     - integer
-   * - :ref:`Tokudb_CACHETABLE_POOL_CLIENT_MAX_QUEUE_SIZE`
-     - integer
-   * - :ref:`Tokudb_CACHETABLE_POOL_CLIENT_TOTAL_ITEMS_PROCESSED`
-     - integer
-   * - :ref:`Tokudb_CACHETABLE_POOL_CLIENT_TOTAL_EXECUTION_TIME`
-     - integer
-   * - :ref:`Tokudb_CACHETABLE_POOL_CACHETABLE_NUM_THREADS`
-     - integer
-   * - :ref:`Tokudb_CACHETABLE_POOL_CACHETABLE_NUM_THREADS_ACTIVE`
-     - integer
-   * - :ref:`Tokudb_CACHETABLE_POOL_CACHETABLE_QUEUE_SIZE`
-     - integer
-   * - :ref:`Tokudb_CACHETABLE_POOL_CACHETABLE_MAX_QUEUE_SIZE`
-     - integer
-   * - :ref:`Tokudb_CACHETABLE_POOL_CACHETABLE_TOTAL_ITEMS_PROCESSED`
-     - integer
-   * - :ref:`Tokudb_CACHETABLE_POOL_CACHETABLE_TOTAL_EXECUTION_TIME`
-     - integer
-   * - :ref:`Tokudb_CACHETABLE_POOL_CHECKPOINT_NUM_THREADS`
-     - integer
-   * - :ref:`Tokudb_CACHETABLE_POOL_CHECKPOINT_NUM_THREADS_ACTIVE`
-     - integer
-   * - :ref:`Tokudb_CACHETABLE_POOL_CHECKPOINT_QUEUE_SIZE`
-     - integer
-   * - :ref:`Tokudb_CACHETABLE_POOL_CHECKPOINT_MAX_QUEUE_SIZE`
-     - integer
-   * - :ref:`Tokudb_CACHETABLE_POOL_CHECKPOINT_TOTAL_ITEMS_PROCESSED`
-     - integer
-   * - :ref:`Tokudb_CACHETABLE_POOL_CHECKPOINT_TOTAL_EXECUTION_TIME`
-     - integer
-   * - :ref:`Tokudb_LOCKTREE_MEMORY_SIZE`
-     - integer
-   * - :ref:`Tokudb_LOCKTREE_MEMORY_SIZE_LIMIT`
-     - integer
-   * - :ref:`Tokudb_LOCKTREE_ESCALATION_NUM`
-     - integer
-   * - :ref:`Tokudb_LOCKTREE_ESCALATION_SECONDS`
-     - numeric
-   * - :ref:`Tokudb_LOCKTREE_LATEST_POST_ESCALATION_MEMORY_SIZE`
-     - integer
-   * - :ref:`Tokudb_LOCKTREE_OPEN_CURRENT`
-     - integer
-   * - :ref:`Tokudb_LOCKTREE_PENDING_LOCK_REQUESTS`
-     - integer
-   * - :ref:`Tokudb_LOCKTREE_STO_ELIGIBLE_NUM`
-     - integer
-   * - :ref:`Tokudb_LOCKTREE_STO_ENDED_NUM`
-     - integer
-   * - :ref:`Tokudb_LOCKTREE_STO_ENDED_SECONDS`
-     - numeric
-   * - :ref:`Tokudb_LOCKTREE_WAIT_COUNT`
-     - integer
-   * - :ref:`Tokudb_LOCKTREE_WAIT_TIME`
-     - integer
-   * - :ref:`Tokudb_LOCKTREE_LONG_WAIT_COUNT`
-     - integer
-   * - :ref:`Tokudb_LOCKTREE_LONG_WAIT_TIME`
-     - integer
-   * - :ref:`Tokudb_LOCKTREE_TIMEOUT_COUNT`
-     - integer
-   * - :ref:`Tokudb_LOCKTREE_WAIT_ESCALATION_COUNT`
-     - integer
-   * - :ref:`Tokudb_LOCKTREE_WAIT_ESCALATION_TIME`
-     - integer
-   * - :ref:`Tokudb_LOCKTREE_LONG_WAIT_ESCALATION_COUNT`
-     - integer
-   * - :ref:`Tokudb_LOCKTREE_LONG_WAIT_ESCALATION_TIME`
-     - integer
-   * - :ref:`Tokudb_DICTIONARY_UPDATES`
-     - integer
-   * - :ref:`Tokudb_DICTIONARY_BROADCAST_UPDATES`
-     - integer
-   * - :ref:`Tokudb_DESCRIPTOR_SET`
-     - integer
-   * - :ref:`Tokudb_MESSAGES_IGNORED_BY_LEAF_DUE_TO_MSN`
-     - integer
-   * - :ref:`Tokudb_TOTAL_SEARCH_RETRIES`
-     - integer
-   * - :ref:`Tokudb_SEARCH_TRIES_GT_HEIGHT`
-     - integer
-   * - :ref:`Tokudb_SEARCH_TRIES_GT_HEIGHTPLUS3`
-     - integer
-   * - :ref:`Tokudb_LEAF_NODES_FLUSHED_NOT_CHECKPOINT`
-     - integer
-   * - :ref:`Tokudb_LEAF_NODES_FLUSHED_NOT_CHECKPOINT_BYTES`
-     - integer
-   * - :ref:`Tokudb_LEAF_NODES_FLUSHED_NOT_CHECKPOINT_UNCOMPRESSED_BYTES`
-     - integer
-   * - :ref:`Tokudb_LEAF_NODES_FLUSHED_NOT_CHECKPOINT_SECONDS`
-     - numeric
-   * - :ref:`Tokudb_NONLEAF_NODES_FLUSHED_TO_DISK_NOT_CHECKPOINT`
-     - integer
-   * - :ref:`Tokudb_NONLEAF_NODES_FLUSHED_TO_DISK_NOT_CHECKPOINT_BYTES`
-     - integer
-   * - :ref:`Tokudb_NONLEAF_NODES_FLUSHED_TO_DISK_NOT_CHECKPOINT_UNCOMPRESSE`
-     - integer
-   * - :ref:`Tokudb_NONLEAF_NODES_FLUSHED_TO_DISK_NOT_CHECKPOINT_SECONDS`
-     - numeric
-   * - :ref:`Tokudb_LEAF_NODES_FLUSHED_CHECKPOINT`
-     - integer
-   * - :ref:`Tokudb_LEAF_NODES_FLUSHED_CHECKPOINT_BYTES`
-     - integer
-   * - :ref:`Tokudb_LEAF_NODES_FLUSHED_CHECKPOINT_UNCOMPRESSED_BYTES`
-     - integer
-   * - :ref:`Tokudb_LEAF_NODES_FLUSHED_CHECKPOINT_SECONDS`
-     - numeric
-   * - :ref:`Tokudb_NONLEAF_NODES_FLUSHED_TO_DISK_CHECKPOINT`
-     - integer
-   * - :ref:`Tokudb_NONLEAF_NODES_FLUSHED_TO_DISK_CHECKPOINT_BYTES`
-     - integer
-   * - :ref:`Tokudb_NONLEAF_NODES_FLUSHED_TO_DISK_CHECKPOINT_UNCOMPRESSED_BY`
-     - integer
-   * - :ref:`Tokudb_NONLEAF_NODES_FLUSHED_TO_DISK_CHECKPOINT_SECONDS`
-     - numeric
-   * - :ref:`Tokudb_LEAF_NODE_COMPRESSION_RATIO`
-     - numeric
-   * - :ref:`Tokudb_NONLEAF_NODE_COMPRESSION_RATIO`
-     - numeric
-   * - :ref:`Tokudb_OVERALL_NODE_COMPRESSION_RATIO`
-     - numeric
-   * - :ref:`Tokudb_NONLEAF_NODE_PARTIAL_EVICTIONS`
-     - numeric
-   * - :ref:`Tokudb_NONLEAF_NODE_PARTIAL_EVICTIONS_BYTES`
-     - integer
-   * - :ref:`Tokudb_LEAF_NODE_PARTIAL_EVICTIONS`
-     - integer
-   * - :ref:`Tokudb_LEAF_NODE_PARTIAL_EVICTIONS_BYTES`
-     - integer
-   * - :ref:`Tokudb_LEAF_NODE_FULL_EVICTIONS`
-     - integer
-   * - :ref:`Tokudb_LEAF_NODE_FULL_EVICTIONS_BYTES`
-     - integer
-   * - :ref:`Tokudb_NONLEAF_NODE_FULL_EVICTIONS`
-     - integer
-   * - :ref:`Tokudb_NONLEAF_NODE_FULL_EVICTIONS_BYTES`
-     - integer
-   * - :ref:`Tokudb_LEAF_NODES_CREATED`
-     - integer
-   * - :ref:`Tokudb_NONLEAF_NODES_CREATED`
-     - integer
-   * - :ref:`Tokudb_LEAF_NODES_DESTROYED`
-     - integer
-   * - :ref:`Tokudb_NONLEAF_NODES_DESTROYED`
-     - integer
-   * - :ref:`Tokudb_MESSAGES_INJECTED_AT_ROOT_BYTES`
-     - integer
-   * - :ref:`Tokudb_MESSAGES_FLUSHED_FROM_H1_TO_LEAVES_BYTES`
-     - integer
-   * - :ref:`Tokudb_MESSAGES_IN_TREES_ESTIMATE_BYTES`
-     - integer
-   * - :ref:`Tokudb_MESSAGES_INJECTED_AT_ROOT`
-     - integer
-   * - :ref:`Tokudb_BROADCASE_MESSAGES_INJECTED_AT_ROOT`
-     - integer
-   * - :ref:`Tokudb_BASEMENTS_DECOMPRESSED_TARGET_QUERY`
-     - integer
-   * - :ref:`Tokudb_BASEMENTS_DECOMPRESSED_PRELOCKED_RANGE`
-     - integer
-   * - :ref:`Tokudb_BASEMENTS_DECOMPRESSED_PREFETCH`
-     - integer
-   * - :ref:`Tokudb_BASEMENTS_DECOMPRESSED_FOR_WRITE`
-     - integer
-   * - :ref:`Tokudb_BUFFERS_DECOMPRESSED_TARGET_QUERY`
-     - integer
-   * - :ref:`Tokudb_BUFFERS_DECOMPRESSED_PRELOCKED_RANGE`
-     - integer
-   * - :ref:`Tokudb_BUFFERS_DECOMPRESSED_PREFETCH`
-     - integer
-   * - :ref:`Tokudb_BUFFERS_DECOMPRESSED_FOR_WRITE`
-     - integer
-   * - :ref:`Tokudb_PIVOTS_FETCHED_FOR_QUERY`
-     - integer
-   * - :ref:`Tokudb_PIVOTS_FETCHED_FOR_QUERY_BYTES`
-     - integer
-   * - :ref:`Tokudb_PIVOTS_FETCHED_FOR_QUERY_SECONDS`
-     - numeric
-   * - :ref:`Tokudb_PIVOTS_FETCHED_FOR_PREFETCH`
-     - integer
-   * - :ref:`Tokudb_PIVOTS_FETCHED_FOR_PREFETCH_BYTES`
-     - integer
-   * - :ref:`Tokudb_PIVOTS_FETCHED_FOR_PREFETCH_SECONDS`
-     - numeric
-   * - :ref:`Tokudb_PIVOTS_FETCHED_FOR_WRITE`
-     - integer
-   * - :ref:`Tokudb_PIVOTS_FETCHED_FOR_WRITE_BYTES`
-     - integer
-   * - :ref:`Tokudb_PIVOTS_FETCHED_FOR_WRITE_SECONDS`
-     - numeric
-   * - :ref:`Tokudb_BASEMENTS_FETCHED_TARGET_QUERY`
-     - integer
-   * - :ref:`Tokudb_BASEMENTS_FETCHED_TARGET_QUERY_BYTES`
-     - integer
-   * - :ref:`Tokudb_BASEMENTS_FETCHED_TARGET_QUERY_SECONDS`
-     - numeric
-   * - :ref:`Tokudb_BASEMENTS_FETCHED_PRELOCKED_RANGE`
-     - integer
-   * - :ref:`Tokudb_BASEMENTS_FETCHED_PRELOCKED_RANGE_BYTES`
-     - integer
-   * - :ref:`Tokudb_BASEMENTS_FETCHED_PRELOCKED_RANGE_SECONDS`
-     - numeric
-   * - :ref:`Tokudb_BASEMENTS_FETCHED_PREFETCH`
-     - integer
-   * - :ref:`Tokudb_BASEMENTS_FETCHED_PREFETCH_BYTES`
-     - integer
-   * - :ref:`Tokudb_BASEMENTS_FETCHED_PREFETCH_SECONDS`
-     - numeric
-   * - :ref:`Tokudb_BASEMENTS_FETCHED_FOR_WRITE`
-     - integer
-   * - :ref:`Tokudb_BASEMENTS_FETCHED_FOR_WRITE_BYTES`
-     - integer
-   * - :ref:`Tokudb_BASEMENTS_FETCHED_FOR_WRITE_SECONDS`
-     - numeric
-   * - :ref:`Tokudb_BUFFERS_FETCHED_TARGET_QUERY`
-     - integer
-   * - :ref:`Tokudb_BUFFERS_FETCHED_TARGET_QUERY_BYTES`
-     - integer
-   * - :ref:`Tokudb_BUFFERS_FETCHED_TARGET_QUERY_SECONDS`
-     - numeric
-   * - :ref:`Tokudb_BUFFERS_FETCHED_PRELOCKED_RANGE`
-     - integer
-   * - :ref:`Tokudb_BUFFERS_FETCHED_PRELOCKED_RANGE_BYTES`
-     - integer
-   * - :ref:`Tokudb_BUFFERS_FETCHED_PRELOCKED_RANGE_SECONDS`
-     - numeric
-   * - :ref:`Tokudb_BUFFERS_FETCHED_PREFETCH`
-     - integer
-   * - :ref:`Tokudb_BUFFERS_FETCHED_PREFETCH_BYTES`
-     - integer
-   * - :ref:`Tokudb_BUFFERS_FETCHED_PREFETCH_SECONDS`
-     - numeric
-   * - :ref:`Tokudb_BUFFERS_FETCHED_FOR_WRITE`
-     - integer
-   * - :ref:`Tokudb_BUFFERS_FETCHED_FOR_WRITE_BYTES`
-     - integer
-   * - :ref:`Tokudb_BUFFERS_FETCHED_FOR_WRITE_SECONDS`
-     - integer
-   * - :ref:`Tokudb_LEAF_COMPRESSION_TO_MEMORY_SECONDS`
-     - numeric
-   * - :ref:`Tokudb_LEAF_SERIALIZATION_TO_MEMORY_SECONDS`
-     - numeric
-   * - :ref:`Tokudb_LEAF_DECOMPRESSION_TO_MEMORY_SECONDS`
-     - numeric
-   * - :ref:`Tokudb_LEAF_DESERIALIZATION_TO_MEMORY_SECONDS`
-     - numeric
-   * - :ref:`Tokudb_NONLEAF_COMPRESSION_TO_MEMORY_SECONDS`
-     - numeric
-   * - :ref:`Tokudb_NONLEAF_SERIALIZATION_TO_MEMORY_SECONDS`
-     - numeric
-   * - :ref:`Tokudb_NONLEAF_DECOMPRESSION_TO_MEMORY_SECONDS`
-     - numeric
-   * - :ref:`Tokudb_NONLEAF_DESERIALIZATION_TO_MEMORY_SECONDS`
-     - numeric
-   * - :ref:`Tokudb_PROMOTION_ROOTS_SPLIT`
-     - integer
-   * - :ref:`Tokudb_PROMOTION_LEAF_ROOTS_INJECTED_INTO`
-     - integer
-   * - :ref:`Tokudb_PROMOTION_H1_ROOTS_INJECTED_INTO`
-     - integer
-   * - :ref:`Tokudb_PROMOTION_INJECTIONS_AT_DEPTH_0`
-     - integer
-   * - :ref:`Tokudb_PROMOTION_INJECTIONS_AT_DEPTH_1`
-     - integer
-   * - :ref:`Tokudb_PROMOTION_INJECTIONS_AT_DEPTH_2`
-     - integer
-   * - :ref:`Tokudb_PROMOTION_INJECTIONS_AT_DEPTH_3`
-     - integer
-   * - :ref:`Tokudb_PROMOTION_INJECTIONS_LOWER_THAN_DEPTH_3`
-     - integer
-   * - :ref:`Tokudb_PROMOTION_STOPPED_NONEMPTY_BUFFER`
-     - integer
-   * - :ref:`Tokudb_PROMOTION_STOPPED_AT_HEIGHT_1`
-     - integer
-   * - :ref:`Tokudb_PROMOTION_STOPPED_CHILD_LOCKED_OR_NOT_IN_MEMORY`
-     - integer
-   * - :ref:`Tokudb_PROMOTION_STOPPED_CHILD_NOT_FULLY_IN_MEMORY`
-     - integer
-   * - :ref:`Tokudb_PROMOTION_STOPPED_AFTER_LOCKING_CHILD`
-     - integer
-   * - :ref:`Tokudb_BASEMENT_DESERIALIZATION_FIXED_KEY`
-     - integer
-   * - :ref:`Tokudb_BASEMENT_DESERIALIZATION_VARIABLE_KEY`
-     - integer
-   * - :ref:`Tokudb_PRO_RIGHTMOST_LEAF_SHORTCUT_SUCCESS`
-     - integer
-   * - :ref:`Tokudb_PRO_RIGHTMOST_LEAF_SHORTCUT_FAIL_POS`
-     - integer
-   * - :ref:`Tokudb_RIGHTMOST_LEAF_SHORTCUT_FAIL_REACTIVE`
-     - integer
-   * - :ref:`Tokudb_CURSOR_SKIP_DELETED_LEAF_ENTRY`
-     - integer
-   * - :ref:`Tokudb_FLUSHER_CLEANER_TOTAL_NODES`
-     - integer
-   * - :ref:`Tokudb_FLUSHER_CLEANER_H1_NODES`
-     - integer
-   * - :ref:`Tokudb_FLUSHER_CLEANER_HGT1_NODES`
-     - integer
-   * - :ref:`Tokudb_FLUSHER_CLEANER_EMPTY_NODES`
-     - integer
-   * - :ref:`Tokudb_FLUSHER_CLEANER_NODES_DIRTIED`
-     - integer
-   * - :ref:`Tokudb_FLUSHER_CLEANER_MAX_BUFFER_SIZE`
-     - integer
-   * - :ref:`Tokudb_FLUSHER_CLEANER_MIN_BUFFER_SIZE`
-     - integer
-   * - :ref:`Tokudb_FLUSHER_CLEANER_TOTAL_BUFFER_SIZE`
-     - integer
-   * - :ref:`Tokudb_FLUSHER_CLEANER_MAX_BUFFER_WORKDONE`
-     - integer
-   * - :ref:`Tokudb_FLUSHER_CLEANER_MIN_BUFFER_WORKDONE`
-     - integer
-   * - :ref:`Tokudb_FLUSHER_CLEANER_TOTAL_BUFFER_WORKDONE`
-     - integer
-   * - :ref:`Tokudb_FLUSHER_CLEANER_NUM_LEAF_MERGES_STARTED`
-     - integer
-   * - :ref:`Tokudb_FLUSHER_CLEANER_NUM_LEAF_MERGES_RUNNING`
-     - integer
-   * - :ref:`Tokudb_FLUSHER_CLEANER_NUM_LEAF_MERGES_COMPLETED`
-     - integer
-   * - :ref:`Tokudb_FLUSHER_CLEANER_NUM_DIRTIED_FOR_LEAF_MERGE`
-     - integer
-   * - :ref:`Tokudb_FLUSHER_FLUSH_TOTAL`
-     - integer
-   * - :ref:`Tokudb_FLUSHER_FLUSH_IN_MEMORY`
-     - integer
-   * - :ref:`Tokudb_FLUSHER_FLUSH_NEEDED_IO`
-     - integer
-   * - :ref:`Tokudb_FLUSHER_FLUSH_CASCADES`
-     - integer
-   * - :ref:`Tokudb_FLUSHER_FLUSH_CASCADES_1`
-     - integer
-   * - :ref:`Tokudb_FLUSHER_FLUSH_CASCADES_2`
-     - integer
-   * - :ref:`Tokudb_FLUSHER_FLUSH_CASCADES_3`
-     - integer
-   * - :ref:`Tokudb_FLUSHER_FLUSH_CASCADES_4`
-     - integer
-   * - :ref:`Tokudb_FLUSHER_FLUSH_CASCADES_5`
-     - integer
-   * - :ref:`Tokudb_FLUSHER_FLUSH_CASCADES_GT_5`
-     - integer
-   * - :ref:`Tokudb_FLUSHER_SPLIT_LEAF`
-     - integer
-   * - :ref:`Tokudb_FLUSHER_SPLIT_NONLEAF`
-     - integer
-   * - :ref:`Tokudb_FLUSHER_MERGE_LEAF`
-     - integer
-   * - :ref:`Tokudb_FLUSHER_MERGE_NONLEAF`
-     - integer
-   * - :ref:`Tokudb_FLUSHER_BALANCE_LEAF`
-     - integer
-   * - :ref:`Tokudb_HOT_NUM_STARTED`
-     - integer
-   * - :ref:`Tokudb_HOT_NUM_COMPLETED`
-     - integer
-   * - :ref:`Tokudb_HOT_NUM_ABORTED`
-     - integer
-   * - :ref:`Tokudb_HOT_MAX_ROOT_FLUSH_COUNT`
-     - integer
-   * - :ref:`Tokudb_TXN_BEGIN`
-     - integer
-   * - :ref:`Tokudb_TXN_BEGIN_READ_ONLY`
-     - integer
-   * - :ref:`Tokudb_TXN_COMMITS`
-     - integer
-   * - :ref:`Tokudb_TXN_ABORTS`
-     - integer
-   * - :ref:`Tokudb_LOGGER_NEXT_LSN`
-     - integer
-   * - :ref:`Tokudb_LOGGER_WRITES`
-     - integer
-   * - :ref:`Tokudb_LOGGER_WRITES_BYTES`
-     - integer
-   * - :ref:`Tokudb_LOGGER_WRITES_UNCOMPRESSED_BYTES`
-     - integer
-   * - :ref:`Tokudb_LOGGER_WRITES_SECONDS`
-     - numeric
-   * - :ref:`Tokudb_LOGGER_WAIT_LONG`
-     - integer
-   * - :ref:`Tokudb_LOADER_NUM_CREATED`
-     - integer
-   * - :ref:`Tokudb_LOADER_NUM_CURRENT`
-     - integer
-   * - :ref:`Tokudb_LOADER_NUM_MAX`
-     - integer
-   * - :ref:`Tokudb_MEMORY_MALLOC_COUNT`
-     - integer
-   * - :ref:`Tokudb_MEMORY_FREE_COUNT`
-     - integer
-   * - :ref:`Tokudb_MEMORY_REALLOC_COUNT`
-     - integer
-   * - :ref:`Tokudb_MEMORY_MALLOC_FAIL`
-     - integer
-   * - :ref:`Tokudb_MEMORY_REALLOC_FAIL`
-     - integer
-   * - :ref:`Tokudb_MEMORY_REQUESTED`
-     - integer
-   * - :ref:`Tokudb_MEMORY_USED`
-     - integer
-   * - :ref:`Tokudb_MEMORY_FREED`
-     - integer
-   * - :ref:`Tokudb_MEMORY_MAX_REQUESTED_SIZE`
-     - integer
-   * - :ref:`Tokudb_MEMORY_LAST_FAILED_SIZE`
-     - integer
-   * - :ref:`Tokudb_MEM_ESTIMATED_MAXIMUM_MEMORY_FOOTPRINT`
-     - integer
-   * - :ref:`Tokudb_MEMORY_MALLOCATOR_VERSION`
-     - string
-   * - :ref:`Tokudb_MEMORY_MMAP_THRESHOLD`
-     - integer
-   * - :ref:`Tokudb_FILESYSTEM_THREADS_BLOCKED_BY_FULL_DISK`
-     - integer
-   * - :ref:`Tokudb_FILESYSTEM_FSYNC_TIME`
-     - integer
-   * - :ref:`Tokudb_FILESYSTEM_FSYNC_NUM`
-     - integer
-   * - :ref:`Tokudb_FILESYSTEM_LONG_FSYNC_TIME`
-     - integer
-   * - :ref:`Tokudb_FILESYSTEM_LONG_FSYNC_NUM`
-     - integer
-
-.. _Tokudb_DB_OPENS:
-
-.. rubric:: ``Tokudb_DB_OPENS``
-
-This variable shows the number of times an individual PerconaFT dictionary file
-was opened. This is a not a useful value for a regular user to use for any
-purpose due to layers of open/close caching on top.
-
-.. _Tokudb_DB_CLOSES:
-
-.. rubric:: ``Tokudb_DB_CLOSES``
-
-This variable shows the number of times an individual PerconaFT dictionary file
-was closed. This is a not a useful value for a regular user to use for any
-purpose due to layers of open/close caching on top.
-
-.. _Tokudb_DB_OPEN_CURRENT:
-
-.. rubric:: ``Tokudb_DB_OPEN_CURRENT``
-
-This variable shows the number of currently opened databases.
-
-.. _Tokudb_DB_OPEN_MAX:
-
-.. rubric:: ``Tokudb_DB_OPEN_MAX``
-
-This variable shows the maximum number of concurrently opened databases.
-
-.. _Tokudb_LEAF_ENTRY_MAX_COMMITTED_XR:
-
-.. rubric:: ``Tokudb_LEAF_ENTRY_MAX_COMMITTED_XR``
-
-This variable shows the maximum number of committed transaction records that
-were stored on disk in a new or modified row.
-
-.. _Tokudb_LEAF_ENTRY_MAX_PROVISIONAL_XR:
-
-.. rubric:: ``Tokudb_LEAF_ENTRY_MAX_PROVISIONAL_XR``
-
-This variable shows the maximum number of provisional transaction records that
-were stored on disk in a new or modified row.
-
-.. _Tokudb_LEAF_ENTRY_EXPANDED:
-
-.. rubric:: ``Tokudb_LEAF_ENTRY_EXPANDED``
-
-This variable shows the number of times that an expanded memory mechanism was
-used to store a new or modified row on disk.
-
-.. _Tokudb_LEAF_ENTRY_MAX_MEMSIZE:
-
-.. rubric:: ``Tokudb_LEAF_ENTRY_MAX_MEMSIZE``
-
-This variable shows the maximum number of bytes that were stored on disk as a
-new or modified row. This is the maximum uncompressed size of any row stored in
-*TokuDB* that was created or modified since the server started.
-
-.. _Tokudb_LEAF_ENTRY_APPLY_GC_BYTES_IN:
-
-.. rubric:: ``Tokudb_LEAF_ENTRY_APPLY_GC_BYTES_IN``
-
-This variable shows the total number of bytes of leaf nodes data before
-performing garbage collection for non-flush events.
-
-.. _Tokudb_LEAF_ENTRY_APPLY_GC_BYTES_OUT:
-
-.. rubric:: ``Tokudb_LEAF_ENTRY_APPLY_GC_BYTES_OUT``
-
-This variable shows the total number of bytes of leaf nodes data after
-performing garbage collection for non-flush events.
-
-.. _Tokudb_LEAF_ENTRY_NORMAL_GC_BYTES_IN:
-
-.. rubric:: ``Tokudb_LEAF_ENTRY_NORMAL_GC_BYTES_IN``
-
-This variable shows the total number of bytes of leaf nodes data before
-performing garbage collection for flush events.
-
-.. _Tokudb_LEAF_ENTRY_NORMAL_GC_BYTES_OUT:
-
-.. rubric:: ``Tokudb_LEAF_ENTRY_NORMAL_GC_BYTES_OUT``
-
-This variable shows the total number of bytes of leaf nodes data after
-performing garbage collection for flush events.
-
-.. _Tokudb_CHECKPOINT_PERIOD:
-
-.. rubric:: ``Tokudb_CHECKPOINT_PERIOD``
-
-This variable shows the interval in seconds between the end of an automatic
-checkpoint and the beginning of the next automatic checkpoint.
-
-.. _Tokudb_CHECKPOINT_FOOTPRINT:
-
-.. rubric:: ``Tokudb_CHECKPOINT_FOOTPRINT``
-
-This variable shows at what stage the checkpointer is at. It's used for
-debugging purposes only and not a useful value for a normal user.
-
-.. _Tokudb_CHECKPOINT_LAST_BEGAN:
-
-.. rubric:: ``Tokudb_CHECKPOINT_LAST_BEGAN``
-
-This variable shows the time the last checkpoint began. If a checkpoint is
-currently in progress, then this time may be later than the time the last
-checkpoint completed. If no checkpoint has ever taken place, then this value
-will be ``Dec 31, 1969`` on Linux hosts.
-
-.. _Tokudb_CHECKPOINT_LAST_COMPLETE_BEGAN:
-
-.. rubric:: ``Tokudb_CHECKPOINT_LAST_COMPLETE_BEGAN``
-
-This variable shows the time the last complete checkpoint started. Any data
-that changed after this time will not be captured in the checkpoint.
-
-.. _Tokudb_CHECKPOINT_LAST_COMPLETE_ENDED:
-
-.. rubric:: ``Tokudb_CHECKPOINT_LAST_COMPLETE_ENDED``
-
-This variable shows the time the last complete checkpoint ended.
-
-.. _Tokudb_CHECKPOINT_DURATION:
-
-.. rubric:: ``Tokudb_CHECKPOINT_DURATION``
-
-This variable shows time (in seconds) required to complete all
-checkpoints.
-
-.. _Tokudb_CHECKPOINT_DURATION_LAST:
-
-.. rubric:: ``Tokudb_CHECKPOINT_DURATION_LAST``
-
-This variable shows time (in seconds) required to complete the last
-checkpoint.
-
-.. _Tokudb_CHECKPOINT_LAST_LSN:
-
-.. rubric:: ``Tokudb_CHECKPOINT_LAST_LSN``
-
-This variable shows the last successful checkpoint LSN. Each checkpoint from
-the time the PerconaFT environment is created has a monotonically incrementing
-LSN. This is not a useful value for a normal user to use for any purpose other
-than having some idea of how many checkpoints have occurred since the system
-was first created.
-
-.. _Tokudb_CHECKPOINT_TAKEN:
-
-.. rubric:: ``Tokudb_CHECKPOINT_TAKEN`` 
-
-This variable shows the number of complete checkpoints that have been taken.
-
-.. _Tokudb_CHECKPOINT_FAILED:
-
-.. rubric:: ``Tokudb_CHECKPOINT_FAILED`` 
-
-This variable shows the number of checkpoints that have failed for any reason.
-
-.. _Tokudb_CHECKPOINT_WAITERS_NOW:
-
-.. rubric:: ``Tokudb_CHECKPOINT_WAITERS_NOW`` 
-
-This variable shows the current number of threads waiting for the ``checkpoint
-safe`` lock. This is a not a useful value for a regular user to use for any
-purpose.
-
-.. _Tokudb_CHECKPOINT_WAITERS_MAX:
-
-.. rubric:: ``Tokudb_CHECKPOINT_WAITERS_MAX`` 
-
-This variable shows the maximum number of threads that concurrently waited for
-the ``checkpoint safe`` lock. This is a not a useful value for a regular user to
-use for any purpose.
-
-.. _Tokudb_CHECKPOINT_CLIENT_WAIT_ON_MO:
-
-.. rubric:: ``Tokudb_CHECKPOINT_CLIENT_WAIT_ON_MO`` 
-
-This variable shows the number of times a non-checkpoint client thread waited
-for the multi-operation lock. It is an internal ``rwlock`` that is similar in
-nature to the *InnoDB* kernel mutex, it effectively halts all access to the
-PerconaFT API when write locked. The ``begin`` phase of the checkpoint takes
-this lock for a brief period.
-
-.. _Tokudb_CHECKPOINT_CLIENT_WAIT_ON_CS:
-
-.. rubric:: ``Tokudb_CHECKPOINT_CLIENT_WAIT_ON_CS`` 
-
-This variable shows the number of times a non-checkpoint client thread waited
-for the checkpoint-safe lock. This is the lock taken when you ``SET
-tokudb_checkpoint_lock=1``. If a client trying to lock/postpone the
-checkpointer has to wait for the currently running checkpoint to complete, that
-wait time will be reflected here and summed. This is not a useful metric as
-regular users should never be manipulating the checkpoint lock.
-
-.. _Tokudb_CHECKPOINT_BEGIN_TIME:
-
-.. rubric:: ``Tokudb_CHECKPOINT_BEGIN_TIME`` 
-
-This variable shows the cumulative time (in microseconds) required to mark all
-dirty nodes as pending a checkpoint.
-
-.. _Tokudb_CHECKPOINT_LONG_BEGIN_TIME:
-
-.. rubric:: ``Tokudb_CHECKPOINT_LONG_BEGIN_TIME`` 
-
-This variable shows the cumulative actual time (in microseconds) of checkpoint
-``begin`` stages that took longer than 1 second.
-
-.. _Tokudb_CHECKPOINT_LONG_BEGIN_COUNT:
-
-.. rubric:: ``Tokudb_CHECKPOINT_LONG_BEGIN_COUNT``
-
-This variable shows the number of checkpoints whose ``begin`` stage took longer
-than 1 second.
-
-.. _Tokudb_CHECKPOINT_END_TIME:
-
-.. rubric:: ``Tokudb_CHECKPOINT_END_TIME`` 
-
-This variable shows the time spent in checkpoint end operation in seconds.
-
-.. _Tokudb_CHECKPOINT_LONG_END_TIME:
-
-.. rubric:: ``Tokudb_CHECKPOINT_LONG_END_TIME`` 
-
-This variable shows the total time of long checkpoints in seconds.
-
-.. _Tokudb_CHECKPOINT_LONG_END_COUNT:
-
-.. rubric:: ``Tokudb_CHECKPOINT_LONG_END_COUNT`` 
-
-This variable shows the number of checkpoints whose ``end_checkpoint``
-operations exceeded 1 minute.
-
-.. _Tokudb_CACHETABLE_MISS:
-
-.. rubric:: ``Tokudb_CACHETABLE_MISS`` 
-
-This variable shows the number of times the application was unable to access
-the data in the internal cache. A cache miss means that date will need to be
-read from disk.
-
-.. _Tokudb_CACHETABLE_MISS_TIME:
-
-.. rubric:: ``Tokudb_CACHETABLE_MISS_TIME``  
-
-This variable shows the total time, in microseconds, of how long the database
-has had to wait for a disk read to complete.
-
-.. _Tokudb_CACHETABLE_PREFETCHES:
-
-.. rubric:: ``Tokudb_CACHETABLE_PREFETCHES``  
-
-This variable shows the total number of times that a block of memory has been
-prefetched into the database's cache. Data is prefetched when the database's
-algorithms determine that a block of memory is likely to be accessed by the
-application.
-
-.. _Tokudb_CACHETABLE_SIZE_CURRENT:
-
-.. rubric:: ``Tokudb_CACHETABLE_SIZE_CURRENT``  
-
-This variable shows how much of the uncompressed data, in bytes, is
-currently in the database's internal cache.
-
-.. _Tokudb_CACHETABLE_SIZE_LIMIT:
-
-.. rubric:: ``Tokudb_CACHETABLE_SIZE_LIMIT``  
-
-This variable shows how much of the uncompressed data, in bytes, will fit in
-the database's internal cache.
-
-.. _Tokudb_CACHETABLE_SIZE_WRITING:
-
-.. rubric:: ``Tokudb_CACHETABLE_SIZE_WRITING``  
-
-This variable shows the number of bytes that are currently queued up to be
-written to disk.
-
-.. _Tokudb_CACHETABLE_SIZE_NONLEAF:
-
-.. rubric:: ``Tokudb_CACHETABLE_SIZE_NONLEAF``  
-
-This variable shows the amount of memory, in bytes, the current set of non-leaf
-nodes occupy in the cache.
-
-.. _Tokudb_CACHETABLE_SIZE_LEAF:
-
-.. rubric:: ``Tokudb_CACHETABLE_SIZE_LEAF`` 
- 
-This variable shows the amount of memory, in bytes, the current set of
-(decompressed) leaf nodes occupy in the cache.
-
-.. _Tokudb_CACHETABLE_SIZE_ROLLBACK:
-
-.. rubric:: ``Tokudb_CACHETABLE_SIZE_ROLLBACK``  
-
-This variable shows the rollback nodes size, in bytes, in the cache.
-
-.. _Tokudb_CACHETABLE_SIZE_CACHEPRESSURE:
-
-.. rubric:: ``Tokudb_CACHETABLE_SIZE_CACHEPRESSURE``  
-
-This variable shows the number of bytes causing cache pressure (the sum of
-buffers and work done counters), helps to understand if cleaner threads are
-keeping up with workload. It should really be looked at as more of a value to
-use in a ratio of cache pressure / cache table size. The closer that ratio
-evaluates to 1, the higher the cache pressure.
-
-.. _Tokudb_CACHETABLE_SIZE_CLONED:
-
-.. rubric:: ``Tokudb_CACHETABLE_SIZE_CLONED`` 
-
-This variable shows the amount of memory, in bytes, currently used for cloned
-nodes. During the checkpoint operation, dirty nodes are cloned prior to
-serialization/compression, then written to disk. After which, the memory for
-the cloned block is returned for re-use.
-
-.. _Tokudb_CACHETABLE_EVICTIONS:
-
-.. rubric:: ``Tokudb_CACHETABLE_EVICTIONS`` 
-
-This variable shows the number of blocks evicted from cache. On its own this is
-not a useful number as its impact on performance depends entirely on the
-hardware and workload in use. For example, two workloads, one random, one
-linear for the same starting data set will have two wildly different eviction
-patterns.
-
-.. _Tokudb_CACHETABLE_CLEANER_EXECUTIONS:
-
-.. rubric:: ``Tokudb_CACHETABLE_CLEANER_EXECUTIONS`` 
-
-This variable shows the total number of times the cleaner thread loop has
-executed.
-
-.. _Tokudb_CACHETABLE_CLEANER_PERIOD:
-
-.. rubric:: ``Tokudb_CACHETABLE_CLEANER_PERIOD`` 
-
-*TokuDB* includes a cleaner thread that optimizes indexes in the background.
-This variable is the time, in seconds, between the completion of a group of
-cleaner operations and the beginning of the next group of cleaner operations.
-The cleaner operations run on a background thread performing work that does not
-need to be done on the client thread.
-
-.. _Tokudb_CACHETABLE_CLEANER_ITERATIONS:
-
-.. rubric:: ``Tokudb_CACHETABLE_CLEANER_ITERATIONS`` 
-
-This variable shows the number of cleaner operations that are performed every
-cleaner period.
-
-.. _Tokudb_CACHETABLE_WAIT_PRESSURE_COUNT:
-
-.. rubric:: ``Tokudb_CACHETABLE_WAIT_PRESSURE_COUNT`` 
-
-This variable shows the number of times a thread was stalled due to cache
-pressure. 
-
-.. _Tokudb_CACHETABLE_WAIT_PRESSURE_TIME:
-
-.. rubric:: ``Tokudb_CACHETABLE_WAIT_PRESSURE_TIME`` 
-
-This variable shows the total time, in microseconds, waiting on cache pressure
-to subside.
-
-.. _Tokudb_CACHETABLE_LONG_WAIT_PRESSURE_COUNT:
-
-.. rubric:: ``Tokudb_CACHETABLE_LONG_WAIT_PRESSURE_COUNT`` 
-
-This variable shows the number of times a thread was stalled for more than one
-second due to cache pressure.
-
-.. _Tokudb_CACHETABLE_LONG_WAIT_PRESSURE_TIME:
-
-.. rubric:: ``Tokudb_CACHETABLE_LONG_WAIT_PRESSURE_TIME`` 
-
-This variable shows the total time, in microseconds, waiting on cache pressure
-to subside for more than one second.
-
-.. _Tokudb_CACHETABLE_POOL_CLIENT_NUM_THREADS:
-
-.. rubric:: ``Tokudb_CACHETABLE_POOL_CLIENT_NUM_THREADS`` 
-
-This variable shows the number of threads in the client thread pool.
-
-.. _Tokudb_CACHETABLE_POOL_CLIENT_NUM_THREADS_ACTIVE:
-
-.. rubric:: ``Tokudb_CACHETABLE_POOL_CLIENT_NUM_THREADS_ACTIVE`` 
-
-This variable shows the number of currently active threads in the client
-thread pool.
-
-.. _Tokudb_CACHETABLE_POOL_CLIENT_QUEUE_SIZE:
-
-.. rubric:: ``Tokudb_CACHETABLE_POOL_CLIENT_QUEUE_SIZE`` 
-
-This variable shows the number of currently queued work items in the client
-thread pool.
-
-.. _Tokudb_CACHETABLE_POOL_CLIENT_MAX_QUEUE_SIZE:
-
-.. rubric:: ``Tokudb_CACHETABLE_POOL_CLIENT_MAX_QUEUE_SIZE`` 
-
-This variable shows the largest number of queued work items in the client
-thread pool.
-
-.. _Tokudb_CACHETABLE_POOL_CLIENT_TOTAL_ITEMS_PROCESSED:
-
-.. rubric:: ``Tokudb_CACHETABLE_POOL_CLIENT_TOTAL_ITEMS_PROCESSED`` 
-
-This variable shows the total number of work items processed in the client
-thread pool.
-
-.. _Tokudb_CACHETABLE_POOL_CLIENT_TOTAL_EXECUTION_TIME:
-
-.. rubric:: ``Tokudb_CACHETABLE_POOL_CLIENT_TOTAL_EXECUTION_TIME`` 
-
-This variable shows the total execution time of processing work items in the
-client thread pool.
-
-.. _Tokudb_CACHETABLE_POOL_CACHETABLE_NUM_THREADS:
-
-.. rubric:: ``Tokudb_CACHETABLE_POOL_CACHETABLE_NUM_THREADS`` 
-
-This variable shows the number of threads in the cachetable threadpool.
-
-.. _Tokudb_CACHETABLE_POOL_CACHETABLE_NUM_THREADS_ACTIVE:
-
-.. rubric:: ``Tokudb_CACHETABLE_POOL_CACHETABLE_NUM_THREADS_ACTIVE`` 
-
-This variable shows the number of currently active threads in the cachetable
-thread pool.
-
-.. _Tokudb_CACHETABLE_POOL_CACHETABLE_QUEUE_SIZE:
-
-.. rubric:: ``Tokudb_CACHETABLE_POOL_CACHETABLE_QUEUE_SIZE`` 
-
-This variable shows the number of currently queued work items in the cachetable
-thread pool. 
-
-.. _Tokudb_CACHETABLE_POOL_CACHETABLE_MAX_QUEUE_SIZE:
-
-.. rubric:: ``Tokudb_CACHETABLE_POOL_CACHETABLE_MAX_QUEUE_SIZE`` 
-
-This variable shows the largest number of queued work items in the cachetable
-thread pool.
-
-.. _Tokudb_CACHETABLE_POOL_CACHETABLE_TOTAL_ITEMS_PROCESSED:
-
-.. rubric:: ``Tokudb_CACHETABLE_POOL_CACHETABLE_TOTAL_ITEMS_PROCESSED`` 
-
-This variable shows the total number of work items processed in the cachetable
-thread pool.
-
-.. _Tokudb_CACHETABLE_POOL_CACHETABLE_TOTAL_EXECUTION_TIME:
-
-.. rubric:: ``Tokudb_CACHETABLE_POOL_CACHETABLE_TOTAL_EXECUTION_TIME`` 
-
-This variable shows the total execution time of processing work items in the
-cachetable thread pool.
-
-.. _Tokudb_CACHETABLE_POOL_CHECKPOINT_NUM_THREADS:
-
-.. rubric:: ``Tokudb_CACHETABLE_POOL_CHECKPOINT_NUM_THREADS`` 
-
-This variable shows the number of threads in the checkpoint threadpool.
-
-.. _Tokudb_CACHETABLE_POOL_CHECKPOINT_NUM_THREADS_ACTIVE:
-
-.. rubric:: ``Tokudb_CACHETABLE_POOL_CHECKPOINT_NUM_THREADS_ACTIVE`` 
-
-This variable shows the number of currently active threads in the checkpoint
-thread pool.
-
-.. _Tokudb_CACHETABLE_POOL_CHECKPOINT_QUEUE_SIZE:
-
-.. rubric:: ``Tokudb_CACHETABLE_POOL_CHECKPOINT_QUEUE_SIZE`` 
-
-This variable shows the number of currently queued work items in the checkpoint
-thread pool. 
-
-.. _Tokudb_CACHETABLE_POOL_CHECKPOINT_MAX_QUEUE_SIZE:
-
-.. rubric:: ``Tokudb_CACHETABLE_POOL_CHECKPOINT_MAX_QUEUE_SIZE`` 
-
-This variable shows the largest number of queued work items in the checkpoint
-thread pool.
-
-.. _Tokudb_CACHETABLE_POOL_CHECKPOINT_TOTAL_ITEMS_PROCESSED:
-
-.. rubric:: ``Tokudb_CACHETABLE_POOL_CHECKPOINT_TOTAL_ITEMS_PROCESSED`` 
-
-This variable shows the total number of work items processed in the checkpoint
-thread pool.
-
-.. _Tokudb_CACHETABLE_POOL_CHECKPOINT_TOTAL_EXECUTION_TIME:
-
-.. rubric:: ``Tokudb_CACHETABLE_POOL_CHECKPOINT_TOTAL_EXECUTION_TIME`` 
-
-This variable shows the total execution time of processing work items in the
-checkpoint thread pool.
-
-.. _Tokudb_LOCKTREE_MEMORY_SIZE:
-
-.. rubric:: ``Tokudb_LOCKTREE_MEMORY_SIZE`` 
-
-This variable shows the amount of memory, in bytes, that the locktree is
-currently using.
-
-.. _Tokudb_LOCKTREE_MEMORY_SIZE_LIMIT:
-
-.. rubric:: ``Tokudb_LOCKTREE_MEMORY_SIZE_LIMIT`` 
-
-This variable shows the maximum amount of memory, in bytes, that the locktree
-is allowed to use.
-
-.. _Tokudb_LOCKTREE_ESCALATION_NUM:
-
-.. rubric:: ``Tokudb_LOCKTREE_ESCALATION_NUM`` 
-
-This variable shows the number of times the locktree needed to run lock
-escalation to reduce its memory footprint.
-
-.. _Tokudb_LOCKTREE_ESCALATION_SECONDS:
-
-.. rubric:: ``Tokudb_LOCKTREE_ESCALATION_SECONDS`` 
-
-This variable shows the total number of seconds spent performing locktree
-escalation.
-
-.. _Tokudb_LOCKTREE_LATEST_POST_ESCALATION_MEMORY_SIZE:
-
-.. rubric:: ``Tokudb_LOCKTREE_LATEST_POST_ESCALATION_MEMORY_SIZE`` 
-
-This variable shows the locktree size, in bytes, after most current locktree
-escalation.
-
-.. _Tokudb_LOCKTREE_OPEN_CURRENT:
-
-.. rubric:: ``Tokudb_LOCKTREE_OPEN_CURRENT`` 
-
-This variable shows the number of locktrees that are currently opened.
-
-.. _Tokudb_LOCKTREE_PENDING_LOCK_REQUESTS:
-
-.. rubric:: ``Tokudb_LOCKTREE_PENDING_LOCK_REQUESTS`` 
-
-This variable shows the number of requests waiting for a lock grant.
-
-.. _Tokudb_LOCKTREE_STO_ELIGIBLE_NUM:
-
-.. rubric:: ``Tokudb_LOCKTREE_STO_ELIGIBLE_NUM`` 
-
-This variable shows the number of locktrees eligible for ``Single Transaction
-optimizations``. STO optimization are behaviors that can happen within the
-locktree when there is exactly one transaction active within the locktree. This
-is a not a useful value for a regular user to use for any purpose.
-
-.. _Tokudb_LOCKTREE_STO_ENDED_NUM:
-
-.. rubric:: ``Tokudb_LOCKTREE_STO_ENDED_NUM`` 
-
-This variable shows the total number of times a ``Single Transaction
-Optimization`` was ended early due to another transaction starting. STO
-optimization are behaviors that can happen within the locktree when there is
-exactly one transaction active within the locktree. This is a not a useful
-value for a regular user to use for any purpose.
-
-.. _Tokudb_LOCKTREE_STO_ENDED_SECONDS:
-
-.. rubric:: ``Tokudb_LOCKTREE_STO_ENDED_SECONDS`` 
-
-This variable shows the total number of seconds ending the ``Single
-Transaction Optimizations``. STO optimization are behaviors that can happen
-within the locktree when there is exactly one transaction active within the
-locktree. This is a not a useful value for a regular user to use for any
-purpose.
-
-.. _Tokudb_LOCKTREE_WAIT_COUNT:
-
-.. rubric:: ``Tokudb_LOCKTREE_WAIT_COUNT`` 
-
-This variable shows the number of times that a lock request could not be
-acquired because of a conflict with some other transaction. PerconaFT lock
-request  cycles to try to obtain a lock, if it can not get a lock, it
-sleeps/waits and times out, checks to get the lock again, repeat. This value
-indicates the number of cycles it needed to execute before it obtained the
-lock. 
-
-.. _Tokudb_LOCKTREE_WAIT_TIME:
-
-.. rubric:: ``Tokudb_LOCKTREE_WAIT_TIME`` 
-
-This variable shows the total time, in microseconds, spent by client waiting
-for a lock conflict to be resolved.
-
-.. _Tokudb_LOCKTREE_LONG_WAIT_COUNT:
-
-.. rubric:: ``Tokudb_LOCKTREE_LONG_WAIT_COUNT`` 
-
-This variable shows number of lock waits greater than one second in duration.
-
-.. _Tokudb_LOCKTREE_LONG_WAIT_TIME:
-
-.. rubric:: ``Tokudb_LOCKTREE_LONG_WAIT_TIME`` 
-
-This variable shows the total time, in microseconds, of the long waits.
-
-.. _Tokudb_LOCKTREE_TIMEOUT_COUNT:
-
-.. rubric:: ``Tokudb_LOCKTREE_TIMEOUT_COUNT`` 
-
-This variable shows the number of times that a lock request timed out.
-
-.. _Tokudb_LOCKTREE_WAIT_ESCALATION_COUNT:
-
-.. rubric:: ``Tokudb_LOCKTREE_WAIT_ESCALATION_COUNT`` 
-
-When the sum of the sizes of locks taken reaches the lock tree limit, we run
-lock escalation on a background thread. The clients threads need to wait for
-escalation to consolidate locks and free up memory. This variables shows the
-number of times a client thread had to wait on lock escalation.
-
-.. _Tokudb_LOCKTREE_WAIT_ESCALATION_TIME:
-
-.. rubric:: ``Tokudb_LOCKTREE_WAIT_ESCALATION_TIME`` 
-
-This variable shows the total time, in microseconds, that a client thread spent
-waiting for lock escalation to free up memory.
-
-.. _Tokudb_LOCKTREE_LONG_WAIT_ESCALATION_COUNT:
-
-.. rubric:: ``Tokudb_LOCKTREE_LONG_WAIT_ESCALATION_COUNT`` 
-
-This variable shows number of times that a client thread had to wait on lock
-escalation and the wait time was greater than one second.
-
-.. _Tokudb_LOCKTREE_LONG_WAIT_ESCALATION_TIME:
-.. rubric:: ``Tokudb_LOCKTREE_LONG_WAIT_ESCALATION_TIME`` 
-
-This variable shows the total time, in microseconds, of the long waits for lock
-escalation to free up memory.
-
-.. _Tokudb_DICTIONARY_UPDATES:
-
-.. rubric:: ``Tokudb_DICTIONARY_UPDATES`` 
-
-This variable shows the total number of rows that have been updated in all
-primary and secondary indexes combined, if those updates have been done with a
-separate recovery log entry per index.
-
-.. _Tokudb_DICTIONARY_BROADCAST_UPDATES:
-
-.. rubric:: ``Tokudb_DICTIONARY_BROADCAST_UPDATES`` 
-
-This variable shows the number of broadcast updates that have been successfully
-performed. A broadcast update is an update that affects all rows in a
-dictionary.
-
-.. _Tokudb_DESCRIPTOR_SET:
-
-.. rubric:: ``Tokudb_DESCRIPTOR_SET`` 
-
-This variable shows the number of time a descriptor was updated when the entire
-dictionary was updated (for example, when the schema has been changed).
-
-.. _Tokudb_MESSAGES_IGNORED_BY_LEAF_DUE_TO_MSN:
-
-.. rubric:: ``Tokudb_MESSAGES_IGNORED_BY_LEAF_DUE_TO_MSN`` 
-
-This variable shows the number of messages that were ignored by a leaf because
-it had already been applied.
-
-.. _Tokudb_TOTAL_SEARCH_RETRIES:
-
-.. rubric:: ``Tokudb_TOTAL_SEARCH_RETRIES`` 
-
-Internal value that is no use to anyone other than a developer debugging a
-specific query/search issue.
-
-.. _Tokudb_SEARCH_TRIES_GT_HEIGHT:
-
-.. rubric:: ``Tokudb_SEARCH_TRIES_GT_HEIGHT`` 
-
-Internal value that is no use to anyone other than a developer debugging a
-specific query/search issue.
-
-.. _Tokudb_SEARCH_TRIES_GT_HEIGHTPLUS3:
-
-.. rubric:: ``Tokudb_SEARCH_TRIES_GT_HEIGHTPLUS3`` 
-
-Internal value that is no use to anyone other than a developer debugging a
-specific query/search issue.
-
-.. _Tokudb_LEAF_NODES_FLUSHED_NOT_CHECKPOINT:
-
-.. rubric:: ``Tokudb_LEAF_NODES_FLUSHED_NOT_CHECKPOINT`` 
-
-This variable shows the number of leaf nodes flushed to disk, not for
-checkpoint.
-
-.. _Tokudb_LEAF_NODES_FLUSHED_NOT_CHECKPOINT_BYTES:
-
-.. rubric:: ``Tokudb_LEAF_NODES_FLUSHED_NOT_CHECKPOINT_BYTES`` 
-
-This variable shows the size, in bytes, of leaf nodes flushed to disk, not
-for checkpoint.
-
-.. _Tokudb_LEAF_NODES_FLUSHED_NOT_CHECKPOINT_UNCOMPRESSED_BYTES:
-
-.. rubric:: ``Tokudb_LEAF_NODES_FLUSHED_NOT_CHECKPOINT_UNCOMPRESSED_BYTES`` 
-
-This variable shows the size, in bytes, of uncompressed leaf nodes flushed to
-disk not for checkpoint.
-
-.. _Tokudb_LEAF_NODES_FLUSHED_NOT_CHECKPOINT_SECONDS:
-
-.. rubric:: ``Tokudb_LEAF_NODES_FLUSHED_NOT_CHECKPOINT_SECONDS`` 
-
-This variable shows the number of seconds waiting for I/O when writing leaf
-nodes flushed to disk, not for checkpoint
-
-.. _Tokudb_NONLEAF_NODES_FLUSHED_TO_DISK_NOT_CHECKPOINT:
-
-.. rubric:: ``Tokudb_NONLEAF_NODES_FLUSHED_TO_DISK_NOT_CHECKPOINT`` 
-
-This variable shows the number of non-leaf nodes flushed to disk, not for
-checkpoint.
-
-.. _Tokudb_NONLEAF_NODES_FLUSHED_TO_DISK_NOT_CHECKPOINT_BYTES:
-
-.. rubric:: ``Tokudb_NONLEAF_NODES_FLUSHED_TO_DISK_NOT_CHECKPOINT_BYTES`` 
-
-This variable shows the size, in bytes, of non-leaf nodes flushed to disk, not
-for checkpoint.
-
-.. _Tokudb_NONLEAF_NODES_FLUSHED_TO_DISK_NOT_CHECKPOINT_UNCOMPRESSE:
-
-.. rubric:: ``Tokudb_NONLEAF_NODES_FLUSHED_TO_DISK_NOT_CHECKPOINT_UNCOMPRESSE`` 
-
-This variable shows the size, in bytes, of uncompressed non-leaf nodes flushed
-to disk not for checkpoint.
-
-.. _Tokudb_NONLEAF_NODES_FLUSHED_TO_DISK_NOT_CHECKPOINT_SECONDS:
-
-.. rubric:: ``Tokudb_NONLEAF_NODES_FLUSHED_TO_DISK_NOT_CHECKPOINT_SECONDS`` 
-
-This variable shows the number of seconds waiting for I/O when writing non-leaf
-nodes flushed to disk, not for checkpoint
-
-.. _Tokudb_LEAF_NODES_FLUSHED_CHECKPOINT:
-
-.. rubric:: ``Tokudb_LEAF_NODES_FLUSHED_CHECKPOINT`` 
-
-This variable shows the number of leaf nodes flushed to disk, for checkpoint.
-
-.. _Tokudb_LEAF_NODES_FLUSHED_CHECKPOINT_BYTES:
-
-.. rubric:: ``Tokudb_LEAF_NODES_FLUSHED_CHECKPOINT_BYTES`` 
-
-This variable shows the size, in bytes, of leaf nodes flushed to disk, for
-checkpoint.
-
-.. _Tokudb_LEAF_NODES_FLUSHED_CHECKPOINT_UNCOMPRESSED_BYTES:
-
-.. rubric:: ``Tokudb_LEAF_NODES_FLUSHED_CHECKPOINT_UNCOMPRESSED_BYTES`` 
-
-This variable shows the size, in bytes, of uncompressed leaf nodes flushed to
-disk for checkpoint.
-
-.. _Tokudb_LEAF_NODES_FLUSHED_CHECKPOINT_SECONDS:
-
-.. rubric:: ``Tokudb_LEAF_NODES_FLUSHED_CHECKPOINT_SECONDS`` 
-
-This variable shows the number of seconds waiting for I/O when writing leaf
-nodes flushed to disk for checkpoint
-
-.. _Tokudb_NONLEAF_NODES_FLUSHED_TO_DISK_CHECKPOINT:
-
-.. rubric:: ``Tokudb_NONLEAF_NODES_FLUSHED_TO_DISK_CHECKPOINT`` 
-
-This variable shows the number of non-leaf nodes flushed to disk, for
-checkpoint.
-
-.. _Tokudb_NONLEAF_NODES_FLUSHED_TO_DISK_CHECKPOINT_BYTES:
-
-.. rubric:: ``Tokudb_NONLEAF_NODES_FLUSHED_TO_DISK_CHECKPOINT_BYTES`` 
-
-This variable shows the size, in bytes, of non-leaf nodes flushed to disk, for
-checkpoint.
-
-.. _Tokudb_NONLEAF_NODES_FLUSHED_TO_DISK_CHECKPOINT_UNCOMPRESSED_BY:
-
-.. rubric:: ``Tokudb_NONLEAF_NODES_FLUSHED_TO_DISK_CHECKPOINT_UNCOMPRESSED_BY`` 
-
-This variable shows the size, in bytes, of uncompressed non-leaf nodes flushed
-to disk for checkpoint.
-
-.. _Tokudb_NONLEAF_NODES_FLUSHED_TO_DISK_CHECKPOINT_SECONDS:
-
-.. rubric:: ``Tokudb_NONLEAF_NODES_FLUSHED_TO_DISK_CHECKPOINT_SECONDS`` 
-
-This variable shows the number of seconds waiting for I/O when writing non-leaf
-nodes flushed to disk for checkpoint
-
-.. _Tokudb_LEAF_NODE_COMPRESSION_RATIO:
-
-.. rubric:: ``Tokudb_LEAF_NODE_COMPRESSION_RATIO`` 
-
-This variable shows the ratio of uncompressed bytes (in-memory) to compressed
-bytes (on-disk) for leaf nodes.
-
-.. _Tokudb_NONLEAF_NODE_COMPRESSION_RATIO:
-
-.. rubric:: ``Tokudb_NONLEAF_NODE_COMPRESSION_RATIO`` 
-
-This variable shows the ratio of uncompressed bytes (in-memory) to compressed
-bytes (on-disk) for non-leaf nodes.
-
-.. _Tokudb_OVERALL_NODE_COMPRESSION_RATIO:
-
-.. rubric:: ``Tokudb_OVERALL_NODE_COMPRESSION_RATIO`` 
-
-This variable shows the ratio of uncompressed bytes (in-memory) to compressed
-bytes (on-disk) for all nodes.
-
-.. _Tokudb_NONLEAF_NODE_PARTIAL_EVICTIONS:
-
-.. rubric:: ``Tokudb_NONLEAF_NODE_PARTIAL_EVICTIONS`` 
-
-This variable shows the number of times a partition of a non-leaf node was
-evicted from the cache.
-
-.. _Tokudb_NONLEAF_NODE_PARTIAL_EVICTIONS_BYTES:
-
-.. rubric:: ``Tokudb_NONLEAF_NODE_PARTIAL_EVICTIONS_BYTES`` 
-
-This variable shows the amount, in bytes, of memory freed by evicting
-partitions of non-leaf nodes from the cache.
-
-.. _Tokudb_LEAF_NODE_PARTIAL_EVICTIONS:
-
-.. rubric:: ``Tokudb_LEAF_NODE_PARTIAL_EVICTIONS`` 
-
-This variable shows the number of times a partition of a leaf node was evicted
-from the cache.
-
-.. _Tokudb_LEAF_NODE_PARTIAL_EVICTIONS_BYTES:
-
-.. rubric:: ``Tokudb_LEAF_NODE_PARTIAL_EVICTIONS_BYTES`` 
-
-This variable shows the amount, in bytes, of memory freed by evicting
-partitions of leaf nodes from the cache.
-
-.. _Tokudb_LEAF_NODE_FULL_EVICTIONS:
-
-.. rubric:: ``Tokudb_LEAF_NODE_FULL_EVICTIONS`` 
-
-This variable shows the number of times a full leaf node was evicted from the
-cache.
-
-.. _Tokudb_LEAF_NODE_FULL_EVICTIONS_BYTES:
-
-.. rubric:: ``Tokudb_LEAF_NODE_FULL_EVICTIONS_BYTES`` 
-
-This variable shows the amount, in bytes, of memory freed by evicting full leaf
-nodes from the cache.
-
-.. _Tokudb_NONLEAF_NODE_FULL_EVICTIONS:
-
-.. rubric:: ``Tokudb_NONLEAF_NODE_FULL_EVICTIONS`` 
-
-This variable shows the number of times a full non-leaf node was evicted from
-the cache.
-
-.. _Tokudb_NONLEAF_NODE_FULL_EVICTIONS_BYTES:
-
-.. rubric:: ``Tokudb_NONLEAF_NODE_FULL_EVICTIONS_BYTES`` 
-
-This variable shows the amount, in bytes, of memory freed by evicting full
-non-leaf nodes from the cache.
-
-.. _Tokudb_LEAF_NODES_CREATED:
-
-.. rubric:: ``Tokudb_LEAF_NODES_CREATED`` 
-
-This variable shows the number of created leaf nodes.
-
-.. _Tokudb_NONLEAF_NODES_CREATED:
-
-.. rubric:: ``Tokudb_NONLEAF_NODES_CREATED`` 
-
-This variable shows the number of created non-leaf nodes.
-
-.. _Tokudb_LEAF_NODES_DESTROYED:
-
-.. rubric:: ``Tokudb_LEAF_NODES_DESTROYED`` 
-
-This variable shows the number of destroyed leaf nodes.
-
-.. _Tokudb_NONLEAF_NODES_DESTROYED:
-
-.. rubric:: ``Tokudb_NONLEAF_NODES_DESTROYED`` 
-
-This variable shows the number of destroyed non-leaf nodes.
-
-.. _Tokudb_MESSAGES_INJECTED_AT_ROOT_BYTES:
-
-.. rubric:: ``Tokudb_MESSAGES_INJECTED_AT_ROOT_BYTES`` 
-
-This variable shows the size, in bytes, of messages injected at root (for all
-trees).
-
-.. _Tokudb_MESSAGES_FLUSHED_FROM_H1_TO_LEAVES_BYTES:
-
-.. rubric:: ``Tokudb_MESSAGES_FLUSHED_FROM_H1_TO_LEAVES_BYTES`` 
-
-This variable shows the size, in bytes, of messages flushed from ``h1`` nodes
-to leaves.
-
-.. _Tokudb_MESSAGES_IN_TREES_ESTIMATE_BYTES:
-
-.. rubric:: ``Tokudb_MESSAGES_IN_TREES_ESTIMATE_BYTES`` 
-
-This variable shows the estimated size, in bytes, of messages currently in
-trees. 
-
-.. _Tokudb_MESSAGES_INJECTED_AT_ROOT:
-
-.. rubric:: ``Tokudb_MESSAGES_INJECTED_AT_ROOT`` 
-
-This variables shows the number of messages that were injected at root node of
-a tree.
-
-.. _Tokudb_BROADCASE_MESSAGES_INJECTED_AT_ROOT:
-
-.. rubric:: ``Tokudb_BROADCASE_MESSAGES_INJECTED_AT_ROOT`` 
-
-This variable shows the number of broadcast messages dropped into the root node
-of a tree. These are things such as the result of ``OPTIMIZE TABLE`` and a few
-other operations. This is not a useful metric for a regular user to use for any
-purpose.
-
-.. _Tokudb_BASEMENTS_DECOMPRESSED_TARGET_QUERY:
-
-.. rubric:: ``Tokudb_BASEMENTS_DECOMPRESSED_TARGET_QUERY`` 
-
-This variable shows the number of basement nodes decompressed for queries.
-
-.. _Tokudb_BASEMENTS_DECOMPRESSED_PRELOCKED_RANGE:
-
-.. rubric:: ``Tokudb_BASEMENTS_DECOMPRESSED_PRELOCKED_RANGE`` 
-
-This variable shows the number of basement nodes aggressively decompressed by
-queries.
-
-.. _Tokudb_BASEMENTS_DECOMPRESSED_PREFETCH:
-
-.. rubric:: ``Tokudb_BASEMENTS_DECOMPRESSED_PREFETCH`` 
-
-This variable shows the number of basement nodes decompressed by a prefetch
-thread.
-
-.. _Tokudb_BASEMENTS_DECOMPRESSED_FOR_WRITE:
-
-.. rubric:: ``Tokudb_BASEMENTS_DECOMPRESSED_FOR_WRITE`` 
-
-This variable shows the number of basement nodes decompressed for writes.
-
-.. _Tokudb_BUFFERS_DECOMPRESSED_TARGET_QUERY:
-
-.. rubric:: ``Tokudb_BUFFERS_DECOMPRESSED_TARGET_QUERY`` 
-
-This variable shows the number of buffers decompressed for queries.
-
-.. _Tokudb_BUFFERS_DECOMPRESSED_PRELOCKED_RANGE:
-
-.. rubric:: ``Tokudb_BUFFERS_DECOMPRESSED_PRELOCKED_RANGE`` 
-
-This variable shows the number of buffers decompressed by queries aggressively.
-
-.. _Tokudb_BUFFERS_DECOMPRESSED_PREFETCH:
-
-.. rubric:: ``Tokudb_BUFFERS_DECOMPRESSED_PREFETCH`` 
-
-This variable shows the number of buffers decompressed by a prefetch thread.
-
-.. _Tokudb_BUFFERS_DECOMPRESSED_FOR_WRITE:
-
-.. rubric:: ``Tokudb_BUFFERS_DECOMPRESSED_FOR_WRITE`` 
-
-This variable shows the number of buffers decompressed for writes.
-
-.. _Tokudb_PIVOTS_FETCHED_FOR_QUERY:
-
-.. rubric:: ``Tokudb_PIVOTS_FETCHED_FOR_QUERY`` 
-
-This variable shows the number of pivot nodes fetched for queries.
-
-.. _Tokudb_PIVOTS_FETCHED_FOR_QUERY_BYTES:
-
-.. rubric:: ``Tokudb_PIVOTS_FETCHED_FOR_QUERY_BYTES`` 
-
-This variable shows the number of bytes of pivot nodes fetched for queries.
-
-.. _Tokudb_PIVOTS_FETCHED_FOR_QUERY_SECONDS:
-
-.. rubric:: ``Tokudb_PIVOTS_FETCHED_FOR_QUERY_SECONDS`` 
-
-This variable shows the number of seconds waiting for I/O when fetching pivot
-nodes for queries.
-
-.. _Tokudb_PIVOTS_FETCHED_FOR_PREFETCH:
-
-.. rubric:: ``Tokudb_PIVOTS_FETCHED_FOR_PREFETCH`` 
-
-This variable shows the number of pivot nodes fetched by a prefetch thread.
-
-.. _Tokudb_PIVOTS_FETCHED_FOR_PREFETCH_BYTES:
-
-.. rubric:: ``Tokudb_PIVOTS_FETCHED_FOR_PREFETCH_BYTES`` 
-
-This variable shows the number of bytes of pivot nodes fetched for queries.
-
-.. _Tokudb_PIVOTS_FETCHED_FOR_PREFETCH_SECONDS:
-
-.. rubric:: ``Tokudb_PIVOTS_FETCHED_FOR_PREFETCH_SECONDS`` 
-
-This variable shows the number seconds waiting for I/O when fetching pivot
-nodes by a prefetch thread.
-
-.. _Tokudb_PIVOTS_FETCHED_FOR_WRITE:
-
-.. rubric:: ``Tokudb_PIVOTS_FETCHED_FOR_WRITE`` 
-
-This variable shows the number of pivot nodes fetched for writes.
-
-.. _Tokudb_PIVOTS_FETCHED_FOR_WRITE_BYTES:
-
-.. rubric:: ``Tokudb_PIVOTS_FETCHED_FOR_WRITE_BYTES`` 
-
-This variable shows the number of bytes of pivot nodes fetched for writes.
-
-.. _Tokudb_PIVOTS_FETCHED_FOR_WRITE_SECONDS:
-
-.. rubric:: ``Tokudb_PIVOTS_FETCHED_FOR_WRITE_SECONDS`` 
-
-This variable shows the number of seconds waiting for I/O when fetching pivot
-nodes for writes.
-
-.. _Tokudb_BASEMENTS_FETCHED_TARGET_QUERY:
-
-.. rubric:: ``Tokudb_BASEMENTS_FETCHED_TARGET_QUERY`` 
-
-This variable shows the number of basement nodes fetched from disk for queries.
-
-.. _Tokudb_BASEMENTS_FETCHED_TARGET_QUERY_BYTES:
-
-.. rubric:: ``Tokudb_BASEMENTS_FETCHED_TARGET_QUERY_BYTES`` 
-
-This variable shows the number of basement node bytes fetched from disk for
-queries.
-
-.. _Tokudb_BASEMENTS_FETCHED_TARGET_QUERY_SECONDS:
-
-.. rubric:: ``Tokudb_BASEMENTS_FETCHED_TARGET_QUERY_SECONDS`` 
-
-This variable shows the number of seconds waiting for I/O when fetching
-basement nodes from disk for queries.
-
-.. _Tokudb_BASEMENTS_FETCHED_PRELOCKED_RANGE:
-
-.. rubric:: ``Tokudb_BASEMENTS_FETCHED_PRELOCKED_RANGE`` 
-
-This variable shows the number of basement nodes fetched from disk
-aggressively.
-
-.. _Tokudb_BASEMENTS_FETCHED_PRELOCKED_RANGE_BYTES:
-
-.. rubric:: ``Tokudb_BASEMENTS_FETCHED_PRELOCKED_RANGE_BYTES`` 
-
-This variable shows the number of basement node bytes fetched from disk
-aggressively.
-
-.. _Tokudb_BASEMENTS_FETCHED_PRELOCKED_RANGE_SECONDS:
-
-.. rubric:: ``Tokudb_BASEMENTS_FETCHED_PRELOCKED_RANGE_SECONDS`` 
-
-This variable shows the number of seconds waiting for I/O when fetching
-basement nodes from disk aggressively.
-
-.. _Tokudb_BASEMENTS_FETCHED_PREFETCH:
-
-.. rubric:: ``Tokudb_BASEMENTS_FETCHED_PREFETCH`` 
-
-This variable shows the number of basement nodes fetched from disk by a
-prefetch thread.
-
-.. _Tokudb_BASEMENTS_FETCHED_PREFETCH_BYTES:
-
-.. rubric:: ``Tokudb_BASEMENTS_FETCHED_PREFETCH_BYTES`` 
-
-This variable shows the number of basement node bytes fetched from disk by a
-prefetch thread.
-
-
-.. _Tokudb_BASEMENTS_FETCHED_PREFETCH_SECONDS:
-
-.. rubric:: ``Tokudb_BASEMENTS_FETCHED_PREFETCH_SECONDS`` 
-
-This variable shows the number of seconds waiting for I/O when fetching
-basement nodes from disk by a prefetch thread.
-
-.. _Tokudb_BASEMENTS_FETCHED_FOR_WRITE:
-
-.. rubric:: ``Tokudb_BASEMENTS_FETCHED_FOR_WRITE`` 
-
-This variable shows the number of buffers fetched from disk for writes.
-
-.. _Tokudb_BASEMENTS_FETCHED_FOR_WRITE_BYTES:
-
-.. rubric:: ``Tokudb_BASEMENTS_FETCHED_FOR_WRITE_BYTES`` 
-
-This variable shows the number of buffer bytes fetched from disk for writes.
-
-.. _Tokudb_BASEMENTS_FETCHED_FOR_WRITE_SECONDS:
-
-.. rubric:: ``Tokudb_BASEMENTS_FETCHED_FOR_WRITE_SECONDS`` 
-
-This variable shows the number of seconds waiting for I/O when fetching buffers
-from disk for writes.
-
-.. _Tokudb_BUFFERS_FETCHED_TARGET_QUERY:
-
-.. rubric:: ``Tokudb_BUFFERS_FETCHED_TARGET_QUERY`` 
-
-This variable shows the number of buffers fetched from disk for queries.
-
-.. _Tokudb_BUFFERS_FETCHED_TARGET_QUERY_BYTES:
-
-.. rubric:: ``Tokudb_BUFFERS_FETCHED_TARGET_QUERY_BYTES`` 
-
-This variable shows the number of buffer bytes fetched from disk for queries.
-
-.. _Tokudb_BUFFERS_FETCHED_TARGET_QUERY_SECONDS:
-
-.. rubric:: ``Tokudb_BUFFERS_FETCHED_TARGET_QUERY_SECONDS`` 
-
-This variable shows the number of seconds waiting for I/O when fetching buffers
-from disk for queries.
-
-.. _Tokudb_BUFFERS_FETCHED_PRELOCKED_RANGE:
-
-.. rubric:: ``Tokudb_BUFFERS_FETCHED_PRELOCKED_RANGE`` 
-
-This variable shows the number of buffers fetched from disk aggressively.
-
-.. _Tokudb_BUFFERS_FETCHED_PRELOCKED_RANGE_BYTES:
-
-.. rubric:: ``Tokudb_BUFFERS_FETCHED_PRELOCKED_RANGE_BYTES`` 
-
-This variable shows the number of buffer bytes fetched from disk aggressively.
-
-.. _Tokudb_BUFFERS_FETCHED_PRELOCKED_RANGE_SECONDS:
-
-.. rubric:: ``Tokudb_BUFFERS_FETCHED_PRELOCKED_RANGE_SECONDS`` 
-
-This variable shows the number of seconds waiting for I/O when fetching buffers
-from disk aggressively.
-
-.. _Tokudb_BUFFERS_FETCHED_PREFETCH:
-
-.. rubric:: ``Tokudb_BUFFERS_FETCHED_PREFETCH`` 
-
-This variable shows the number of buffers fetched from disk aggressively.
-
-.. _Tokudb_BUFFERS_FETCHED_PREFETCH_BYTES:
-
-.. rubric:: ``Tokudb_BUFFERS_FETCHED_PREFETCH_BYTES`` 
-
-This variable shows the number of buffer bytes fetched from disk by a prefetch
-thread.
-
-.. _Tokudb_BUFFERS_FETCHED_PREFETCH_SECONDS:
-
-.. rubric:: ``Tokudb_BUFFERS_FETCHED_PREFETCH_SECONDS`` 
-
-This variable shows the number of seconds waiting for I/O when fetching buffers
-from disk by a prefetch thread.
-
-.. _Tokudb_BUFFERS_FETCHED_FOR_WRITE:
-
-.. rubric:: ``Tokudb_BUFFERS_FETCHED_FOR_WRITE`` 
-
-This variable shows the number of buffers fetched from disk for writes.
-
-.. _Tokudb_BUFFERS_FETCHED_FOR_WRITE_BYTES:
-
-.. rubric:: ``Tokudb_BUFFERS_FETCHED_FOR_WRITE_BYTES`` 
-
-This variable shows the number of buffer bytes fetched from disk for writes.
-
-.. _Tokudb_BUFFERS_FETCHED_FOR_WRITE_SECONDS:
-
-.. rubric:: ``Tokudb_BUFFERS_FETCHED_FOR_WRITE_SECONDS`` 
-
-This variable shows the number of seconds waiting for I/O when fetching buffers
-from disk for writes.
-
-.. _Tokudb_LEAF_COMPRESSION_TO_MEMORY_SECONDS:
-
-.. rubric:: ``Tokudb_LEAF_COMPRESSION_TO_MEMORY_SECONDS`` 
-
-This variable shows the total time, in seconds, spent compressing leaf nodes.
-
-.. _Tokudb_LEAF_SERIALIZATION_TO_MEMORY_SECONDS:
-
-.. rubric:: ``Tokudb_LEAF_SERIALIZATION_TO_MEMORY_SECONDS`` 
-
-This variable shows the total time, in seconds, spent serializing leaf nodes.
-
-.. _Tokudb_LEAF_DECOMPRESSION_TO_MEMORY_SECONDS:
-
-.. rubric:: ``Tokudb_LEAF_DECOMPRESSION_TO_MEMORY_SECONDS`` 
-
-This variable shows the total time, in seconds, spent decompressing leaf nodes.
-
-.. _Tokudb_LEAF_DESERIALIZATION_TO_MEMORY_SECONDS:
-
-.. rubric:: ``Tokudb_LEAF_DESERIALIZATION_TO_MEMORY_SECONDS`` 
-
-This variable shows the total time, in seconds, spent deserializing leaf nodes.
-
-.. _Tokudb_NONLEAF_COMPRESSION_TO_MEMORY_SECONDS:
-
-.. rubric:: ``Tokudb_NONLEAF_COMPRESSION_TO_MEMORY_SECONDS`` 
-
-This variable shows the total time, in seconds, spent compressing non leaf
-nodes.
-
-.. _Tokudb_NONLEAF_SERIALIZATION_TO_MEMORY_SECONDS:
-
-.. rubric:: ``Tokudb_NONLEAF_SERIALIZATION_TO_MEMORY_SECONDS`` 
-
-This variable shows the total time, in seconds, spent serializing non leaf
-nodes.
-
-.. _Tokudb_NONLEAF_DECOMPRESSION_TO_MEMORY_SECONDS:
-
-.. rubric:: ``Tokudb_NONLEAF_DECOMPRESSION_TO_MEMORY_SECONDS`` 
-
-This variable shows the total time, in seconds, spent decompressing non leaf
-nodes.
-
-.. _Tokudb_NONLEAF_DESERIALIZATION_TO_MEMORY_SECONDS:
-
-.. rubric:: ``Tokudb_NONLEAF_DESERIALIZATION_TO_MEMORY_SECONDS`` 
-
-This variable shows the total time, in seconds, spent deserializing non leaf
-nodes.
-
-.. _Tokudb_PROMOTION_ROOTS_SPLIT:
-
-.. rubric:: ``Tokudb_PROMOTION_ROOTS_SPLIT`` 
-
-This variable shows the number of times the root split during promotion.
-
-.. _Tokudb_PROMOTION_LEAF_ROOTS_INJECTED_INTO:
-
-.. rubric:: ``Tokudb_PROMOTION_LEAF_ROOTS_INJECTED_INTO`` 
-
-This variable shows the number of times a message stopped at a root with
-height ``0``.
-
-.. _Tokudb_PROMOTION_H1_ROOTS_INJECTED_INTO:
-
-.. rubric:: ``Tokudb_PROMOTION_H1_ROOTS_INJECTED_INTO`` 
-
-This variable shows the number of times a message stopped at a root with
-height ``1``.
-
-.. _Tokudb_PROMOTION_INJECTIONS_AT_DEPTH_0:
-
-.. rubric:: ``Tokudb_PROMOTION_INJECTIONS_AT_DEPTH_0`` 
-
-This variable shows the number of times a message stopped at depth ``0``.
-
-.. _Tokudb_PROMOTION_INJECTIONS_AT_DEPTH_1:
-
-.. rubric:: ``Tokudb_PROMOTION_INJECTIONS_AT_DEPTH_1`` 
-
-This variable shows the number of times a message stopped at depth ``1``.
-
-.. _Tokudb_PROMOTION_INJECTIONS_AT_DEPTH_2:
-
-.. rubric:: ``Tokudb_PROMOTION_INJECTIONS_AT_DEPTH_2`` 
-
-This variable shows the number of times a message stopped at depth ``2``.
-
-.. _Tokudb_PROMOTION_INJECTIONS_AT_DEPTH_3:
-
-.. rubric:: ``Tokudb_PROMOTION_INJECTIONS_AT_DEPTH_3`` 
-
-This variable shows the number of times a message stopped at depth ``3``.
-
-.. _Tokudb_PROMOTION_INJECTIONS_LOWER_THAN_DEPTH_3:
-
-.. rubric:: ``Tokudb_PROMOTION_INJECTIONS_LOWER_THAN_DEPTH_3`` 
-
-This variable shows the number of times a message was promoted past depth
-``3``.
-
-.. _Tokudb_PROMOTION_STOPPED_NONEMPTY_BUFFER:
-
-.. rubric:: ``Tokudb_PROMOTION_STOPPED_NONEMPTY_BUFFER`` 
-
-This variable shows the number of times a message stopped because it reached
-a nonempty buffer.
-
-.. _Tokudb_PROMOTION_STOPPED_AT_HEIGHT_1:
-
-.. rubric:: ``Tokudb_PROMOTION_STOPPED_AT_HEIGHT_1`` 
-
-This variable shows the number of times a message stopped because it had
-reached height ``1``.
-
-.. _Tokudb_PROMOTION_STOPPED_CHILD_LOCKED_OR_NOT_IN_MEMORY:
-
-.. rubric:: ``Tokudb_PROMOTION_STOPPED_CHILD_LOCKED_OR_NOT_IN_MEMORY`` 
-
-This variable shows the number of times a message stopped because it could not
-cheaply get access to a child.
-
-.. _Tokudb_PROMOTION_STOPPED_CHILD_NOT_FULLY_IN_MEMORY:
-
-.. rubric:: ``Tokudb_PROMOTION_STOPPED_CHILD_NOT_FULLY_IN_MEMORY`` 
-
-This variable shows the number of times a message stopped because it could not
-cheaply get access to a child.
-
-.. _Tokudb_PROMOTION_STOPPED_AFTER_LOCKING_CHILD:
-
-.. rubric:: ``Tokudb_PROMOTION_STOPPED_AFTER_LOCKING_CHILD`` 
-
-This variable shows the number of times a message stopped before a child which
-had been locked.
-
-.. _Tokudb_BASEMENT_DESERIALIZATION_FIXED_KEY:
-
-.. rubric:: ``Tokudb_BASEMENT_DESERIALIZATION_FIXED_KEY`` 
-
-This variable shows the number of basement nodes deserialized where all keys
-had the same size, leaving the basement in a format that is optimal for
-in-memory workloads.
-
-.. _Tokudb_BASEMENT_DESERIALIZATION_VARIABLE_KEY:
-
-.. rubric:: ``Tokudb_BASEMENT_DESERIALIZATION_VARIABLE_KEY`` 
-
-This variable shows the number of basement nodes deserialized where all keys
-did not have the same size, and thus ineligible for an in-memory optimization.
-
-.. _Tokudb_PRO_RIGHTMOST_LEAF_SHORTCUT_SUCCESS:
-
-.. rubric:: ``Tokudb_PRO_RIGHTMOST_LEAF_SHORTCUT_SUCCESS`` 
-
-This variable shows the number of times a message injection detected a series
-of sequential inserts to the rightmost side of the tree and successfully
-applied an insert message directly to the rightmost leaf node. This is a not a
-useful value for a regular user to use for any purpose.
-
-.. _Tokudb_PRO_RIGHTMOST_LEAF_SHORTCUT_FAIL_POS:
-
-.. rubric:: ``Tokudb_PRO_RIGHTMOST_LEAF_SHORTCUT_FAIL_POS`` 
-
-This variable shows the number of times a message injection detected a series
-of sequential inserts to the rightmost side of the tree and was unable to
-follow the pattern of directly applying an insert message directly to the
-rightmost leaf node because the key does not continue the sequence. This is a
-not a useful value for a regular user to use for any purpose.
-
-.. _Tokudb_RIGHTMOST_LEAF_SHORTCUT_FAIL_REACTIVE:
-
-.. rubric:: ``Tokudb_RIGHTMOST_LEAF_SHORTCUT_FAIL_REACTIVE`` 
-
-This variable shows the number of times a message injection detected a series
-of sequential inserts to the rightmost side of the tree and was unable to
-follow the pattern of directly applying an insert message directly to the
-rightmost leaf node because the leaf is full. This is a not a useful value for
-a regular user to use for any purpose.
-
-.. _Tokudb_CURSOR_SKIP_DELETED_LEAF_ENTRY:
-
-.. rubric:: ``Tokudb_CURSOR_SKIP_DELETED_LEAF_ENTRY`` 
-
-This variable shows the number of leaf entries skipped during search/scan
-because the result of message application and reconciliation of the leaf entry
-MVCC stack reveals that the leaf entry is ``deleted`` in the current
-transactions view. It is a good indicator that there might be excessive garbage
-in a tree if a range scan seems to take too long.
-
-.. _Tokudb_FLUSHER_CLEANER_TOTAL_NODES:
-
-.. rubric:: ``Tokudb_FLUSHER_CLEANER_TOTAL_NODES`` 
-
-This variable shows the total number of nodes potentially flushed by flusher or
-cleaner threads. This is a not a useful value for a regular user to use for any
-purpose.
-
-.. _Tokudb_FLUSHER_CLEANER_H1_NODES:
-
-.. rubric:: ``Tokudb_FLUSHER_CLEANER_H1_NODES`` 
-
-This variable shows the number of height ``1`` nodes that had messages flushed
-by flusher or cleaner threads, i.e., internal nodes immediately above leaf
-nodes. This is a not a useful value for a regular user to use for any purpose.
-
-.. _Tokudb_FLUSHER_CLEANER_HGT1_NODES:
-
-.. rubric:: ``Tokudb_FLUSHER_CLEANER_HGT1_NODES`` 
-
-This variable shows the number of nodes with height greater than ``1`` that had
-messages flushed by flusher or cleaner threads. This is a not a useful value
-for a regular user to use for any purpose.
-
-.. _Tokudb_FLUSHER_CLEANER_EMPTY_NODES:
-
-.. rubric:: ``Tokudb_FLUSHER_CLEANER_EMPTY_NODES`` 
-
-This variable shows the number of nodes cleaned by flusher or cleaner threads
-which had empty message buffers. This is a not a useful value for a regular
-user to use for any purpose.
-
-.. _Tokudb_FLUSHER_CLEANER_NODES_DIRTIED:
-
-.. rubric:: ``Tokudb_FLUSHER_CLEANER_NODES_DIRTIED`` 
-
-This variable shows the number of nodes dirtied by flusher or cleaner threads
-as a result of flushing messages downward. This is a not a useful value for a
-regular user to use for any purpose.
-
-.. _Tokudb_FLUSHER_CLEANER_MAX_BUFFER_SIZE:
-
-.. rubric:: ``Tokudb_FLUSHER_CLEANER_MAX_BUFFER_SIZE`` 
-
-This variable shows the maximum bytes in a message buffer flushed by flusher or
-cleaner threads. This is a not a useful value for a regular user to use for any
-purpose.
-
-.. _Tokudb_FLUSHER_CLEANER_MIN_BUFFER_SIZE:
-
-.. rubric:: ``Tokudb_FLUSHER_CLEANER_MIN_BUFFER_SIZE`` 
-
-This variable shows the minimum bytes in a message buffer flushed by flusher or
-cleaner threads. This is a not a useful value for a regular user to use for any
-purpose.
-
-.. _Tokudb_FLUSHER_CLEANER_TOTAL_BUFFER_SIZE:
-
-.. rubric:: ``Tokudb_FLUSHER_CLEANER_TOTAL_BUFFER_SIZE`` 
-
-This variable shows the total bytes in buffers flushed by flusher and cleaner
-threads. This is a not a useful value for a regular user to use for any purpose.
-
-.. _Tokudb_FLUSHER_CLEANER_MAX_BUFFER_WORKDONE:
-
-.. rubric:: ``Tokudb_FLUSHER_CLEANER_MAX_BUFFER_WORKDONE`` 
-
-This variable shows the maximum bytes worth of work done in a message buffer
-flushed by flusher or cleaner threads. This is a not a useful value for a
-regular user to use for any purpose.
-
-.. _Tokudb_FLUSHER_CLEANER_MIN_BUFFER_WORKDONE:
-
-.. rubric:: ``Tokudb_FLUSHER_CLEANER_MIN_BUFFER_WORKDONE`` 
-
-This variable shows the minimum bytes worth of work done in a message buffer
-flushed by flusher or cleaner threads. This is a not a useful value for a
-regular user to use for any purpose.
-
-.. _Tokudb_FLUSHER_CLEANER_TOTAL_BUFFER_WORKDONE:
-
-.. rubric:: ``Tokudb_FLUSHER_CLEANER_TOTAL_BUFFER_WORKDONE`` 
-
-This variable shows the total bytes worth of work done in buffers flushed by
-flusher or cleaner threads. This is a not a useful value for a regular user to
-use for any purpose.
-
-.. _Tokudb_FLUSHER_CLEANER_NUM_LEAF_MERGES_STARTED:
-
-.. rubric:: ``Tokudb_FLUSHER_CLEANER_NUM_LEAF_MERGES_STARTED`` 
-
-This variable shows the number of times flusher and cleaner threads tried to
-merge two leafs. This is a not a useful value for a regular user to use for any
-purpose.
-
-.. _Tokudb_FLUSHER_CLEANER_NUM_LEAF_MERGES_RUNNING:
-
-.. rubric:: ``Tokudb_FLUSHER_CLEANER_NUM_LEAF_MERGES_RUNNING`` 
-
-This variable shows the number of flusher and cleaner threads leaf merges in
-progress. This is a not a useful value for a regular user to use for any
-purpose.
-
-.. _Tokudb_FLUSHER_CLEANER_NUM_LEAF_MERGES_COMPLETED:
-
-.. rubric:: ``Tokudb_FLUSHER_CLEANER_NUM_LEAF_MERGES_COMPLETED`` 
-
-This variable shows the number of successful flusher and cleaner threads leaf
-merges. This is a not a useful value for a regular user to use for any purpose.
-
-.. _Tokudb_FLUSHER_CLEANER_NUM_DIRTIED_FOR_LEAF_MERGE:
-
-.. rubric:: ``Tokudb_FLUSHER_CLEANER_NUM_DIRTIED_FOR_LEAF_MERGE`` 
-
-This variable shows the number of nodes dirtied by flusher or cleaner threads
-performing leaf node merges. This is a not a useful value for a regular user to
-use for any purpose.
-
-.. _Tokudb_FLUSHER_FLUSH_TOTAL:
-
-.. rubric:: ``Tokudb_FLUSHER_FLUSH_TOTAL`` 
-
-This variable shows the total number of flushes done by flusher threads or
-cleaner threads. This is a not a useful value for a regular user to use for any
-purpose.
-
-.. _Tokudb_FLUSHER_FLUSH_IN_MEMORY:
-
-.. rubric:: ``Tokudb_FLUSHER_FLUSH_IN_MEMORY`` 
-
-This variable shows the number of in memory flushes (required no disk reads) by
-flusher or cleaner threads. This is a not a useful value for a regular user to
-use for any purpose.
-
-.. _Tokudb_FLUSHER_FLUSH_NEEDED_IO:
-
-.. rubric:: ``Tokudb_FLUSHER_FLUSH_NEEDED_IO`` 
-
-This variable shows the number of flushes that read something off disk by
-flusher or cleaner threads. This is a not a useful value for a regular user to
-use for any purpose.
-
-.. _Tokudb_FLUSHER_FLUSH_CASCADES:
-
-.. rubric:: ``Tokudb_FLUSHER_FLUSH_CASCADES`` 
-
-This variable shows the number of flushes that triggered a flush in child node
-by flusher or cleaner threads. This is a not a useful value for a regular user
-to use for any purpose.
-
-.. _Tokudb_FLUSHER_FLUSH_CASCADES_1:
-
-.. rubric:: ``Tokudb_FLUSHER_FLUSH_CASCADES_1`` 
-
-This variable shows the number of flushes that triggered one cascading flush by
-flusher or cleaner threads. This is a not a useful value for a regular user to
-use for any purpose.
-
-.. _Tokudb_FLUSHER_FLUSH_CASCADES_2:
-
-.. rubric:: ``Tokudb_FLUSHER_FLUSH_CASCADES_2`` 
-
-This variable shows the number of flushes that triggered two cascading flushes
-by flusher or cleaner threads. This is a not a useful value for a regular user
-to use for any purpose.
-
-.. _Tokudb_FLUSHER_FLUSH_CASCADES_3:
-
-.. rubric:: ``Tokudb_FLUSHER_FLUSH_CASCADES_3`` 
-
-This variable shows the number of flushes that triggered three cascading
-flushes by flusher or cleaner threads. This is a not a useful value for a
-regular user to use for any purpose.
-
-.. _Tokudb_FLUSHER_FLUSH_CASCADES_4:
-
-.. rubric:: ``Tokudb_FLUSHER_FLUSH_CASCADES_4`` 
-
-This variable shows the number of flushes that triggered four cascading
-flushes by flusher or cleaner threads. This is a not a useful value for a
-regular user to use for any purpose.
-
-.. _Tokudb_FLUSHER_FLUSH_CASCADES_5:
-
-.. rubric:: ``Tokudb_FLUSHER_FLUSH_CASCADES_5`` 
-
-This variable shows the number of flushes that triggered five cascading
-flushes by flusher or cleaner threads. This is a not a useful value for a
-regular user to use for any purpose.
-
-.. _Tokudb_FLUSHER_FLUSH_CASCADES_GT_5:
-
-.. rubric:: ``Tokudb_FLUSHER_FLUSH_CASCADES_GT_5`` 
-
-This variable shows the number of flushes that triggered more than five
-cascading flushes by flusher or cleaner threads. This is a not a useful value
-for a regular user to use for any purpose.
-
-.. _Tokudb_FLUSHER_SPLIT_LEAF:
-
-.. rubric:: ``Tokudb_FLUSHER_SPLIT_LEAF`` 
-
-This variable shows the total number of leaf node splits done by flusher
-threads or cleaner threads. This is a not a useful value for a regular user to
-use for any purpose.
-
-.. _Tokudb_FLUSHER_SPLIT_NONLEAF:
-
-.. rubric:: ``Tokudb_FLUSHER_SPLIT_NONLEAF`` 
-
-This variable shows the total number of non-leaf node splits done by flusher
-threads or cleaner threads. This is a not a useful value for a regular user to
-use for any purpose.
-
-.. _Tokudb_FLUSHER_MERGE_LEAF:
-
-.. rubric:: ``Tokudb_FLUSHER_MERGE_LEAF`` 
-
-This variable shows the total number of leaf node merges done by flusher
-threads or cleaner threads. This is a not a useful value for a regular user to
-use for any purpose.
-
-.. _Tokudb_FLUSHER_MERGE_NONLEAF:
-
-.. rubric:: ``Tokudb_FLUSHER_MERGE_NONLEAF`` 
-
-This variable shows the total number of non-leaf node merges done by flusher
-threads or cleaner threads. This is a not a useful value for a regular user to
-use for any purpose.
-
-.. _Tokudb_FLUSHER_BALANCE_LEAF:
-
-.. rubric:: ``Tokudb_FLUSHER_BALANCE_LEAF`` 
-
-This variable shows the number of times two adjacent leaf nodes were rebalanced
-or had their content redistributed evenly by flusher or cleaner threads. This
-is a not a useful value for a regular user to use for any purpose.
-
-.. _Tokudb_HOT_NUM_STARTED:
-
-.. rubric:: ``Tokudb_HOT_NUM_STARTED`` 
-
-This variable shows the number of hot operations started (``OPTIMIZE TABLE``).
-This is a not a useful value for a regular user to use for any purpose.
-
-.. _Tokudb_HOT_NUM_COMPLETED:
-
-.. rubric:: ``Tokudb_HOT_NUM_COMPLETED`` 
-
-This variable shows the number of hot operations completed (``OPTIMIZE TABLE``).
-This is a not a useful value for a regular user to use for any purpose.
-
-.. _Tokudb_HOT_NUM_ABORTED:
-
-.. rubric:: ``Tokudb_HOT_NUM_ABORTED`` 
-
-This variable shows the number of hot operations aborted (``OPTIMIZE TABLE``).
-This is a not a useful value for a regular user to use for any purpose.
-
-.. _Tokudb_HOT_MAX_ROOT_FLUSH_COUNT:
-
-.. rubric:: ``Tokudb_HOT_MAX_ROOT_FLUSH_COUNT`` 
-
-This variable shows the maximum number of flushes from root ever required to
-optimize trees. This is a not a useful value for a regular user to use for any
-purpose.
-
-.. _Tokudb_TXN_BEGIN:
-
-.. rubric:: ``Tokudb_TXN_BEGIN`` 
-
-This variable shows the number of transactions that have been started.
-
-.. _Tokudb_TXN_BEGIN_READ_ONLY:
-
-.. rubric:: ``Tokudb_TXN_BEGIN_READ_ONLY`` 
-
-This variable shows the number of read-only transactions started.
-
-.. _Tokudb_TXN_COMMITS:
-
-.. rubric:: ``Tokudb_TXN_COMMITS`` 
-
-This variable shows the total number of transactions that have been committed.
-
-.. _Tokudb_TXN_ABORTS:
-
-.. rubric:: ``Tokudb_TXN_ABORTS`` 
-
-This variable shows the total number of transactions that have been aborted.
-
-.. _Tokudb_LOGGER_NEXT_LSN:
-
-.. rubric:: ``Tokudb_LOGGER_NEXT_LSN`` 
-
-This variable shows the recovery logger next LSN. This is a not a useful value
-for a regular user to use for any purpose.
-
-.. _Tokudb_LOGGER_WRITES:
-
-.. rubric:: ``Tokudb_LOGGER_WRITES`` 
-
-This variable shows the number of times the logger has written to disk.
-
-.. _Tokudb_LOGGER_WRITES_BYTES:
-
-.. rubric:: ``Tokudb_LOGGER_WRITES_BYTES`` 
-
-This variable shows the number of bytes the logger has written to disk.
-
-.. _Tokudb_LOGGER_WRITES_UNCOMPRESSED_BYTES:
-
-.. rubric:: ``Tokudb_LOGGER_WRITES_UNCOMPRESSED_BYTES`` 
-
-This variable shows the number of uncompressed bytes the logger has written to
-disk.
-
-.. _Tokudb_LOGGER_WRITES_SECONDS:
-
-.. rubric:: ``Tokudb_LOGGER_WRITES_SECONDS`` 
-
-This variable shows the number of seconds waiting for IO when writing logs to
-disk.
-
-.. _Tokudb_LOGGER_WAIT_LONG:
-
-.. rubric:: ``Tokudb_LOGGER_WAIT_LONG`` 
-
-This variable shows the number of times a logger write operation required 100ms
-or more.
-
-.. _Tokudb_LOADER_NUM_CREATED:
-
-.. rubric:: ``Tokudb_LOADER_NUM_CREATED`` 
-
-This variable shows the number of times one of our internal objects, a loader,
-has been created.
-
-.. _Tokudb_LOADER_NUM_CURRENT:
-
-.. rubric:: ``Tokudb_LOADER_NUM_CURRENT`` 
-
-This variable shows the number of loaders that currently exist.
-
-.. _Tokudb_LOADER_NUM_MAX:
-
-.. rubric:: ``Tokudb_LOADER_NUM_MAX`` 
-
-This variable shows the maximum number of loaders that ever existed
-simultaneously.
-
-.. _Tokudb_MEMORY_MALLOC_COUNT:
-
-.. rubric:: ``Tokudb_MEMORY_MALLOC_COUNT`` 
-
-This variable shows the number of ``malloc`` operations by PerconaFT.
-
-.. _Tokudb_MEMORY_FREE_COUNT:
-
-.. rubric:: ``Tokudb_MEMORY_FREE_COUNT`` 
-
-This variable shows the number of ``free`` operations by PerconaFT.
-
-.. _Tokudb_MEMORY_REALLOC_COUNT:
-
-.. rubric:: ``Tokudb_MEMORY_REALLOC_COUNT`` 
-
-This variable shows the number of ``realloc`` operations by PerconaFT.
-
-.. _Tokudb_MEMORY_MALLOC_FAIL:
-
-.. rubric:: ``Tokudb_MEMORY_MALLOC_FAIL`` 
-
-This variable shows the number of ``malloc`` operations that failed by
-PerconaFT.
-
-.. _Tokudb_MEMORY_REALLOC_FAIL:
-
-.. rubric:: ``Tokudb_MEMORY_REALLOC_FAIL`` 
-
-This variable shows the number of ``realloc`` operations that failed by
-PerconaFT.
-
-.. _Tokudb_MEMORY_REQUESTED:
-
-.. rubric:: ``Tokudb_MEMORY_REQUESTED`` 
-
-This variable shows the number of bytes requested by PerconaFT.
-
-.. _Tokudb_MEMORY_USED:
-
-.. rubric:: ``Tokudb_MEMORY_USED`` 
-
-This variable shows the number of bytes used (requested + overhead) by
-PerconaFT.
-
-.. _Tokudb_MEMORY_FREED:
-
-.. rubric:: ``Tokudb_MEMORY_FREED`` 
-
-This variable shows the number of bytes freed by PerconaFT.
-
-.. _Tokudb_MEMORY_MAX_REQUESTED_SIZE:
-
-.. rubric:: ``Tokudb_MEMORY_MAX_REQUESTED_SIZE`` 
-
-This variable shows the largest attempted allocation size by PerconaFT.
-
-.. _Tokudb_MEMORY_LAST_FAILED_SIZE:
-
-.. rubric:: ``Tokudb_MEMORY_LAST_FAILED_SIZE`` 
-
-This variable shows the size of the last failed allocation attempt by
-PerconaFT.
-
-.. _Tokudb_MEM_ESTIMATED_MAXIMUM_MEMORY_FOOTPRINT:
-
-.. rubric:: ``Tokudb_MEM_ESTIMATED_MAXIMUM_MEMORY_FOOTPRINT`` 
-
-This variable shows the maximum memory footprint of the storage engine, the
-max value of (used - freed).
-
-.. _Tokudb_MEMORY_MALLOCATOR_VERSION:
-
-.. rubric:: ``Tokudb_MEMORY_MALLOCATOR_VERSION`` 
-
-This variable shows the version of the memory allocator library detected by
-PerconaFT.
-
-.. _Tokudb_MEMORY_MMAP_THRESHOLD:
-
-.. rubric:: ``Tokudb_MEMORY_MMAP_THRESHOLD`` 
-
-This variable shows the ``mmap`` threshold in PerconaFT, anything larger than
-this gets ``mmap'ed``.
-
-.. _Tokudb_FILESYSTEM_THREADS_BLOCKED_BY_FULL_DISK:
-
-.. rubric:: ``Tokudb_FILESYSTEM_THREADS_BLOCKED_BY_FULL_DISK`` 
-
-This variable shows the number of threads that are currently blocked because
-they are attempting to write to a full disk. This is normally zero. If this
-value is non-zero, then a warning will appear in the ``disk free space`` field.
-
-.. _Tokudb_FILESYSTEM_FSYNC_TIME:
-
-.. rubric:: ``Tokudb_FILESYSTEM_FSYNC_TIME`` 
-
-This variable shows the total time, in microseconds, used to ``fsync`` to disk.
-
-.. _Tokudb_FILESYSTEM_FSYNC_NUM:
-
-.. rubric:: ``Tokudb_FILESYSTEM_FSYNC_NUM`` 
-
-This variable shows the total number of times the database has flushed the
-operating system's file buffers to disk.
-
-.. _Tokudb_FILESYSTEM_LONG_FSYNC_TIME:
-
-.. rubric:: ``Tokudb_FILESYSTEM_LONG_FSYNC_TIME`` 
-
-This variable shows the total time, in microseconds, used to ``fsync`` to dis
-k when the operation required more than one second.
-
-.. _Tokudb_FILESYSTEM_LONG_FSYNC_NUM:
-
-.. rubric:: ``Tokudb_FILESYSTEM_LONG_FSYNC_NUM`` 
-
-This variable shows the total number of times the database has flushed the
-operating system's file buffers to disk and this operation required more than
-one second.
diff --git a/doc/source/tokudb/tokudb_troubleshooting.rst b/doc/source/tokudb/tokudb_troubleshooting.rst
deleted file mode 100644
index 99a7023002e6..000000000000
--- a/doc/source/tokudb/tokudb_troubleshooting.rst
+++ /dev/null
@@ -1,1514 +0,0 @@
-.. _tokudb_troubleshooting:
-
-======================
-TokuDB Troubleshooting
-======================
-
-.. Important:: 
-
-   Starting with :ref:`8.0.28-19`, the TokuDB storage engine is no longer supported. We have removed the storage engine from the installation packages and disabled the storage engine in our binary builds.
-
-   Starting with :ref:`8.0.26-16`, the binary builds and packages include but disable the TokuDB storage engine plugins. The ``tokudb_enabled`` option and the ``tokudb_backup_enabled`` option control the state of the plugins and have a default setting of ``FALSE``. The result of attempting to load the plugins are the plugins fail to initialize and print a deprecation message.
-
-   We recommend :ref:`migrate-myrocks`. To enable the plugins to migrate to another storage engine, set the ``tokudb_enabled`` and ``tokudb_backup_enabled`` options to ``TRUE`` in your ``my.cnf`` file and restart your server instance. Then, you can load the plugins.
-
-   The TokuDB Storage Engine was `declared as deprecated <https://www.percona.com/doc/percona-server/8.0/release-notes/Percona-Server-8.0.13-3.html>`__ in Percona Server for MySQL 8.0. For more information, see the Percona blog post: `Heads-Up: TokuDB Support Changes and Future Removal from Percona Server for MySQL 8.0 <https://www.percona.com/blog/2021/05/21/tokudb-support-changes-and-future-removal-from-percona-server-for-mysql-8-0/>`__.
-
-.. contents::
-   :local:
-   :depth: 1
-
-.. _tokudb_known_issues:
-
-Known Issues
-===============================================================================
-
-**Replication and binary logging**: *TokuDB* supports binary logging and replication, with one restriction. *TokuDB* does not implement a lock on the auto-increment function, so concurrent insert statements with one or more of the statements inserting multiple rows may result in a non-deterministic interleaving of the auto-increment values. When running replication with these concurrent inserts, the auto-increment values on the replica table may not match the auto-increment values on the source table. Note that this is only an issue with Statement Based Replication (SBR), and not Row Based Replication (RBR).
-
-For more information about auto-increment and replication, see the *MySQL*
-Reference Manual: `AUTO_INCREMENT handling in InnoDB
-<http://dev.mysql.com/doc/refman/8.0/en/innodb-auto-increment-handling.html>`_.
-
-In addition, when using the ``REPLACE INTO`` or ``INSERT IGNORE`` on tables with no secondary indexes or tables where secondary indexes are subsets of the primary, the session variable :ref:`tokudb_pk_insert_mode` controls whether row based replication will work.
-
-**Uninformative error message**: The ``LOAD DATA INFILE`` command can sometimes
- produce ``ERROR 1030 (HY000): Got error 1 from storage engine``. The message
- should say that the error is caused by insufficient disk space for the
- temporary files created by the loader.
-
-**Transparent Huge Pages**: *TokuDB* will refuse to start if transparent huge
- pages are enabled. Transparent huge page support can be disabled by issuing the
- following as root:
-
-.. code-block:: console
-
-   # echo never > /sys/kernel/mm/redhat_transparent_hugepage/enabled
-
-.. note::
-
-   The previous command needs to be executed after every reboot, because it
-   defaults to ``always``.
-
-**XA behavior vs. InnoDB**: *InnoDB* forces a deadlocked XA transaction to
- abort, *TokuDB* does not.
-
-**Disabling the unique checks**: For tables with unique keys, every insertion
-into the table causes a lookup by key followed by an insertion, if the key is
-not in the table. This greatly limits insertion performance. If one knows by
-design that the rows being inserted into the table have unique keys, then one
-can disable the key lookup prior to insertion.
-
-If your primary key is an auto-increment key, and none of your secondary keys
-are declared to be unique, then setting ``unique_checks=OFF`` will provide
-limited performance gains. On the other hand, if your primary key has a lot of
-entropy (it looks random), or your secondary keys are declared unique and have
-a lot of entropy, then disabling unique checks can provide a significant
-performance boost.
-
-If :ref:`unique_checks` is disabled when the primary key is not unique,
-secondary indexes may become corrupted. In this case, the indexes should be
-dropped and rebuilt. This behavior differs from that of *InnoDB*, in which
-uniqueness is always checked on the primary key, and setting
-:ref:`unique_checks` to off turns off uniqueness checking on secondary
-indexes only. Turning off uniqueness checking on the primary key can provide
-large performance boosts, but it should only be done when the primary key is
-known to be unique.
-
-**Group Replication**: *TokuDB* storage engine doesn't support `Group Replication
-<https://dev.mysql.com/doc/refman/8.0/en/group-replication.html>`_.
-
-As of 8.0.17, InnoDB supports `multi-valued indexes <https://dev.mysql.com/doc/refman/8.0/en/create-index.html#create-index-multi-valued>`__. TokuDB does not support this feature.
-
-As of 8.0.17, InnoDB supports the `Clone Plugin <https://dev.mysql.com/doc/refman/8.0/en/clone-plugin.html>`__ and the Clone Plugin API. TokuDB tables do not support either of these features.
-
-.. _tokudb_lock_visualization:
-
-Lock Visualization in TokuDB
-================================================================================
-
-*TokuDB* uses key range locks to implement serializable transactions, which are
-acquired as the transaction progresses. The locks are released when the
-transaction commits or aborts (this implements two phase locking).
-
-*TokuDB* stores these locks in a data structure called the lock tree. The lock
-tree stores the set of range locks granted to each transaction. In addition, the
-lock tree stores the set of locks that are not granted due to a conflict with
-locks granted to some other transaction. When these other transactions are
-retired, these pending lock requests are retried. If a pending lock request is
-not granted before the lock timer expires, then the lock request is aborted.
-
-Lock visualization in *TokuDB* exposes the state of the lock tree with tables in
-the information schema. We also provide a mechanism that may be used by a
-database client to retrieve details about lock conflicts that it encountered
-while executing a transaction.
-
-The ``TOKUDB_TRX`` table
---------------------------------------------------------------------------------
-
-The :ref:`TOKUDB_TRX` table in the ``INFORMATION_SCHEMA`` maps *TokuDB*
-transaction identifiers to *MySQL* client identifiers. This mapping allows one
-to associate a *TokuDB* transaction with a *MySQL* client operation.
-
-The following query returns the *MySQL* clients that have a live *TokuDB*
-transaction:
-
-.. code-block:: mysql
-
-   SELECT * FROM INFORMATION_SCHEMA.TOKUDB_TRX,
-   INFORMATION_SCHEMA.PROCESSLIST
-   WHERE trx_mysql_thread_id = id;
-
-The ``TOKUDB_LOCKS`` table
---------------------------------------------------------------------------------
-
-The :ref:`tokudb_locks` table in the information schema contains the set of
-locks granted to *TokuDB* transactions.
-
-The following query returns all of the locks granted to some *TokuDB*
-transaction:
-
-.. code-block:: mysql
-
-   SELECT * FROM INFORMATION_SCHEMA.TOKUDB_LOCKS;
-
-The following query returns the locks granted to some *MySQL* client:
-
-.. code-block:: mysql
-
-   SELECT id FROM INFORMATION_SCHEMA.TOKUDB_LOCKS,
-   INFORMATION_SCHEMA.PROCESSLIST
-   WHERE locks_mysql_thread_id = id;
-
-The ``TOKUDB_LOCK_WAITS`` table
---------------------------------------------------------------------------------
-
-The :ref:`tokudb_lock_waits` table in the information schema contains the set
-of lock requests that are not granted due to a lock conflict with some other
-transaction.
-
-The following query returns the locks that are waiting to be granted due to a
-lock conflict with some other transaction:
-
-.. code-block:: mysql
-
-   SELECT * FROM INFORMATION_SCHEMA.TOKUDB_LOCK_WAITS;
-
-Supporting explicit DEFAULT value expressions as of 8.0.13-3
---------------------------------------------------------------------------------
-
-TokuDB does not support `explicit DEFAULT value expressions <https://dev.mysql.com/doc/refman/8.0/en/data-type-defaults.html>`__ as of verion 8.0.13-3.
-
-
-The :ref:`tokudb_lock_timeout_debug` session variable
---------------------------------------------------------------------------------
-
-The :ref:`tokudb_lock_timeout_debug` session variable controls how lock
-timeouts and lock deadlocks seen by the database client are reported.
-
-The following values are available:
-
-:0: No lock timeouts or lock deadlocks are reported.
-
-:1: A JSON document that describes the lock conflict is stored in the
-    :ref:`tokudb_last_lock_timeout` session variable
-
-:2: A JSON document that describes the lock conflict is printed to the *MySQL*
-    error log.
-
-    *Supported since 7.5.5*: In addition to the JSON document describing the lock conflict, the following lines are printed to the MySQL error log:
-
-    * A line containing the blocked thread id and blocked SQL
-    * A line containing the blocking thread id and the blocking SQL.
-
-:3: A JSON document that describes the lock conflict is stored in the :ref:`tokudb_last_lock_timeout` session variable and is printed to the *MySQL* error log.
-
-    *Supported since 7.5.5*: In addition to the JSON document describing the lock conflict, the following lines are printed to the *MySQL* error log:
-
-    * A line containing the blocked thread id and blocked SQL
-    * A line containing the blocking thread id and the blocking SQL.
-
-The :ref:`tokudb_last_lock_timeout` session variable
---------------------------------------------------------------------------------
-
-The :ref:`tokudb_last_lock_timeout` session variable contains a JSON
-document that describes the last lock conflict seen by the current *MySQL*
-client. It gets set when a blocked lock request times out or a lock deadlock is
-detected. The :ref:`tokudb_lock_timeout_debug` session variable should have
-bit ``0`` set (decimal ``1``).
-
-.. rubric:: Example
-
-Suppose that we create a table with a single column that is the primary key.
-
-.. code-block:: mysql
-
- mysql> SHOW CREATE TABLE table;
-
- Create Table: CREATE TABLE ‘table‘ (
- ‘id‘ int(11) NOT NULL,
- PRIMARY KEY (‘id‘)) ENGINE=TokuDB DEFAULT CHARSET=latin1
-
-Suppose that we have 2 *MySQL* clients with ID's 1 and 2 respectively. Suppose
-that *MySQL* client 1 inserts some values into ``table``. *TokuDB* transaction
-51 is created for the insert statement. Since autocommit is disabled,
-transaction 51 is still live after the insert statement completes, and we can
-query the :ref:`tokudb_locks` table in information schema to see the locks
-that are held by the transaction.
-
-.. code-block:: mysql
-
-   mysql> SET AUTOCOMMIT=OFF;
-   mysql> INSERT INTO table VALUES (1),(10),(100);
-
-.. admonition:: Output
-
-   .. code-block:: mysql
-
-      Query OK, 3 rows affected (0.00 sec)
-      Records: 3  Duplicates: 0  Warnings: 0
-
-.. code-block:: mysql
-
-   mysql> SELECT * FROM INFORMATION_SCHEMA.TOKUDB_LOCKS;
-
-.. admonition:: Output
-
-   .. code-block:: mysql
-
-      +--------------+-----------------------+---------------+----------------+-----------------+--------------------+------------------+-----------------------------+
-      | locks_trx_id | locks_mysql_thread_id | locks_dname   | locks_key_left | locks_key_right | locks_table_schema | locks_table_name | locks_table_dictionary_name |
-      +--------------+-----------------------+---------------+----------------+-----------------+--------------------+------------------+-----------------------------+
-      |           51 |                     1 | ./test/t-main | 0001000000     | 0001000000      | test               | t                | main                        |
-      |           51 |                     1 | ./test/t-main | 000a000000     | 000a000000      | test               | t                | main                        |
-      |           51 |                     1 | ./test/t-main | 0064000000     | 0064000000      | test               | t                | main                        |
-      +--------------+-----------------------+---------------+----------------+-----------------+--------------------+------------------+-----------------------------+
-
-.. code-block:: mysql
-
-   mysql> SELECT * FROM INFORMATION_SCHEMA.TOKUDB_LOCK_WAITS;
-
-.. admonition:: Output
-
-   .. code-block:: mysql
-
-      Empty set (0.00 sec)
-
-The keys are currently hex dumped.
-
-Now we switch to the other *MySQL* client with ID 2.
-
-.. code-block:: mysql
-
-   mysql> INSERT INTO table VALUES (2),(20),(100);
-
-The insert gets blocked since there is a conflict on the primary key with value 100.
-
-The granted *TokuDB* locks are:
-
-.. code-block:: mysql
-
-   SELECT * FROM INFORMATION_SCHEMA.TOKUDB_LOCKS;
-
-.. admonition:: Output
-
-   .. code-block:: mysql
-
-      +--------------+-----------------------+---------------+----------------+-----------------+--------------------+------------------+-----------------------------+
-      | locks_trx_id | locks_mysql_thread_id | locks_dname   | locks_key_left | locks_key_right | locks_table_schema | locks_table_name | locks_table_dictionary_name |
-      +--------------+-----------------------+---------------+----------------+-----------------+--------------------+------------------+-----------------------------+
-      |           51 |                     1 | ./test/t-main | 0001000000     | 0001000000      | test               | t                | main                        |
-      |           51 |                     1 | ./test/t-main | 000a000000     | 000a000000      | test               | t                | main                        |
-      |           51 |                     1 | ./test/t-main | 0064000000     | 0064000000      | test               | t                | main                        |
-      |           51 |                     1 | ./test/t-main | 0002000000     | 0002000000      | test               | t                | main                        |
-      |           51 |                     1 | ./test/t-main | 0014000000     | 0014000000      | test               | t                | main                        |
-      +--------------+-----------------------+---------------+----------------+-----------------+--------------------+------------------+-----------------------------+
-
-The locks that are pending due to a conflict are:
-
-.. code-block:: mysql
-
-   SELECT * FROM INFORMATION_SCHEMA.TOKUDB_LOCK_WAITS;
-
-   +-------------------+-----------------+------------------+---------------------+----------------------+-----------------------+--------------------+------------------+-----------------------------+
-   | requesting_trx_id | blocking_trx_id | lock_waits_dname | lock_waits_key_left | lock_waits_key_right | lock_waits_start_time | locks_table_schema | locks_table_name | locks_table_dictionary_name |
-   +-------------------+-----------------+------------------+---------------------+----------------------+-----------------------+--------------------+------------------+-----------------------------+
-   |                62 |              51 | ./test/t-main    | 0064000000          | 0064000000           |         1380656990910 | test               | t                | main                        |
-   +-------------------+-----------------+------------------+---------------------+----------------------+-----------------------+--------------------+------------------+-----------------------------+
-
-Eventually, the lock for client 2 times out, and we can retrieve a JSON document that describes the conflict.
-
-.. admonition:: Error
-
-   ERROR 1205 (HY000): Lock wait timeout exceeded; try restarting transaction
-
-.. code-block:: mysql
-
-   SELECT @@TOKUDB_LAST_LOCK_TIMEOUT;
-
-.. admonition:: Output
-
-   .. code-block:: mysql
-
-      +---------------------------------------------------------------------------------------------------------------+
-      | @@tokudb_last_lock_timeout                                                                                    |
-      +---------------------------------------------------------------------------------------------------------------+
-      | "mysql_thread_id":2, "dbname":"./test/t-main", "requesting_txnid":62, "blocking_txnid":51, "key":"0064000000" |
-      +---------------------------------------------------------------------------------------------------------------+
-
-.. code-block:: mysql
-
-   ROLLBACK;
-
-Since transaction 62 was rolled back, all of the locks taken by it are released.
-
-.. code-block:: mysql
-
-   SELECT * FROM INFORMATION_SCHEMA.TOKUDB_LOCKS;
-
-.. admonition:: Output
-
-   .. code-block:: mysql
-
-      +--------------+-----------------------+---------------+----------------+-----------------+--------------------+------------------+-----------------------------+
-      | locks_trx_id | locks_mysql_thread_id | locks_dname   | locks_key_left | locks_key_right | locks_table_schema | locks_table_name | locks_table_dictionary_name |
-      +--------------+-----------------------+---------------+----------------+-----------------+--------------------+------------------+-----------------------------+
-      |           51 |                     1 | ./test/t-main | 0001000000     | 0001000000      | test               | t                | main                        |
-      |           51 |                     1 | ./test/t-main | 000a000000     | 000a000000      | test               | t                | main                        |
-      |           51 |                     1 | ./test/t-main | 0064000000     | 0064000000      | test               | t                | main                        |
-      |           51 |                     2 | ./test/t-main | 0002000000     | 0002000000      | test               | t                | main                        |
-      |           51 |                     2 | ./test/t-main | 0014000000     | 0014000000      | test               | t                | main                        |
-      +--------------+-----------------------+---------------+----------------+-----------------+--------------------+------------------+-----------------------------+
-
-Engine Status
---------------------------------------------------------------------------------
-
-Engine status provides details about the inner workings of *TokuDB* and can be
-useful in tuning your particular environment. The engine status can be
-determined by running the following command:  :mysql:`SHOW ENGINE tokudb STATUS;`
-
-The following is a reference of the table status statements:
-
-.. list-table::
-   :widths: 15 85
-   :header-rows: 1
-
-   * - Table Status
-     - Description
-
-   * - disk free space
-     - This is a gross estimate of how much of your file system is available.
-       Possible displays in this field are:
-
-       * More than twice the reserve ("more than 10 percent of total file system
-	 space")
-       * Less than twice the reserve
-       * Less than the reserve
-       * File system is completely full
-
-   * - time of environment creation
-     - This is the time when the *TokuDB* storage engine was first started up.
-       Normally, this is when ``mysqld`` was initially installed with *TokuDB*. If
-       the environment was upgraded from *TokuDB* 4.x (4.2.0 or later), then this
-       will be displayed as "Dec 31, 1969" on Linux hosts.
-
-   * - time of engine startup
-     - This is the time when the *TokuDB* storage engine started up. Normally, this
-       is when ``mysqld`` started.
-
-   * - time now
-     - Current date/time on server.
-
-   * - db opens
-     - This is the number of times an individual PerconaFT dictionary file was
-       opened. This is a not a useful value for a regular user to use for any purpose
-       due to layers of open/close caching on top.
-
-   * - db closes
-     - This is the number of times an individual PerconaFT dictionary file was
-       closed. This is a not a useful value for a regular user to use for any purpose
-       due to layers of open/close caching on top.
-
-   * - num open dbs now
-     - This is the number of currently open databases.
-
-   * - max open dbs
-     - This is the maximum number of concurrently opened databases.
-
-   * - period, in ms, that recovery log is automatically fsynced
-     - ``fsync()`` frequency in milliseconds.
-
-   * - dictionary inserts
-     - This is the total number of rows that have been inserted into all primary and
-       secondary indexes combined, when those inserts have been done with a separate
-       recovery log entry per index. For example, inserting a row into a table with
-       one primary and two secondary indexes will increase this count by three, if
-       the inserts were done with separate recovery log entries.
-
-   * - dictionary inserts fail
-     - This is the number of single-index insert operations that failed.
-
-   * - dictionary deletes
-     - This is the total number of rows that have been deleted from all primary and
-       secondary indexes combined, if those deletes have been done with a separate
-       recovery log entry per index.
-
-   * - dictionary deletes fail
-     - This is the number of single-index delete operations that failed.
-
-   * - dictionary updates
-     - This is the total number of rows that have been updated in all primary and
-       secondary indexes combined, if those updates have been done with a separate
-       recovery log entry per index.
-
-   * - dictionary updates fail
-     - This is the number of single-index update operations that failed.
-
-   * - dictionary broadcast updates
-     - This is the number of broadcast updates that have been successfully performed.
-       A broadcast update is an update that affects all rows in a dictionary.
-
-   * - dictionary broadcast updates fail
-     - This is the number of broadcast updates that have failed.
-
-   * - dictionary multi inserts
-     - This is the total number of rows that have been inserted into all primary and
-       secondary indexes combined, when those inserts have been done with a single
-       recovery log entry for the entire row. (For example, inserting a row into a
-       table with one primary and two secondary indexes will normally increase this
-       count by three).
-
-   * - dictionary multi inserts fail
-     - This is the number of multi-index insert operations that failed.
-
-   * - dictionary multi deletes
-     - This is the total number of rows that have been deleted from all primary and
-       secondary indexes combined, when those deletes have been done with a single
-       recovery log entry for the entire row.
-
-   * - dictionary multi deletes fail
-     - This is the number of multi-index delete operations that failed.
-
-   * - dictionary updates multi
-     - This is the total number of rows that have been updated in all primary and
-       secondary indexes combined, if those updates have been done with a single
-       recovery log entry for the entire row.
-
-   * - dictionary updates fail multi
-     - This is the number of multi-index update operations that failed.
-
-   * - le: max committed xr
-     - This is the maximum number of committed transaction records that were stored
-       on disk in a new or modified row.
-
-   * - le: max provisional xr
-     - This is the maximum number of provisional transaction records that were stored
-       on disk in a new or modified row.
-
-   * - le: expanded
-     - This is the number of times that an expanded memory mechanism was used to
-       store a new or modified row on disk.
-
-   * - le: max memsize
-     - This is the maximum number of bytes that were stored on disk as a new or
-       modified row. This is the maximum uncompressed size of any row stored in
-       *TokuDB* that was created or modified since the server started.
-
-   * - le: size of leafentries before garbage collection (during message application)
-     - Total number of bytes of leaf nodes data before performing garbage collection
-       for non-flush events.
-
-   * - le: size of leafentries after garbage collection (during message application)
-     - Total number of bytes of leaf nodes data after performing garbage collection
-       for non-flush events.
-
-   * - le: size of leafentries before garbage collection (outside message application)
-     - Total number of bytes of leaf nodes data before performing garbage collection
-       for flush events.
-
-   * - le: size of leafentries after garbage collection (outside message application)
-     - Total number of bytes of leaf nodes data after performing garbage collection
-       for flush events.
-
-   * - checkpoint: period
-     - This is the interval in seconds between the end of an automatic checkpoint and
-       the beginning of the next automatic checkpoint.
-
-   * - checkpoint: footprint
-     - Where the database is in the checkpoint process.
-
-   * - checkpoint: last checkpoint began
-     - This is the time the last checkpoint began. If a checkpoint is currently in
-       progress, then this time may be later than the time the last checkpoint
-       completed.
-
-       .. note::
-
-	  If no checkpoint has ever taken place, then this value will be ``Dec 31,
-	  1969`` on Linux hosts.
-
-   * - checkpoint: last complete checkpoint began
-     - This is the time the last complete checkpoint started. Any data that changed
-       after this time will not be captured in the checkpoint.
-
-   * - checkpoint: last complete checkpoint ended
-     - This is the time the last complete checkpoint ended.
-
-   * - checkpoint: time spent during checkpoint (begin and end phases)
-     - Time (in seconds) required to complete all checkpoints.
-
-   * - checkpoint: time spent during last checkpoint (begin and end phases)
-     - Time (in seconds) required to complete the last checkpoint.
-
-   * - checkpoint: last complete checkpoint LSN
-     - This is the Log Sequence Number of the last complete checkpoint.
-
-   * - checkpoint: checkpoints taken
-     - This is the number of complete checkpoints that have been taken.
-
-   * - checkpoint: checkpoints failed
-     - This is the number of checkpoints that have failed for any reason.
-
-   * - checkpoint: waiters now
-     - This is the current number of threads simultaneously waiting for the
-       checkpoint-safe lock to perform a checkpoint.
-
-   * - checkpoint: waiters max
-     - This is the maximum number of threads ever simultaneously waiting for the
-       checkpoint-safe lock to perform a checkpoint.
-
-   * - checkpoint: non-checkpoint client wait on mo lock
-     - The number of times a non-checkpoint client thread waited for the
-       multi-operation lock.
-
-   * - checkpoint: non-checkpoint client wait on cs lock
-     - The number of times a non-checkpoint client thread waited for the
-       checkpoint-safe lock.
-
-   * - checkpoint: checkpoint begin time
-     - Cumulative time (in microseconds) required to mark all dirty nodes as
-       pending a checkpoint.
-
-   * - checkpoint: long checkpoint begin time
-     - The total time, in microseconds, of long checkpoint begins. A long checkpoint
-       begin is one taking more than 1 second.
-
-   * - checkpoint: long checkpoint begin count
-     - The total number of times a checkpoint begin took more than 1 second.
-
-   * - checkpoint: checkpoint end time
-     - The time spent in checkpoint end operation in seconds.
-
-   * - checkpoint: long checkpoint end time
-     - The time spent in checkpoint end operation in seconds.
-
-   * - checkpoint: long checkpoint end count
-     - This is the count of end_checkpoint operations that exceeded 1 minute.
-
-   * - cachetable: miss
-     - This is a count of how many times the application was unable to access your
-       data in the internal cache.
-
-   * - cachetable: miss time
-     - This is the total time, in microseconds, of how long the database has had to
-       wait for a disk read to complete.
-
-   * - cachetable: prefetches
-     - This is the total number of times that a block of memory has been prefetched
-       into the database's cache. Data is prefetched when the database's algorithms
-       determine that a block of memory is likely to be accessed by the application.
-
-   * - cachetable: size current
-     - This shows how much of the uncompressed data, in bytes, is currently in the
-       database's internal cache.
-
-   * - cachetable: size limit
-     - This shows how much of the uncompressed data, in bytes, will fit in the
-       database's internal cache.
-
-   * - cachetable: size writing
-     - This is the number of bytes that are currently queued up to be written to
-       disk.
-
-   * - cachetable: size nonleaf
-     - This shows the amount of memory, in bytes, the current set of non-leaf nodes
-       occupy in the cache.
-
-   * - cachetable: size leaf
-     - This shows the amount of memory, in bytes, the current set of (decompressed)
-       leaf nodes occupy in the cache.
-
-   * - cachetable: size rollback
-     - This shows the rollback nodes size, in bytes, in the cache.
-
-   * - cachetable: size cachepressure
-     - This shows the number of bytes causing cache pressure (the sum of buffers and
-       work done counters), helps to understand if cleaner threads are keeping up
-       with workload. It should really be looked at as more of a value to use in a
-       ratio of cache pressure / cache table size. The closer that ratio evaluates to
-       1, the higher the cache pressure.
-
-   * - cachetable: size currently cloned data for checkpoint
-     - Amount of memory, in bytes, currently used for cloned nodes. During the
-       checkpoint operation, dirty nodes are cloned prior to
-       serialization/compression, then written to disk. After which, the memory for
-       the cloned block is returned for re-use.
-
-   * - cachetable: evictions
-     - Number of blocks evicted from cache.
-
-   * - cachetable: cleaner executions
-     - Total number of times the cleaner thread loop has executed.
-
-   * - cachetable: cleaner period
-     - *TokuDB* includes a cleaner thread that optimizes indexes in the background.
-       This variable is the time, in seconds, between the completion of a group of
-       cleaner operations and the beginning of the next group of cleaner operations.
-       The cleaner operations run on a background thread performing work that does
-       not need to be done on the client thread.
-
-   * - cachetable: cleaner iterations
-     - This is the number of cleaner operations that are performed every cleaner
-       period.
-
-   * - cachetable: number of waits on cache pressure
-     - The number of times a thread was stalled due to cache pressure.
-
-   * - cachetable: time waiting on cache pressure
-     - Total time, in microseconds, waiting on cache pressure to subside.
-
-   * - cachetable: number of long waits on cache pressure
-     - The number of times a thread was stalled for more than 1 second due to cache
-       pressure.
-
-   * - cachetable: long time waiting on cache pressure
-     - Total time, in microseconds, waiting on cache pressure to subside for more
-       than 1 second.
-
-   * - cachetable: client pool: number of threads in pool
-     - The number of threads in the client thread pool.
-
-   * - cachetable: client pool: number of currently active threads in pool
-     - The number of currently active threads in the client thread pool.
-
-   * - cachetable: client pool: number of currently queued work items
-     - The number of currently queued work items in the client thread pool.
-
-   * - cachetable: client pool: largest number of queued work items
-     - The largest number of queued work items in the client thread pool.
-
-   * - cachetable: client pool: total number of work items processed
-     - The total number of work items processed in the client thread pool.
-
-   * - cachetable: client pool: total execution time of processing work items
-     - The total execution time of processing work items in the client thread pool.
-
-   * - cachetable: cachetable pool: number of threads in pool
-     - The number of threads in the cachetable thread pool.
-
-   * - cachetable: cachetable pool: number of currently active threads in pool
-     - The number of currently active threads in the cachetable thread pool.
-
-   * - cachetable: cachetable pool: number of currently queued work items
-     - The number of currently queued work items in the cachetable thread pool.
-
-   * - cachetable: cachetable pool: largest number of queued work items
-     - The largest number of queued work items in the cachetable thread pool.
-
-   * - cachetable: cachetable pool: total number of work items processed
-     - The total number of work items processed in the cachetable thread pool.
-
-   * - cachetable: cachetable pool: total execution time of processing work items
-     - The total execution time of processing work items in the cachetable thread
-       pool.
-
-   * - cachetable: checkpoint pool: number of threads in pool
-     - The number of threads in the checkpoint thread pool.
-
-   * - cachetable: checkpoint pool: number of currently active threads in pool
-     - The number of currently active threads in the checkpoint thread pool.
-
-   * - cachetable: checkpoint pool: number of currently queued work items
-     - The number of currently queued work items in the checkpoint thread pool.
-
-   * - cachetable: checkpoint pool: largest number of queued work items
-     - The largest number of queued work items in the checkpoint thread pool.
-
-   * - cachetable: checkpoint pool: total number of work items processed
-     - The total number of work items processed in the checkpoint thread pool.
-
-   * - cachetable: checkpoint pool: total execution time of processing work items
-     - The total execution time of processing work items in the checkpoint thread
-       pool.
-
-   * - locktree: memory size
-     - The amount of memory, in bytes, that the locktree is currently using.
-
-   * - locktree: memory size limit
-     - The maximum amount of memory, in bytes, that the locktree is allowed to use.
-
-   * - locktree: number of times lock escalation ran
-     - Number of times the locktree needed to run lock escalation to reduce its
-       memory footprint.
-
-   * - locktree: time spent running escalation (seconds)
-     - Total number of seconds spent performing locktree escalation.
-
-   * - locktree: latest post-escalation memory size
-     - Size of the locktree, in bytes, after most current locktree escalation.
-
-   * - locktree: number of locktrees open now
-     - Number of locktrees currently open.
-
-   * - locktree: number of pending lock requests
-     - Number of requests waiting for a lock grant.
-
-   * - locktree: number of locktrees eligible for the STO
-     - Number of locktrees eligible for "Single Transaction Optimizations". ``STO``
-       optimization are behaviors that can happen within the locktree when there is
-       exactly one transaction active within the locktree. This is a not a useful
-       value for a regular user to use for any purpose.
-
-   * - locktree: number of times a locktree ended the STO early
-     - Total number of times a "single transaction optimization" was ended early due
-       to another trans- action starting.
-
-   * - locktree: time spent ending the STO early (seconds)
-     - Total number of seconds ending "Single Transaction Optimizations". ``STO``
-       optimization are behaviors that can happen within the locktree when there is
-       exactly one transaction active within the locktree. This is a not a useful
-       value for a regular user to use for any purpose.
-
-   * - locktree: number of wait locks
-     - Number of times that a lock request could not be acquired because of a
-       conflict with some other transaction.
-
-   * - locktree: time waiting for locks
-     - Total time, in microseconds, spend by some client waiting for a lock conflict
-       to be resolved.
-
-   * - locktree: number of long wait locks
-     - Number of lock waits greater than 1 second in duration.
-
-   * - locktree: long time waiting for locks
-     - Total time, in microseconds, of the long waits.
-
-   * - locktree: number of lock timeouts
-     - Count of the number of times that a lock request timed out.
-
-   * - locktree: number of waits on lock escalation
-     - When the sum of the sizes of locks taken reaches the lock tree limit, we run
-       lock escalation on a background thread. The clients threads need to wait for
-       escalation to consolidate locks and free up memory. This counter counts the
-       number of times a client thread has to wait on lock escalation.
-
-   * - locktree: time waiting on lock escalation
-     - Total time, in microseconds, that a client thread spent waiting for lock
-       escalation to free up memory.
-
-   * - locktree: number of long waits on lock escalation
-     - Number of times that a client thread had to wait on lock escalation and the
-       wait time was greater than 1 second.
-
-   * - locktree: long time waiting on lock escalation
-     - Total time, in microseconds, of the long waits for lock escalation to free up
-       memory.
-
-   * - ft: dictionary updates
-     - This is the total number of rows that have been updated in all primary and
-       secondary indexes combined, if those updates have been done with a separate
-       recovery log entry per index.
-
-   * - ft: dictionary broadcast updates
-     - This is the number of broadcast updates that have been successfully performed.
-       A broadcast update is an update that affects all rows in a dictionary.
-
-   * - ft: descriptor set
-     - This is the number of time a descriptor was updated when the entire dictionary
-       was updated (for example, when the schema has been changed).
-
-   * - ft: messages ignored by leaf due to msn
-     - The number of messages that were ignored by a leaf because it had already been
-       applied.
-
-   * - ft: total search retries due to TRY AGAIN
-     - Total number of search retries due to TRY AGAIN. Internal value that is no use
-       to anyone other than a developer debugging a specific query/search issue.
-
-   * - ft: searches requiring more tries than the height of the tree
-     - Number of searches that required more tries than the height of the tree.
-
-   * - ft: searches requiring more tries than the height of the tree plus three
-     - Number of searches that required more tries than the height of the tree plus
-       three.
-
-   * - ft: leaf nodes flushed to disk (not for checkpoint)
-     - Number of leaf nodes flushed to disk, not for checkpoint.
-
-   * - ft: leaf nodes flushed to disk (not for checkpoint) (bytes)
-     - Number of bytes of leaf nodes flushed to disk, not for checkpoint.
-
-   * - ft: leaf nodes flushed to disk (not for checkpoint) (uncompressed bytes)
-     - Number of bytes of leaf nodes flushed to disk, not for checkpoint.
-
-   * - ft: leaf nodes flushed to disk (not for checkpoint) (seconds)
-     - Number of seconds waiting for IO when writing leaf nodes flushed to disk, not
-       for checkpoint.
-
-   * - ft: nonleaf nodes flushed to disk (not for checkpoint)
-     - Number of non-leaf nodes flushed to disk, not for checkpoint.
-
-   * - ft: nonleaf nodes flushed to disk (not for checkpoint) (bytes)
-     - Number of bytes of non-leaf nodes flushed to disk, not for checkpoint.
-
-   * - ft: nonleaf nodes flushed to disk (not for checkpoint) (uncompressed bytes)
-     - Number of uncompressed bytes of non-leaf nodes flushed to disk, not for
-       checkpoint.
-
-   * - ft: nonleaf nodes flushed to disk (not for checkpoint) (seconds)
-     - Number of seconds waiting for I/O when writing non-leaf nodes flushed to disk,
-       not for checkpoint.
-
-   * - ft: leaf nodes flushed to disk (for checkpoint)
-     - Number of leaf nodes flushed to disk for checkpoint.
-
-   * - ft: leaf nodes flushed to disk (for checkpoint) (bytes)
-     - Number of bytes of leaf nodes flushed to disk for checkpoint.
-
-   * - ft: leaf nodes flushed to disk (for checkpoint) (uncompressed bytes)
-     - Number of uncompressed bytes of leaf nodes flushed to disk for checkpoint.
-
-   * - ft: leaf nodes flushed to disk (for checkpoint) (seconds)
-     - Number of seconds waiting for IO when writing leaf nodes flushed to disk for
-       checkpoint.
-
-   * - ft: nonleaf nodes flushed to disk (for checkpoint)
-     - Number of non-leaf nodes flushed to disk for checkpoint.
-
-   * - ft: nonleaf nodes flushed to disk (for checkpoint) (bytes)
-     - Number of bytes of non-leaf nodes flushed to disk for checkpoint.
-
-   * - ft: nonleaf nodes flushed to disk (for checkpoint) (uncompressed bytes)
-     - Number of uncompressed bytes of non-leaf nodes flushed to disk for checkpoint.
-
-   * - ft: nonleaf nodes flushed to disk (for checkpoint) (seconds)
-     - Number of seconds waiting for IO when writing non-leaf nodes flushed to disk
-       for checkpoint.
-
-   * - ft: uncompressed / compressed bytes written (leaf)
-     - Ratio of uncompressed bytes (in-memory) to compressed bytes (on-disk) for leaf
-       nodes.
-
-   * - ft: uncompressed / compressed bytes written (nonleaf)
-     - Ratio of uncompressed bytes (in-memory) to compressed bytes (on-disk) for
-       non-leaf nodes.
-
-   * - ft: uncompressed / compressed bytes written (overall)
-     - Ratio of uncompressed bytes (in-memory) to compressed bytes (on-disk) for all
-       nodes.
-
-   * - ft: nonleaf node partial evictions
-     - The number of times a partition of a non-leaf node was evicted from the cache.
-
-   * - ft: nonleaf node partial evictions (bytes)
-     - The number of bytes freed by evicting partitions of non-leaf nodes from the
-       cache.
-
-   * - ft: leaf node partial evictions
-     - The number of times a partition of a leaf node was evicted from the cache.
-
-   * - ft: leaf node partial evictions (bytes)
-     - The number of bytes freed by evicting partitions of leaf nodes from the cache.
-
-   * - ft: leaf node full evictions
-     - The number of times a full leaf node was evicted from the cache.
-
-   * - ft: leaf node full evictions (bytes)
-     - The number of bytes freed by evicting full leaf nodes from the cache.
-
-   * - ft: nonleaf node full evictions (bytes)
-     - The number of bytes freed by evicting full non-leaf nodes from the cache.
-
-   * - ft: nonleaf node full evictions
-     - The number of times a full non-leaf node was evicted from the cache.
-
-   * - ft: leaf nodes created
-     - Number of created leaf nodes .
-
-   * - ft: nonleaf nodes created
-     - Number of created non-leaf nodes.
-
-   * - ft: leaf nodes destroyed
-     - Number of destroyed leaf nodes.
-
-   * - ft: nonleaf nodes destroyed
-     - Number of destroyed non-leaf nodes.
-
-   * - ft: bytes of messages injected at root (all trees)
-     - Amount of messages, in bytes, injected at root (for all trees).
-
-   * - ft: bytes of messages flushed from h1 nodes to leaves
-     - Amount of messages, in bytes, flushed from ``h1`` nodes to leaves.
-
-   * - ft: bytes of messages currently in trees (estimate)
-     - Amount of messages, in bytes, currently in trees (estimate).
-
-   * - ft: messages injected at root
-     - Number of messages injected at root node of a tree.
-
-   * - ft: broadcast messages injected at root
-     - Number of broadcast messages injected at root node of a tree.
-
-   * - ft: basements decompressed as a target of a query
-     - Number of basement nodes decompressed for queries.
-
-   * - ft: basements decompressed for prelocked range
-     - Number of basement nodes decompressed by queries aggressively.
-
-   * - ft: basements decompressed for prefetch
-     - Number of basement nodes decompressed by a prefetch thread.
-
-   * - ft: basements decompressed for write
-     - Number of basement nodes decompressed for writes.
-
-   * - ft: buffers decompressed as a target of a query
-     - Number of buffers decompressed for queries.
-
-   * - ft: buffers decompressed for prelocked range
-     - Number of buffers decompressed by queries aggressively.
-
-   * - ft: buffers decompressed for prefetch
-     - Number of buffers decompressed by a prefetch thread.
-
-   * - ft: buffers decompressed for write
-     - Number of buffers decompressed for writes.
-
-   * - ft: pivots fetched for query
-     - Number of pivot nodes fetched for queries.
-
-   * - ft: pivots fetched for query (bytes)
-     - Number of bytes of pivot nodes fetched for queries.
-
-   * - ft: pivots fetched for query (seconds)
-     - Number of seconds waiting for I/O when fetching pivot nodes for queries.
-
-   * - ft: pivots fetched for prefetch
-     - Number of pivot nodes fetched by a prefetch thread.
-
-   * - ft: pivots fetched for prefetch (bytes)
-     - Number of bytes of pivot nodes fetched by a prefetch thread.
-
-   * - ft: pivots fetched for prefetch (seconds)
-     - Number seconds waiting for I/O when fetching pivot nodes by a prefetch thread.
-
-   * - ft: pivots fetched for write
-     - Number of pivot nodes fetched for writes.
-
-   * - ft: pivots fetched for write (bytes)
-     - Number of bytes of pivot nodes fetched for writes.
-
-   * - ft: pivots fetched for write (seconds)
-     - Number of seconds waiting for I/O when fetching pivot nodes for writes.
-
-   * - ft: basements fetched as a target of a query
-     - Number of basement nodes fetched from disk for queries.
-
-   * - ft: basements fetched as a target of a query (bytes)
-     - Number of basement node bytes fetched from disk for queries.
-
-   * - ft: basements fetched as a target of a query (seconds)
-     - Number of seconds waiting for IO when fetching basement nodes from disk for
-       queries.
-
-   * - ft: basements fetched for prelocked range
-     - Number of basement nodes fetched from disk aggressively.
-
-   * - ft: basements fetched for prelocked range (bytes)
-     - Number of basement node bytes fetched from disk aggressively.
-
-   * - ft: basements fetched for prelocked range (seconds)
-     - Number of seconds waiting for I/O when fetching basement nodes from disk
-       aggressively.
-
-   * - ft: basements fetched for prefetch
-     - Number of basement nodes fetched from disk by a prefetch thread.
-
-   * - ft: basements fetched for prefetch (bytes)
-     - Number of basement node bytes fetched from disk by a prefetch thread.
-
-   * - ft: basements fetched for prefetch (seconds)
-     - Number of seconds waiting for I/O when fetching basement nodes from disk by a
-       prefetch thread.
-
-   * - ft: basements fetched for write
-     - Number of basement nodes fetched from disk for writes.
-
-   * - ft: basements fetched for write (bytes)
-     - Number of basement node bytes fetched from disk for writes.
-
-   * - ft: basements fetched for write (seconds)
-     - Number of seconds waiting for I/O when fetching basement nodes from disk for
-       writes.
-
-   * - ft: buffers fetched as a target of a query
-     - Number of buffers fetched from disk for queries.
-
-   * - ft: buffers fetched as a target of a query (bytes)
-     - Number of buffer bytes fetched from disk for queries.
-
-   * - ft: buffers fetched as a target of a query (seconds)
-     - Number of seconds waiting for I/O when fetching buffers from disk for queries.
-
-   * - ft: buffers fetched for prelocked range
-     - Number of buffers fetched from disk aggressively.
-
-   * - ft: buffers fetched for prelocked range (bytes)
-     - Number of buffer bytes fetched from disk aggressively.
-
-   * - ft: buffers fetched for prelocked range (seconds)
-     - Number of seconds waiting for I/O when fetching buffers from disk
-       aggressively.
-
-   * - ft: buffers fetched for prefetch
-     - Number of buffers fetched from disk by a prefetch thread.
-
-   * - ft: buffers fetched for prefetch (bytes)
-     - Number of buffer bytes fetched from disk by a prefetch thread.
-
-   * - ft: buffers fetched for prefetch (seconds)
-     - Number of seconds waiting for I/O when fetching buffers from disk by a
-       prefetch thread.
-
-   * - ft: buffers fetched for write
-     - Number of buffers fetched from disk for writes.
-
-   * - ft: buffers fetched for write (bytes)
-     - Number of buffer bytes fetched from disk for writes.
-
-   * - ft: buffers fetched for write (seconds)
-     - Number of seconds waiting for I/O when fetching buffers from disk for writes.
-
-   * - ft: leaf compression to memory (seconds)
-     - Total time, in seconds, spent compressing leaf nodes.
-
-   * - ft: leaf serialization to memory (seconds)
-     - Total time, in seconds, spent serializing leaf nodes.
-
-   * - ft: leaf decompression to memory (seconds)
-     - Total time, in seconds, spent decompressing leaf nodes.
-
-   * - ft: leaf deserialization to memory (seconds)
-     - Total time, in seconds, spent deserializing leaf nodes.
-
-   * - ft: nonleaf compression to memory (seconds)
-     - Total time, in seconds, spent compressing non leaf nodes.
-
-   * - ft: nonleaf serialization to memory (seconds)
-     - Total time, in seconds, spent serializing non leaf nodes.
-
-   * - ft: nonleaf decompression to memory (seconds)
-     - Total time, in seconds, spent decompressing non leaf nodes.
-
-   * - ft: nonleaf deserialization to memory (seconds)
-     - Total time, in seconds, spent deserializing non leaf nodes.
-
-   * - ft: promotion: roots split
-     - Number of times the root split during promotion.
-
-   * - ft: promotion: leaf roots injected into
-     - Number of times a message stopped at a root with height ``0``.
-
-   * - ft: promotion: h1 roots injected into
-     - Number of times a message stopped at a root with height ``1``.
-
-   * - ft: promotion: injections at depth 0
-     - Number of times a message stopped at depth ``0``.
-
-   * - ft: promotion: injections at depth 1
-     - Number of times a message stopped at depth ``1``.
-
-   * - ft: promotion: injections at depth 2
-     - Number of times a message stopped at depth ``2``.
-
-   * - ft: promotion: injections at depth 3
-     - Number of times a message stopped at depth ``3``.
-
-   * - ft: promotion: injections lower than depth 3
-     - Number of times a message was promoted past depth ``3``.
-
-   * - ft: promotion: stopped because of a nonempty buffer
-     - Number of times a message stopped because it reached a nonempty buffer.
-
-   * - ft: promotion: stopped at height 1
-     - Number of times a message stopped because it had reached height ``1``.
-
-   * - ft: promotion: stopped because the child was locked or not at all in memory
-     - Number of times promotion was stopped because the child node was locked or not
-       at all in memory. This is a not a useful value for a regular user to use for
-       any purpose.
-
-   * - ft: promotion: stopped because the child was not fully in memory
-     - Number of times promotion was stopped because the child node was not at all in
-       memory. This is a not a useful value for a normal user to use for any purpose.
-
-   * - ft: promotion: stopped anyway, after locking the child
-     - Number of times a message stopped before a child which had been locked.
-
-   * - ft: basement nodes deserialized with fixed-keysize
-     - The number of basement nodes deserialized where all keys had the same size,
-       leaving the basement in a format that is optimal for in-memory workloads.
-
-   * - ft: basement nodes deserialized with variable-keysize
-     - The number of basement nodes deserialized where all keys did not have the same
-       size, and thus ineligible for an in-memory optimization.
-
-   * - ft: promotion: succeeded in using the rightmost leaf shortcut
-     - Rightmost insertions used the rightmost-leaf pin path, meaning that the
-       Fractal Tree index detected and properly optimized rightmost inserts.
-
-   * - ft: promotion: tried the rightmost leaf shortcut but failed (out-of-bounds)
-     - Rightmost insertions did not use the rightmost-leaf pin path, due to the
-       insert not actually being into the rightmost leaf node.
-
-   * - ft: promotion: tried the rightmost leaf shortcut but failed (child reactive)
-     - Rightmost insertions did not use the rightmost-leaf pin path, due to the
-       leaf being too large (needed to split).
-
-   * - ft: cursor skipped deleted leaf entries
-     - Number of leaf entries skipped during search/scan because the result of
-       message application and reconciliation of the leaf entry MVCC stack reveals
-       that the leaf entry is deleted in the current transactions view. It is a good
-       indicator that there might be excessive garbage in a tree if a range scan
-       seems to take too long.
-
-   * - ft flusher: total nodes potentially flushed by cleaner thread
-     - Total number of nodes whose buffers are potentially flushed by cleaner thread.
-
-   * - ft flusher: height-one nodes flushed by cleaner thread
-     - Number of nodes of height one whose message buffers are flushed by cleaner
-       thread.
-
-   * - ft flusher: height-greater-than-one nodes flushed by cleaner thread
-     - Number of nodes of height > 1 whose message buffers are flushed by cleaner
-       thread.
-
-   * - ft flusher: nodes cleaned which had empty buffers
-     - Number of nodes that are selected by cleaner, but whose buffers are empty.
-
-   * - ft flusher: nodes dirtied by cleaner thread
-     - Number of nodes that are made dirty by the cleaner thread.
-
-   * - ft flusher: max bytes in a buffer flushed by cleaner thread
-     - Max number of bytes in message buffer flushed by cleaner thread.
-
-   * - ft flusher: min bytes in a buffer flushed by cleaner thread
-     - Min number of bytes in message buffer flushed by cleaner thread.
-
-   * - ft flusher: total bytes in buffers flushed by cleaner thread
-     - Total number of bytes in message buffers flushed by cleaner thread.
-
-   * - ft flusher: max workdone in a buffer flushed by cleaner thread
-     - Max workdone value of any message buffer flushed by cleaner thread.
-
-   * - ft flusher: min workdone in a buffer flushed by cleaner thread
-     - Min workdone value of any message buffer flushed by cleaner thread.
-
-   * - ft flusher: total workdone in buffers flushed by cleaner thread
-     - Total workdone value of message buffers flushed by cleaner thread.
-
-   * - ft flusher: times cleaner thread tries to merge a leaf
-     - The number of times the cleaner thread tries to merge a leaf.
-
-   * - ft flusher: cleaner thread leaf merges in progress
-     - The number of cleaner thread leaf merges in progress.
-
-   * - ft flusher: cleaner thread leaf merges successful
-     - The number of times the cleaner thread successfully merges a leaf.
-
-   * - ft flusher: nodes dirtied by cleaner thread leaf merges
-     - The number of nodes dirtied by the "flush from root" process to merge a leaf node.
-
-   * - ft flusher: total number of flushes done by flusher threads or cleaner threads
-     - Total number of flushes done by flusher threads or cleaner threads.
-
-   * - ft flusher: number of in memory flushes
-     - Number of in-memory flushes.
-
-   * - ft flusher: number of flushes that read something off disk
-     - Number of flushes that had to read a child (or part) off disk.
-
-   * - ft flusher: number of flushes that triggered another flush in child
-     - Number of flushes that triggered another flush in the child.
-
-   * - ft flusher: number of flushes that triggered 1 cascading flush
-     - Number of flushes that triggered 1 cascading flush.
-
-   * - ft flusher: number of flushes that triggered 2 cascading flushes
-     - Number of flushes that triggered 2 cascading flushes.
-
-   * - ft flusher: number of flushes that triggered 3 cascading flushes
-     - Number of flushes that triggered 3 cascading flushes.
-
-   * - ft flusher: number of flushes that triggered 4 cascading flushes
-     - Number of flushes that triggered 4 cascading flushes.
-
-   * - ft flusher: number of flushes that triggered 5 cascading flushes
-     - Number of flushes that triggered 5 cascading flushes.
-
-   * - ft flusher: number of flushes that triggered over 5 cascading flushes
-     - Number of flushes that triggered more than 5 cascading flushes.
-
-   * - ft flusher: leaf node splits
-     - Number of leaf nodes split.
-
-   * - ft flusher: nonleaf node splits
-     - Number of non-leaf nodes split.
-
-   * - ft flusher: leaf node merges
-     - Number of times leaf nodes are merged.
-
-   * - ft flusher: nonleaf node merges
-     - Number of times non-leaf nodes are merged.
-
-   * - ft flusher: leaf node balances
-     - Number of times a leaf node is balanced.
-
-   * - hot: operations ever started
-     - This variable shows the number of hot operations started (``OPTIMIZE TABLE``).
-       This is a not a useful value for a regular user to use for any purpose.
-
-   * - hot: operations successfully completed
-     - The number of hot operations that have successfully completed (``OPTIMIZE
-       TABLE``). This is a not a useful value for a regular user to use for any
-       purpose.
-
-   * - hot: operations aborted
-     - The number of hot operations that have been aborted (``OPTIMIZE TABLE``).
-       This is a not a useful value for a regular user to use for any purpose.
-
-   * - hot: max number of flushes from root ever required to optimize a tree
-     - The maximum number of flushes from the root ever required to optimize a tree.
-
-   * - txn: begin
-     - This is the number of transactions that have been started.
-
-   * - txn: begin read only
-     - Number of read only transactions started.
-
-   * - txn: successful commits
-     - This is the total number of transactions that have been committed.
-
-   * - txn: aborts
-     - This is the total number of transactions that have been aborted.
-
-   * - logger: next LSN
-     - This is the next unassigned Log Sequence Number. It will be assigned to the
-       next entry in the recovery log.
-
-   * - logger: writes
-     - Number of times the logger has written to disk.
-
-   * - logger: writes (bytes)
-     - Number of bytes the logger has written to disk.
-
-   * - logger: writes (uncompressed bytes)
-     - Number of uncompressed the logger has written to disk.
-
-   * - logger: writes (seconds)
-     - Number of seconds waiting for I/O when writing logs to disk.
-
-   * - logger: number of long logger write operations
-     - Number of times a logger write operation required 100ms or more.
-
-   * - indexer: number of indexers successfully created
-     - This is the number of times one of our internal objects, a indexer, has been
-       created.
-
-   * - indexer: number of calls to toku_indexer_create_indexer() that failed
-     - This is the number of times a indexer was requested but could not be created.
-
-   * - indexer: number of calls to indexer->build() succeeded
-     - This is the total number of times that indexes were created using a indexer.
-
-   * - indexer: number of calls to indexer->build() failed
-     - This is the total number of times that indexes were unable to be created using a indexer
-
-   * - indexer: number of calls to indexer->close() that succeeded
-     - This is the number of indexers that successfully created the requested index(es).
-
-   * - indexer: number of calls to indexer->close() that failed
-     - This is the number of indexers that were unable to create the requested index(es).
-
-   * - indexer: number of calls to indexer->abort()
-     - This is the number of indexers that were aborted.
-
-   * - indexer: number of indexers currently in existence
-     - This is the number of indexers that currently exist.
-
-   * - indexer: max number of indexers that ever existed simultaneously
-     - This is the maximum number of indexers that ever existed simultaneously.
-
-   * - loader: number of loaders successfully created
-     - This is the number of times one of our internal objects, a loader, has been
-       created.
-
-   * - loader: number of calls to toku_loader_create_loader() that failed
-     - This is the number of times a loader was requested but could not be created.
-
-   * - loader: number of calls to loader->put() succeeded
-     - This is the total number of rows that were inserted using a loader.
-
-   * - loader: number of calls to loader->put() failed
-     - This is the total number of rows that were unable to be inserted using a
-       loader.
-
-   * - loader: number of calls to loader->close() that succeeded
-     - This is the number of loaders that successfully created the requested table.
-
-   * - loader: number of calls to loader->close() that failed
-     - This is the number of loaders that were unable to create the requested table.
-
-   * - loader: number of calls to loader->abort()
-     - This is the number of loaders that were aborted.
-
-   * - loader: number of loaders currently in existence
-     - This is the number of loaders that currently exist.
-
-   * - loader: max number of loaders that ever existed simultaneously
-     - This is the maximum number of loaders that ever existed simultaneously.
-
-   * - memory: number of malloc operations
-     - Number of calls to ``malloc()``.
-
-   * - memory: number of free operations
-     - Number of calls to ``free()``.
-
-   * - memory: number of realloc operations
-     - Number of calls to ``realloc()``.
-
-   * - memory: number of malloc operations that failed
-     - Number of failed calls to ``malloc()``.
-
-   * - memory: number of realloc operations that failed
-     - Number of failed calls to ``realloc()``.
-
-   * - memory: number of bytes requested
-     - Total number of bytes requested from memory allocator library.
-
-   * - memory: number of bytes freed
-     - Total number of bytes allocated from memory allocation library that have been
-       freed (used - freed = bytes in use).
-
-   * - memory: largest attempted allocation size
-     - Largest number of bytes in a single successful ``malloc()`` operation.
-
-   * - memory: size of the last failed allocation attempt
-     - Largest number of bytes in a single failed ``malloc()`` operation.
-
-   * - memory: number of bytes used (requested + overhead)
-     - Total number of bytes allocated by memory allocator library.
-
-   * - memory: estimated maximum memory footprint
-     - Maximum memory footprint of the storage engine,
-       the max value of (used - freed).
-
-   * - memory: mallocator version
-     - Version string from in-use memory allocator.
-
-   * - memory: mmap threshold
-     - The threshold for malloc to use mmap.
-
-   * - filesystem: ENOSPC redzone state
-     - The state of how much disk space exists with respect to the red zone value.
-       Redzone is space greater than :ref:`tokudb_fs_reserve_percent` and less
-       than full disk.
-
-       Valid values are:
-
-       :0: Space is available
-       :1: Warning, with 2x of redzone value. Operations are allowed, but engine
-	   status prints a warning.
-       :2: In red zone, insert operations are blocked
-       :3: All operations are blocked
-
-   * - filesystem: threads currently blocked by full disk
-     - This is the number of threads that are currently blocked because they are
-       attempting to write to a full disk. This is normally zero. If this value is
-       non-zero, then a warning will appear in the "disk free space" field.
-
-   * - filesystem: number of operations rejected by enospc prevention (red zone)
-     - This is the number of database inserts that have been rejected because the
-       amount of disk free space was less than the reserve.
-
-   * - filesystem: most recent disk full
-     - This is the most recent time when the disk file system was entirely full. If
-       the disk has never been full, then this value will be ``Dec 31, 1969`` on
-       Linux hosts.
-
-   * - filesystem: number of write operations that returned ENOSPC
-     - This is the number of times that an attempt to write to disk failed because
-       the disk was full. If the disk is full, this number will continue increasing
-       until space is available.
-
-   * - filesystem: fsync time
-     - This the total time, in microseconds, used to fsync to disk.
-
-   * - filesystem: fsync count
-     - This is the total number of times the database has flushed the operating
-       system's file buffers to disk.
-
-   * - filesystem: long fsync time
-     - This the total time, in microseconds, used to fsync to disk when the operation
-       required more than 1 second.
-
-   * - filesystem: long fsync count
-     - This is the total number of times the database has flushed the operating
-       system's file buffers to disk and this operation required more than 1 second.
-
-   * - context: tree traversals blocked by a full fetch
-     - Number of times node ``rwlock`` contention was observed while pinning nodes
-       from root to leaf because of a full fetch.
-
-   * - context: tree traversals blocked by a partial fetch
-     - Number of times node ``rwlock`` contention was observed while pinning nodes
-       from root to leaf because of a partial fetch.
-
-   * - context: tree traversals blocked by a full eviction
-     - Number of times node ``rwlock`` contention was observed while pinning nodes
-       from root to leaf because of a full eviction.
-
-   * - context: tree traversals blocked by a partial eviction
-     - Number of times node ``rwlock`` contention was observed while pinning nodes
-       from root to leaf because of a partial eviction.
-
-   * - context: tree traversals blocked by a message injection
-     - Number of times node ``rwlock`` contention was observed while pinning nodes
-       from root to leaf because of message injection.
-
-   * - context: tree traversals blocked by a message application
-     - Number of times node ``rwlock`` contention was observed while pinning nodes
-       from root to leaf because of message application (applying fresh ancestors
-       messages to a basement node).
-
-   * - context: tree traversals blocked by a flush
-     - Number of times node ``rwlock`` contention was observed while pinning nodes
-       from root to leaf because of a buffer flush from parent to child.
-
-   * - context: tree traversals blocked by a the cleaner thread
-     - Number of times node ``rwlock`` contention was observed while pinning nodes
-       from root to leaf because of a cleaner thread.
-
-   * - context: tree traversals blocked by something uninstrumented
-     - Number of times node ``rwlock`` contention was observed while pinning nodes
-       from root to leaf because of something uninstrumented.
-
-   * - context: promotion blocked by a full fetch (should never happen)
-     - Number of times node ``rwlock`` contention was observed within promotion
-       (pinning nodes from root to the buffer to receive the message) because of a
-       full fetch.
-
-   * - context: promotion blocked by a partial fetch (should never happen)
-     - Number of times node ``rwlock`` contention was observed within promotion
-       (pinning nodes from root to the buffer to receive the message) because of a
-       partial fetch.
-
-   * - context: promotion blocked by a full eviction (should never happen)
-     - Number of times node ``rwlock`` contention was observed within promotion
-       (pinning nodes from root to the buffer to receive the message) because of a
-       full eviction.
-
-   * - context: promotion blocked by a partial eviction (should never happen)
-     - Number of times node ``rwlock`` contention was observed within promotion
-       (pinning nodes from root to the buffer to receive the message) because of a
-       partial eviction.
-
-   * - context: promotion blocked by a message injection
-     - Number of times node ``rwlock`` contention was observed within promotion
-       (pinning nodes from root to the buffer to receive the message) because of
-       message injection.
-
-   * - context: promotion blocked by a message application
-     - Number of times node ``rwlock`` contention was observed within promotion
-       (pinning nodes from root to the buffer to receive the message) because of
-       message application (applying fresh ancestors messages to a basement node).
-
-   * - context: promotion blocked by a flush
-     - Number of times node ``rwlock`` contention was observed within promotion
-       (pinning nodes from root to the buffer to receive the message) because of a
-       buffer flush from parent to child.
-
-   * - context: promotion blocked by the cleaner thread
-     - Number of times node ``rwlock`` contention was observed within promotion
-       (pinning nodes from root to the buffer to receive the message) because of a
-       cleaner thread.
-
-   * - context: promotion blocked by something uninstrumented
-     - Number of times node ``rwlock`` contention was observed within promotion
-       (pinning nodes from root to the buffer to receive the message) because of
-       something uninstrumented.
-
-   * - context: something uninstrumented blocked by something uninstrumented
-     - Number of times node ``rwlock`` contention was observed for an uninstrumented
-       process because of something uninstrumented.
-
-   * - handlerton: primary key bytes inserted
-     - Total number of bytes inserted into all primary key indexes.
diff --git a/doc/source/tokudb/tokudb_variables.rst b/doc/source/tokudb/tokudb_variables.rst
deleted file mode 100644
index 40585ae6e123..000000000000
--- a/doc/source/tokudb/tokudb_variables.rst
+++ /dev/null
@@ -1,2401 +0,0 @@
-.. _tokudb_variables:
-
-================
-TokuDB Variables
-================
-
-.. Important:: 
-
-   Starting with :ref:`8.0.28-19`, the TokuDB storage engine is no longer supported. We have removed the storage engine from the installation packages and disabled the storage engine in our binary builds.
-
-   Starting with :ref:`8.0.26-16`, the binary builds and packages include but disable the TokuDB storage engine plugins. The ``tokudb_enabled`` option and the ``tokudb_backup_enabled`` option control the state of the plugins and have a default setting of ``FALSE``. The result of attempting to load the plugins are the plugins fail to initialize and print a deprecation message.
-
-   We recommend :ref:`migrate-myrocks`. To enable the plugins to migrate to another storage engine, set the ``tokudb_enabled`` and ``tokudb_backup_enabled`` options to ``TRUE`` in your ``my.cnf`` file and restart your server instance. Then, you can load the plugins.
-
-   The TokuDB Storage Engine was `declared as deprecated <https://www.percona.com/doc/percona-server/8.0/release-notes/Percona-Server-8.0.13-3.html>`__ in Percona Server for MySQL 8.0. For more information, see the Percona blog post: `Heads-Up: TokuDB Support Changes and Future Removal from Percona Server for MySQL 8.0 <https://www.percona.com/blog/2021/05/21/tokudb-support-changes-and-future-removal-from-percona-server-for-mysql-8-0/>`__.
-
-Like all storage engines, *TokuDB* has variables to tune performance and
-control behavior. Fractal Tree algorithms are designed for near optimal
-performance and TokuDB's default settings should work well in most situations,
-eliminating the need for complex and time consuming tuning in most cases.
-
-.. contents::
-  :local:
-
-TokuDB Server Variables
------------------------
-
-.. tabularcolumns:: |p{8.5cm}|p{1.5cm}|p{1.5cm}|p{2cm}|p{1.5cm}|
-
-.. list-table::
-   :header-rows: 1
-
-   * - Name
-     - Cmd-Line
-     - Option File
-     - Var Scope
-     - Dynamic
-   * - :ref:`tokudb_alter_print_error`
-     - Yes
-     - Yes
-     - Session, Global
-     - Yes
-   * - :ref:`tokudb_analyze_delete_fraction`
-     - Yes
-     - Yes
-     - Session, Global
-     - Yes
-   * - :ref:`tokudb_analyze_in_background`
-     - Yes
-     - Yes
-     - Session, Global
-     - Yes
-   * - :ref:`tokudb_analyze_mode`
-     - Yes
-     - Yes
-     - Session, Global
-     - Yes
-   * - :ref:`tokudb_analyze_throttle`
-     - Yes
-     - Yes
-     - Session, Global
-     - Yes
-   * - :ref:`tokudb_analyze_time`
-     - Yes
-     - Yes
-     - Session, Global
-     - Yes
-   * - :ref:`tokudb_auto_analyze`
-     - Yes
-     - Yes
-     - Session, Global
-     - Yes
-   * - :ref:`tokudb_backup_allowed_prefix`
-     - No
-     - Yes
-     - Global
-     - No
-   * - :ref:`tokudb_backup_dir`
-     - No
-     - Yes
-     - Session
-     - No
-   * - :ref:`tokudb_backup_exclude`
-     - Yes
-     - Yes
-     - Session, Global
-     - Yes
-   * - :ref:`tokudb_backup_last_error`
-     - Yes
-     - Yes
-     - Session, Global
-     - Yes
-   * - :ref:`tokudb_backup_last_error_string`
-     - Yes
-     - Yes
-     - Session, Global
-     - Yes
-   * - :ref:`tokudb_backup_plugin_version`
-     - No
-     - No
-     - Global
-     - No
-   * - :ref:`tokudb_backup_throttle`
-     - Yes
-     - Yes
-     - Session, Global
-     - Yes
-   * - :ref:`tokudb_backup_version`
-     - No
-     - No
-     - Global
-     - No
-   * - :ref:`tokudb_block_size`
-     - Yes
-     - Yes
-     - Session, Global
-     - Yes
-   * - :ref:`tokudb_bulk_fetch`
-     - Yes
-     - Yes
-     - Session, Global
-     - Yes
-   * - :ref:`tokudb_cachetable_pool_threads`
-     - Yes
-     - Yes
-     - Global
-     - No
-   * - :ref:`tokudb_cardinality_scale_percent`
-     - Yes
-     - Yes
-     - Global
-     - Yes
-   * - :ref:`tokudb_check_jemalloc`
-     - Yes
-     - Yes
-     - Global
-     - No
-   * - :ref:`tokudb_checkpoint_lock`
-     - Yes
-     - Yes
-     - Global
-     - No
-   * - :ref:`tokudb_checkpoint_on_flush_logs`
-     - Yes
-     - Yes
-     - Global
-     - Yes
-   * - :ref:`tokudb_checkpoint_pool_threads`
-     - Yes
-     - Yes
-     - Global
-     - Yes
-   * - :ref:`tokudb_checkpointing_period`
-     - Yes
-     - Yes
-     - Global
-     - Yes
-   * - :ref:`tokudb_cleaner_iterations`
-     - Yes
-     - Yes
-     - Global
-     - Yes
-   * - :ref:`tokudb_cleaner_period`
-     - Yes
-     - Yes
-     - Global
-     - Yes
-   * - :ref:`tokudb_client_pool_threads`
-     - Yes
-     - Yes
-     - Global
-     - No
-   * - :ref:`tokudb_commit_sync`
-     - Yes
-     - Yes
-     - Session, Global
-     - Yes
-   * - :ref:`tokudb_compress_buffers_before_eviction`
-     - Yes
-     - Yes
-     - Global
-     - No
-   * - :ref:`tokudb_create_index_online`
-     - Yes
-     - Yes
-     - Session, Global
-     - Yes
-   * - :ref:`tokudb_data_dir`
-     - Yes
-     - Yes
-     - Global
-     - No
-   * - :ref:`tokudb_debug`
-     - Yes
-     - Yes
-     - Global
-     - Yes
-   * - :ref:`tokudb_dir_per_db`
-     - Yes
-     - Yes
-     - Global
-     - Yes
-   * - :ref:`tokudb_directio`
-     - Yes
-     - Yes
-     - Global
-     - No
-   * - :ref:`tokudb_disable_hot_alter`
-     - Yes
-     - Yes
-     - Session, Global
-     - Yes
-   * - :ref:`tokudb_disable_prefetching`
-     - Yes
-     - Yes
-     - Session, Global
-     - Yes
-   * - :ref:`tokudb_disable_slow_alter`
-     - Yes
-     - Yes
-     - Session, Global
-     - Yes
-   * - :ref:`tokudb_empty_scan`
-     - Yes
-     - Yes
-     - Session, Global
-     - Yes
-   * - :ref:`tokudb_enable_fast_update`
-     - Yes
-     - Yes
-     - Session, Global
-     - Yes
-   * - :ref:`tokudb_enable_fast_upsert`
-     - Yes
-     - Yes
-     - Session, Global
-     - Yes
-   * - :ref:`tokudb_enable_partial_eviction`
-     - Yes
-     - Yes
-     - Global
-     - No
-   * - :ref:`tokudb_fanout`
-     - Yes
-     - Yes
-     - Session, Global
-     - Yes
-   * - :ref:`tokudb_fs_reserve_percent`
-     - Yes
-     - Yes
-     - Global
-     - No
-   * - :ref:`tokudb_fsync_log_period`
-     - Yes
-     - Yes
-     - Global
-     - Yes
-   * - :ref:`tokudb_hide_default_row_format`
-     - Yes
-     - Yes
-     - Session, Global
-     - Yes
-   * - :ref:`tokudb_killed_time`
-     - Yes
-     - Yes
-     - Session, Global
-     - Yes
-   * - :ref:`tokudb_last_lock_timeout`
-     - Yes
-     - Yes
-     - Session, Global
-     - Yes
-   * - :ref:`tokudb_load_save_space`
-     - Yes
-     - Yes
-     - Session, Global
-     - Yes
-   * - :ref:`tokudb_loader_memory_size`
-     - Yes
-     - Yes
-     - Session, Global
-     - Yes
-   * - :ref:`tokudb_lock_timeout`
-     - Yes
-     - Yes
-     - Session, Global
-     - Yes
-   * - :ref:`tokudb_lock_timeout_debug`
-     - Yes
-     - Yes
-     - Session, Global
-     - Yes
-   * - :ref:`tokudb_log_dir`
-     - Yes
-     - Yes
-     - Global
-     - No
-   * - :ref:`tokudb_max_lock_memory`
-     - Yes
-     - Yes
-     - Global
-     - No
-   * - :ref:`tokudb_optimize_index_fraction`
-     - Yes
-     - Yes
-     - Session, Global
-     - Yes
-   * - :ref:`tokudb_optimize_index_name`
-     - Yes
-     - Yes
-     - Session, Global
-     - Yes
-   * - :ref:`tokudb_optimize_throttle`
-     - Yes
-     - Yes
-     - Session, Global
-     - Yes
-   * - :ref:`tokudb_pk_insert_mode`
-     - Yes
-     - Yes
-     - Session, Global
-     - Yes
-   * - :ref:`tokudb_prelock_empty`
-     - Yes
-     - Yes
-     - Session, Global
-     - Yes
-   * - :ref:`tokudb_read_block_size`
-     - Yes
-     - Yes
-     - Session, Global
-     - Yes
-   * - :ref:`tokudb_read_buf_size`
-     - Yes
-     - Yes
-     - Session, Global
-     - Yes
-   * - :ref:`tokudb_read_status_frequency`
-     - Yes
-     - Yes
-     - Global
-     - Yes
-   * - :ref:`tokudb_row_format`
-     - Yes
-     - Yes
-     - Session, Global
-     - Yes
-   * - :ref:`tokudb_rpl_check_readonly`
-     - Yes
-     - Yes
-     - Session, Global
-     - Yes
-   * - :ref:`tokudb_rpl_lookup_rows`
-     - Yes
-     - Yes
-     - Session, Global
-     - Yes
-   * - :ref:`tokudb_rpl_lookup_rows_delay`
-     - Yes
-     - Yes
-     - Session, Global
-     - Yes
-   * - :ref:`tokudb_rpl_unique_checks`
-     - Yes
-     - Yes
-     - Session, Global
-     - Yes
-   * - :ref:`tokudb_rpl_unique_checks_delay`
-     - Yes
-     - Yes
-     - Session, Global
-     - Yes
-   * - :ref:`tokudb_strip_frm_data`
-     - Yes
-     - Yes
-     - Global
-     - No
-   * - :ref:`tokudb_support_xa`
-     - Yes
-     - Yes
-     - Session, Global
-     - Yes
-   * - :ref:`tokudb_tmp_dir`
-     - Yes
-     - Yes
-     - Global
-     - No
-   * - :ref:`tokudb_version`
-     - No
-     - No
-     - Global
-     - No
-   * - :ref:`tokudb_write_status_frequency`
-     - Yes
-     - Yes
-     - Global
-     - Yes
-
-.. _tokudb_alter_print_error:
-
-.. rubric:: ``tokudb_alter_print_error``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - Yes
-   * - Config file
-     - Yes
-   * - Scope
-     - Global/Session
-   * - Dynamic
-     - Yes
-   * - Data type
-     - Boolean
-   * - Default
-     - OFF
-
-When set to ``ON`` errors will be printed to the client during the ``ALTER
-TABLE`` operations on *TokuDB* tables.
-
-.. _tokudb_analyze_delete_fraction:
-
-.. rubric:: ``tokudb_analyze_delete_fraction``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - Yes
-   * - Config file
-     - Yes
-   * - Scope
-     - Global/Session
-   * - Dynamic
-     - Yes
-   * - Data type
-     - Numeric
-   * - Default
-     - ``1.000000``
-   * - Range
-     - ``0.0`` - ``1.000000``
-
-This variables controls whether or not deleted rows in the fractal tree are
-reported to the client and to the *MySQL* error log during an ``ANALYZE TABLE``
-operation on a *TokuDB* table. When set to ``1``, nothing is reported. When set
-to ``0.1`` and at least 10% of the rows scanned by ``ANALYZE`` were deleted
-rows that are not yet garbage collected, a report is returned to the client and
-the *MySQL* error log.
-
-.. _tokudb_backup_allowed_prefix:
-
-.. rubric:: ``tokudb_backup_allowed_prefix``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - No
-   * - Config file
-     - Yes
-   * - Scope
-     - Global
-   * - Dynamic
-     - No
-   * - Data type
-     - String
-   * - Default
-     - NULL
-
-This system-level variable restricts the location of the destination directory
-where the backups can be located. Attempts to backup to a location outside of
-the directory this variable points to or its children will result in an error.
-
-The default is NULL, backups have no restricted locations. This read only
-variable can be set in the :file:`my.cnf` configuration file and displayed with
-the ``SHOW VARIABLES`` command when :ref:`toku_backup` plugin is loaded.
-
-.. code-block:: mysql
-
-  mysql> SHOW VARIABLES LIKE 'tokudb_backup_allowed_prefix';
-  +------------------------------+-----------+
-  | Variable_name                | Value     |
-  +------------------------------+-----------+
-  | tokudb_backup_allowed_prefix | /dumpdir  |
-  +------------------------------+-----------+
-
-.. _tokudb_backup_dir:
-
-.. rubric:: ``tokudb_backup_dir``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - No
-   * - Config file
-     - No
-   * - Scope
-     - Session
-   * - Dynamic
-     - Yes
-   * - Data type
-     - String
-   * - Default
-     - NULL
-
-When enabled, this session level variable serves two purposes, to point to the
-destination directory where the backups will be dumped and to kick off the
-backup as soon as it is set. For more information see :ref:`toku_backup`.
-
-.. _tokudb_backup_exclude:
-
-.. rubric:: ``tokudb_backup_exclude``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - No
-   * - Config file
-     - No
-   * - Scope
-     - Session
-   * - Dynamic
-     - Yes
-   * - Data type
-     - String
-   * - Default
-     - ``(mysqld_safe\.pid)+``
-
-Use this variable to set a regular expression that defines source files
-excluded from backup. For example, to exclude all :file:`lost+found`
-directories, use the following command:
-
-.. code-block:: mysql
-
-  mysql> set tokudb_backup_exclude='/lost\\+found($|/)';
-
-For more information see :ref:`toku_backup`.
-
-.. _tokudb_backup_last_error:
-
-.. rubric:: ``tokudb_backup_last_error``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - Yes
-   * - Config file
-     - Yes
-   * - Scope
-     - Session, Global
-   * - Dynamic
-     - Yes
-   * - Data type
-     - Numeric
-   * - Default
-     - 0
-
-This session variable will contain the error number from the last backup.
-``0`` indicates success. For more information see :ref:`toku_backup`.
-
-.. _tokudb_backup_last_error_string:
-
-.. rubric:: ``tokudb_backup_last_error_string``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - Yes
-   * - Config file
-     - Yes
-   * - Scope
-     - Session, Global
-   * - Dynamic
-     - Yes
-   * - Data type
-     - String
-   * - Default
-     - NULL
-
-This session variable will contain the error string from the last backup. For
-more information see :ref:`toku_backup`.
-
-.. _tokudb_backup_plugin_version:
-
-.. rubric:: ``tokudb_backup_plugin_version``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - No
-   * - Config file
-     - No
-   * - Scope
-     - Global
-   * - Dynamic
-     - No
-   * - Data type
-     - String 
-
-This read-only server variable documents the version of the *TokuBackup*
-plugin. For more information see :ref:`toku_backup`.
-
-.. _tokudb_backup_throttle:
-
-.. rubric:: ``tokudb_backup_throttle``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - Yes
-   * - Config file
-     - Yes
-   * - Scope
-     - Session, Global
-   * - Dynamic
-     - Yes
-   * - Data type
-     - Numeric
-   * - Default
-     - 18446744073709551615
-
-This variable specifies the maximum number of bytes per second the copier of a
-hot backup process will consume. Lowering its value will cause the hot backup
-operation to take more time but consume less I/O on the server. The default
-value is ``18446744073709551615`` which means no throttling. For more
-information see :ref:`toku_backup`.
-
-.. _tokudb_backup_version:
-
-.. rubric:: ``tokudb_backup_version``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - No
-   * - Config file
-     - No
-   * - Scope
-     - Global
-   * - Dynamic
-     - No
-   * - Data type
-     - String
-
-This read-only server variable documents the version of the hot backup library. For more information see :ref:`toku_backup`.
-
-.. _tokudb_block_size:
-
-.. rubric:: ``tokudb_block_size``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - Yes
-   * - Config file
-     - Yes
-   * - Scope
-     - Session, Global
-   * - Dynamic
-     - Yes
-   * - Data type
-     - Numeric
-   * - Default
-     - 512 MB
-   * - Range
-     - 4096 - 4294967295
-
-This variable controls the maximum size of node in memory before messages
-must be flushed or node must be split.
-
-Changing the value of :ref:`tokudb_block_size` only affects subsequently
-created tables and indexes. The value of this variable cannot be changed for an
-existing table/index without a dump and reload.
-
-.. _tokudb_bulk_fetch:
-
-.. rubric:: ``tokudb_bulk_fetch``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - Yes
-   * - Config file
-     - Yes
-   * - Scope
-     - Session, Global
-   * - Dynamic
-     - Yes
-   * - Data type
-     - Boolean
-   * - Default
-     - ON
-
-This variable determines if our bulk fetch algorithm is used for ``SELECT``
-statements. ``SELECT`` statements include pure ``SELECT ...`` statements, as
-well as ``INSERT INTO table-name ... SELECT ...``, ``CREATE TABLE table-name
-... SELECT ...``, ``REPLACE INTO table-name ... SELECT ...``, ``INSERT IGNORE
-INTO table-name ... SELECT ...``, and ``INSERT INTO table-name ... SELECT ...
-ON DUPLICATE KEY UPDATE``.
-
-.. _tokudb_cache_size:
-
-.. rubric:: ``tokudb_cache_size``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - Yes
-   * - Config file
-     - Yes
-   * - Scope
-     - Global
-   * - Dynamic
-     - No
-   * - Data type
-     - Numeric
-
-This variable configures the size in bytes of the *TokuDB* cache table. The
-default cache table size is 1/2 of physical memory. Percona highly recommends
-using the default setting if using buffered I/O, if using direct I/O then
-consider setting this parameter to 80% of available memory.
-
-Consider decreasing :ref:`tokudb_cache_size` if excessive swapping is
-causing performance problems. Swapping may occur when running multiple *MySQL* server instances or if other running applications use large amounts of physical
-memory.
-
-.. _tokudb_cachetable_pool_threads:
-
-.. rubric:: ``tokudb_cachetable_pool_threads``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - Yes
-   * - Config file
-     - Yes
-   * - Scope
-     - Global
-   * - Dynamic
-     - Yes
-   * - Data type
-     - Numeric
-   * - Default
-     - 0
-   * - Range
-     - 0 - 1024
-
-This variable defines the number of threads for the cachetable worker thread
-pool. This pool is used to perform node prefetches, and to serialize, compress,
-and write nodes during cachetable eviction. The default value of 0 calculates
-the pool size to be num_cpu_threads * 2.
-
-.. _tokudb_check_jemalloc:
-
-.. rubric:: ``tokudb_check_jemalloc``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - Yes
-   * - Config file
-     - Yes
-   * - Scope
-     - Global
-   * - Dynamic
-     - No
-   * - Data type
-     - Boolean
-   * - Default
-     - OFF
-
-This variable enables/disables startup checking if jemalloc is linked and
-correct version and that transparent huge pages are disabled. Used for
-testing only.
-
-.. _tokudb_checkpoint_lock:
-
-.. rubric:: ``tokudb_checkpoint_lock``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - Yes
-   * - Config file
-     - Yes
-   * - Scope
-     - Session, Global
-   * - Dynamic
-     - Yes
-   * - Data type
-     - Boolean
-   * - Default
-     - OFF
-
-Disables checkpointing when true. Session variable but acts like a global, any
-session disabling checkpointing disables it globally. If a session sets this
-lock and disconnects or terminates for any reason, the lock will not be
-released. Special purpose only, do **not** use this in your application.
-
-.. _tokudb_checkpoint_on_flush_logs:
-
-.. rubric:: ``tokudb_checkpoint_on_flush_logs``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - Yes
-   * - Config file
-     - Yes
-   * - Scope
-     - Global
-   * - Dynamic
-     - Yes
-   * - Data type
-     - Boolean
-   * - Default
-     - OFF
-
-When enabled forces a checkpoint if we get a flush logs command from the
-server.
-
-.. _tokudb_checkpoint_pool_threads:
-
-.. rubric:: ``tokudb_checkpoint_pool_threads``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - Yes
-   * - Config file
-     - Yes
-   * - Scope
-     - 
-   * - Dynamic
-     - No
-   * - Data type
-     - Numeric
-   * - Default
-     - 0
-   * - Range 
-     - 0 - 1024
-
-This defines the number of threads for the checkpoint worker thread pool. This
-pool is used to serialize, compress and write nodes cloned during checkpoint.
-Default of ``0`` uses old algorithm to set pool size to ``num_cpu_threads/4``.
-
-.. _tokudb_checkpointing_period:
-
-.. rubric:: ``tokudb_checkpointing_period``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - Yes
-   * - Config file
-     - Yes
-   * - Scope
-     - Global
-   * - Dynamic
-     - Yes
-   * - Data type
-     - Numeric
-   * - Default
-     - 60
-   * - Range 
-     - 0 - 4294967295
-
-This variable specifies the time in seconds between the beginning of one
-checkpoint and the beginning of the next. The default time between *TokuDB*
-checkpoints is 60 seconds. We recommend leaving this variable unchanged.
-
-.. _tokudb_cleaner_iterations:
-
-.. rubric:: ``tokudb_cleaner_iterations``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - Yes
-   * - Config file
-     - Yes
-   * - Scope
-     - Global
-   * - Dynamic
-     - Yes
-   * - Data type
-     - Numeric
-   * - Default
-     - 5
-   * - Range
-     - 0 - 18446744073709551615
-
-This variable specifies how many internal nodes get processed in each
-:ref:`tokudb_cleaner_period` period. The default value is ``5``. Setting
-this variable to ``0`` turns off cleaner threads.
-
-.. _tokudb_cleaner_period:
-
-.. rubric:: ``tokudb_cleaner_period``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - Yes
-   * - Config file
-     - Yes
-   * - Scope
-     - Global
-   * - Dynamic
-     - Yes
-   * - Data type
-     - Numeric
-   * - Default
-     - 1
-   * - Range
-     - 0 - 18446744073709551615
-
-This variable specifies how often in seconds the cleaner thread runs. The
-default value is ``1``. Setting this variable to ``0`` turns off cleaner
-threads.
-
-.. _tokudb_client_pool_threads:
-
-.. rubric:: ``tokudb_client_pool_threads``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - Yes
-   * - Config file
-     - Yes
-   * - Scope
-     - Global
-   * - Dynamic
-     - No
-   * - Data type
-     - Numeric
-   * - Default
-     - 0
-   * - Range
-     - 0 - 1024
-
-This variable defines the number of threads for the client operations thread
-pool. This pool is used to perform node maintenance on over/undersized nodes
-such as message flushing down the tree, node splits, and node merges. Default
-of ``0`` uses old algorithm to set pool size to ``1 * num_cpu_threads``.
-
-.. _tokudb_commit_sync:
-
-.. rubric:: ``tokudb_commit_sync``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - Yes
-   * - Config file
-     - Yes
-   * - Scope
-     - Session, Global
-   * - Dynamic
-     - Yes
-   * - Data type
-     - Boolean
-   * - Default
-     - ON
-
-Session variable :ref:`tokudb_commit_sync` controls whether or not the
-transaction log is flushed when a transaction commits. The default behavior is
-that the transaction log is flushed by the commit. Flushing the transaction log
-requires a disk write and may adversely affect the performance of your
-application.
-
-To disable synchronous flushing of the transaction log, disable the
-:ref:`tokudb_commit_sync` session variable as follows:
-
-.. code-block:: mysql
-
-  SET tokudb_commit_sync=OFF;
-
-Disabling this variable may make the system run faster. However, transactions
-committed since the last checkpoint are not guaranteed to survive a crash.
-
-.. warning::
-
-  By disabling this variable and/or setting the
-  :ref:`tokudb_fsync_log_period` to non-zero value you have effectively
-  downgraded the durability of the storage engine. If you were to have a crash
-  in this same window, you would lose data. The same issue would also appear if
-  you were using some kind of volume snapshot for backups.
-
-.. _tokudb_compress_buffers_before_eviction:
-
-.. rubric:: ``tokudb_compress_buffers_before_eviction``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - Yes
-   * - Config file
-     - Yes
-   * - Scope
-     - Global
-   * - Dynamic
-     - No
-   * - Data type
-     - Boolean
-   * - Default
-     - ON
-
-When this variable is enabled it allows the evictor to compress unused
-internal node partitions in order to reduce memory requirements as a first step
-of partial eviction before fully evicting the partition and eventually the
-entire node.
-
-.. _tokudb_create_index_online:
-
-.. rubric:: ``tokudb_create_index_online``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - Yes
-   * - Config file
-     - Yes
-   * - Scope
-     - Session, Global
-   * - Dynamic
-     - Yes
-   * - Data type
-     - Boolean
-   * - Default
-     - ON
-     - 
-This variable controls whether indexes created with the ``CREATE INDEX``
-command are hot (if enabled), or offline (if disabled). Hot index creation
-means that the table is available for inserts and queries while the index is
-being created. Offline index creation means that the table is not available for
-inserts and queries while the index is being created.
-
-.. note:: Hot index creation is slower than offline index creation.
-
-.. _tokudb_data_dir:
-
-.. rubric:: ``tokudb_data_dir``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - Yes
-   * - Config file
-     - Yes
-   * - Scope
-     - Global
-   * - Dynamic
-     - No
-   * - Data type
-     - String
-   * - Default
-     - ``NULL``
-
-This variable configures the directory name where the *TokuDB* tables are
-stored. The default value is ``NULL`` which uses the location of the *MySQL*
-data directory. For more information check :ref:`tokudb_files_and_file_types`
-and :ref:`tokudb_file_management`.
-
-.. _tokudb_debug:
-
-.. rubric:: ``tokudb_debug``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - Yes
-   * - Config file
-     - Yes
-   * - Scope
-     - Global
-   * - Dynamic
-     - Yes
-   * - Data type
-     - Numeric
-   * - Default
-     - 0
-   * - Range
-     - 0 - 18446744073709551615
-
-This variable enables mysqld debug printing to ``STDERR`` for *TokuDB*.
-Produces tremendous amounts of output that is nearly useless to anyone but a
-*TokuDB* developer, not recommended for any production use at all. It is a mask
-value ``ULONG``::
-
-  #define TOKUDB_DEBUG_INIT                   (1<<0)
-  #define TOKUDB_DEBUG_OPEN                   (1<<1)
-  #define TOKUDB_DEBUG_ENTER                  (1<<2)
-  #define TOKUDB_DEBUG_RETURN                 (1<<3)
-  #define TOKUDB_DEBUG_ERROR                  (1<<4)
-  #define TOKUDB_DEBUG_TXN                    (1<<5)
-  #define TOKUDB_DEBUG_AUTO_INCREMENT         (1<<6)
-  #define TOKUDB_DEBUG_INDEX_KEY              (1<<7)
-  #define TOKUDB_DEBUG_LOCK                   (1<<8)
-  #define TOKUDB_DEBUG_CHECK_KEY              (1<<9)
-  #define TOKUDB_DEBUG_HIDE_DDL_LOCK_ERRORS   (1<<10)
-  #define TOKUDB_DEBUG_ALTER_TABLE            (1<<11)
-  #define TOKUDB_DEBUG_UPSERT                 (1<<12)
-  #define TOKUDB_DEBUG_CHECK                  (1<<13)
-  #define TOKUDB_DEBUG_ANALYZE                (1<<14)
-  #define TOKUDB_DEBUG_XA                     (1<<15)
-  #define TOKUDB_DEBUG_SHARE                  (1<<16)
-
-.. _tokudb_dir_per_db:
-
-.. rubric:: ``tokudb_dir_per_db``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - Yes
-   * - Config file
-     - Yes
-   * - Scope
-     - Global
-   * - Dynamic
-     - Yes
-   * - Data type
-     - Boolean
-   * - Default
-     - ON
-
-When this variable is set to ``ON`` all new tables and indices will be placed
-within their corresponding database directory within the
-:ref:`tokudb_data_dir` or system `datadir`. Existing table files will not be automatically relocated to their corresponding database directory.
-If you rename a table, while this variable is enabled, the mapping in the
-*Percona FT* directory file will be updated and the files will be renamed on
-disk to reflect the new table name. For more information check
-:ref:`tokudb_files_and_file_types` and :ref:`tokudb_file_management`.
-
-.. _tokudb_directio:
-
-.. rubric:: ``tokudb_directio``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - Yes
-   * - Config file
-     - Yes
-   * - Scope
-     - Global
-   * - Dynamic
-     - No
-   * - Data type
-     - Boolean
-   * - Default
-     - OFF
-
-When enabled, TokuDB employs Direct I/O rather than Buffered I/O for writes.
-When using Direct I/O, consider increasing :ref:`tokudb_cache_size` from its default of 1/2 physical memory.
-
-.. _tokudb_disable_hot_alter:
-
-.. rubric:: ``tokudb_disable_hot_alter``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - Yes
-   * - Config file
-     - Yes
-   * - Scope
-     - Session, Global
-   * - Dynamic
-     - Yes
-   * - Data type
-     - Boolean
-   * - Default
-     - OFF
-
-This variable is used specifically for testing or to disable hot alter in case
-there are bugs. Not for use in production.
-
-.. _tokudb_disable_prefetching:
-
-.. rubric:: ``tokudb_disable_prefetching``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - Yes
-   * - Config file
-     - Yes
-   * - Scope
-     - Session, Global
-   * - Dynamic
-     - Yes
-   * - Data type
-     - Boolean
-   * - Default
-     - OFF
-
-*TokuDB* attempts to aggressively prefetch additional blocks of rows, which is
-helpful for most range queries but may create unnecessary I/O for range queries
-with ``LIMIT`` clauses. Prefetching is ``ON`` by default, with a value of
-``0``, it can be disabled by setting this variable to ``1``.
-
-.. _tokudb_disable_slow_alter:
-
-.. rubric:: ``tokudb_disable_slow_alter``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - Yes
-   * - Config file
-     - Yes
-   * - Scope
-     - Session, Global
-   * - Dynamic
-     - Yes
-   * - Data type
-     - Boolean
-   * - Default
-     - OFF
-
-This variable is used specifically for testing or to disable hot alter in case
-there are bugs. Not for use in production. It controls whether slow alter
-tables are allowed. For example, the following command is slow because
-``HCADER`` does not allow a mixture of column additions, deletions, or
-expansions:
-
-.. code-block:: mysql
-
-  ALTER TABLE table
-  ADD COLUMN column_a INT,
-  DROP COLUMN column_b;
-
-By default, :ref:`tokudb_disable_slow_alter` is disabled, and the engine
-reports back to MySQL that this is unsupported resulting in the following output:
-
-.. code-block:: text
-
-  ERROR 1112 (42000): Table 'test_slow' uses an extension that doesn't exist in this MySQL version
-
-.. _tokudb_empty_scan:
-
-.. rubric:: ``tokudb_empty_scan``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - Yes
-   * - Config file
-     - Yes
-   * - Scope
-     - Global/Session
-   * - Dynamic
-     - Yes
-   * - Data type
-     - ENUM
-   * - Default
-     - ``rl``
-  *  - Range
-     - ``disabled``, ``rl`` - right to left, ``lr`` - left to right
-
-Defines direction to be used to perform table scan to check for empty tables
-for bulk loader.
-
-.. _tokudb_enable_fast_update:
-
-.. rubric:: ``tokudb_enable_fast_update``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - Yes
-   * - Config file
-     - Yes
-   * - Scope
-     - Global/Session
-   * - Dynamic
-     - Yes
-   * - Data type
-     - Boolean
-   * - Default
-     - OFF
-
-Toggles the fast updates feature ON/OFF for the ``UPDATE`` statement. Fast
-update involves queries optimization to avoid random reads during their
-execution.
-
-.. _tokudb_enable_fast_upsert:
-
-.. rubric:: ``tokudb_enable_fast_upsert``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - Yes
-   * - Config file
-     - Yes
-   * - Scope
-     - Global/Session
-   * - Dynamic
-     - Yes
-   * - Data type
-     - Boolean
-   * - Default
-     - OFF
-
-Toggles the fast updates feature ON/OFF for the ``INSERT`` statement. Fast
-update involves queries optimization to avoid random reads during their
-execution.
-
-.. _tokudb_enable_partial_eviction:
-
-.. rubric:: ``tokudb_enable_partial_eviction``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - Yes
-   * - Config file
-     - Yes
-   * - Scope
-     - Global
-   * - Dynamic
-     - No
-   * - Data type
-     - Boolean
-   * - Default
-     - OFF
-
-This variable is used to control if partial eviction of nodes is enabled or
-disabled.
-
-.. _tokudb_fanout:
-
-.. rubric:: ``tokudb_fanout``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - Yes
-   * - Config file
-     - Yes
-   * - Scope
-     - Session, Global
-   * - Dynamic
-     - Yes
-   * - Data type
-     - Numeric
-   * - Default
-     - 16
-   * - Range
-     - 2-16384
-
-This variable controls the Fractal Tree fanout. The fanout defines the number
-of pivot keys or child nodes for each internal tree node.
-Changing the value of :ref:`tokudb_fanout` only affects subsequently
-created tables and indexes. The value of this variable cannot be changed for an
-existing table/index without a dump and reload.
-
-.. _tokudb_fs_reserve_percent:
-
-.. rubric:: ``tokudb_fs_reserve_percent``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - Yes
-   * - Config file
-     - Yes
-   * - Scope
-     - Global
-   * - Dynamic
-     - No
-   * - Data type
-     - Numeric
-   * - Default
-     - 5
-   * - Range
-     - 0-100
-
-This variable controls the percentage of the file system that must be available
-for inserts to be allowed. By default, this is set to ``5``. We recommend that
-this reserve be at least half the size of your physical memory. See :ref:`Full
-Disks <tokudb_full_disks>` for more information.
-
-.. _tokudb_fsync_log_period:
-
-.. rubric:: ``tokudb_fsync_log_period``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - Yes
-   * - Config file
-     - Yes
-   * - Scope
-     - Global
-   * - Dynamic
-     - Yes
-   * - Data type
-     - Numeric
-   * - Default
-     - 0
-   * - Range
-     - 0-4294967295
-
-This variable controls the frequency, in milliseconds, for ``fsync()``
-operations. If set to ``0`` then the ``fsync()`` behavior is only controlled by
-the :ref:`tokudb_commit_sync`, which can be ``ON`` or ``OFF``.
-
-.. _tokudb_hide_default_row_format:
-
-.. rubric:: ``tokudb_hide_default_row_format``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - Yes
-   * - Config file
-     - Yes
-   * - Scope
-     - Session, Global
-   * - Dynamic
-     - Yes
-   * - Data type
-     - Boolean
-   * - Default
-     - ON
-
-This variable is used to hide the ``ROW_FORMAT`` in ``SHOW CREATE TABLE``. If
-``zlib`` compression is used, row format will show as ``DEFAULT``.
-
-.. _tokudb_killed_time:
-
-.. rubric:: ``tokudb_killed_time``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - Yes
-   * - Config file
-     - Yes
-   * - Scope
-     - Session, Global
-   * - Dynamic
-     - Yes
-   * - Data type
-     - Numeric
-   * - Default
-     - 4000
-   * - Range
-     - 0-18446744073709551615
-
-This variable is used to specify frequency in milliseconds for lock wait to
-check to see if the lock was killed.
-
-.. _tokudb_last_lock_timeout:
-
-.. rubric:: ``tokudb_last_lock_timeout``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - Yes
-   * - Config file
-     - Yes
-   * - Scope
-     - Session, Global
-   * - Dynamic
-     - Yes
-   * - Data type
-     - String
-   * - Default
-     - NULL
-
-This variable contains a JSON document that describes the last lock conflict
-seen by the current *MySQL* client. It gets set when a blocked lock request
-times out or a lock deadlock is detected.
-
-The :ref:`tokudb_lock_timeout_debug` session variable must have bit ``0``
-set for this behavior, otherwise this session variable will be empty.
-
-.. _tokudb_load_save_space:
-
-.. rubric:: ``tokudb_load_save_space``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - Yes
-   * - Config file
-     - Yes
-   * - Scope
-     - Session, Global
-   * - Dynamic
-     - Yes
-   * - Data type
-     - Boolean
-   * - Default
-     - ON
-
-This session variable changes the behavior of the bulk loader. When it is
-disabled the bulk loader stores intermediate data using uncompressed files
-(which consumes additional CPU), whereas ``ON`` compresses the intermediate
-files.
-
-.. note::
-
-  The location of the temporary disk space used by the bulk loader may be
-  specified with the :ref:`tokudb_tmp_dir` server variable.
-
-If a ``LOAD DATA INFILE`` statement fails with the error message ``ERROR 1030
-(HY000): Got error 1`` from storage engine, then there may not be enough disk
-space for the optimized loader, so disable :ref:`tokudb_prelock_empty` and
-try again. More information is available in :ref:`Known Issues
-<tokudb_known_issues>`.
-
-.. _tokudb_loader_memory_size:
-
-.. rubric:: ``tokudb_loader_memory_size``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - Yes
-   * - Config file
-     - Yes
-   * - Scope
-     - Session, Global
-   * - Dynamic
-     - Yes
-   * - Data type
-     - Numeric
-   * - Default
-     - 100000000
-   * - Range
-     - 0-18446744073709551615
-
-This variable limits the amount of memory (in bytes) that the *TokuDB* bulk
-loader will use for each loader instance. Increasing this value may provide
-a performance benefit when loading extremely large tables with several
-secondary indexes.
-
-.. note::
-
-  Memory allocated to a loader is taken from the TokuDB cache, defined in
-  :ref:`tokudb_cache_size`, and may impact the running workload's
-  performance as existing cached data must be ejected for the loader to begin.
-
-.. _tokudb_lock_timeout:
-
-.. rubric:: ``tokudb_lock_timeout``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - Yes
-   * - Config file
-     - Yes
-   * - Scope
-     - Session, Global
-   * - Dynamic
-     - Yes
-   * - Data type
-     - Numeric
-   * - Default
-     - 4000
-   * - Range
-     - 0-18446744073709551615
-
-This variable controls the amount of time that a transaction will wait for a
-lock held by another transaction to be released. If the conflicting transaction
-does not release the lock within the lock timeout, the transaction that was
-waiting for the lock will get a lock timeout error. The units are milliseconds.
-A value of ``0`` disables lock waits. The default value is 4000 (four seconds).
-
-If your application gets a ``lock wait timeout`` error (-30994), then you may
-find that increasing the :ref:`tokudb_lock_timeout` may help. If your
-application gets a ``deadlock found`` error (-30995), then you need to abort
-the current transaction and retry it.
-
-.. _tokudb_lock_timeout_debug:
-
-.. rubric:: ``tokudb_lock_timeout_debug``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - Yes
-   * - Config file
-     - Yes
-   * - Scope
-     - Session, Global
-   * - Dynamic
-     - Yes
-   * - Data type
-     - Numeric
-   * - Default
-     - 1
-   * - Range
-     - 0-3
-
-The following values are available:
-
-  * ``0``: No lock timeouts or lock deadlocks are reported.
-
-  * ``1``: A JSON document that describes the lock conflict is stored in the
-    :ref:`tokudb_last_lock_timeout` session variable
-
-  * ``2``: A JSON document that describes the lock conflict is printed to the
-    MySQL error log.
-
-      In addition to the JSON document describing the lock conflict, the
-      following lines are printed to the MySQL error log:
-
-      * A line containing the blocked thread id and blocked SQL
-      * A line containing the blocking thread id and the blocking SQL.
-
-  * ``3``: A JSON document that describes the lock conflict is stored in the
-    :ref:`tokudb_last_lock_timeout` session variable and is printed to the
-    MySQL error log.
-
-      In addition to the JSON document describing the lock conflict, the
-      following lines are printed to the MySQL error log:
-
-      * A line containing the blocked thread id and blocked SQL
-      * A line containing the blocking thread id and the blocking SQL.
-
-.. _tokudb_log_dir:
-
-.. rubric:: ``tokudb_log_dir``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - Yes
-   * - Config file
-     - Yes
-   * - Scope
-     - Global
-   * - Dynamic
-     - No
-   * - Data type
-     - String
-   * - Default
-     - NULL
-
-This variable specifies the directory where the *TokuDB* log files are stored.
-The default value is ``NULL`` which uses the location of the *MySQL* data
-directory. Configuring a separate log directory is somewhat involved. Please
-contact Percona support for more details. For more information check
-:ref:`tokudb_files_and_file_types` and :ref:`tokudb_file_management`.
-
-.. warning::
-
-  After changing *TokuDB* log directory path, the old *TokuDB* recovery log
-  file should be moved to new directory prior to start of *MySQL* server and
-  log file's owner must be the ``mysql`` user. Otherwise server will fail to
-  initialize the *TokuDB* store engine restart.
-
-.. _tokudb_max_lock_memory:
-
-.. rubric:: ``tokudb_max_lock_memory``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - Yes
-   * - Config file
-     - Yes
-   * - Scope
-     - Global
-   * - Dynamic
-     - No
-   * - Data type
-     - Numeric
-   * - Default
-     - 65560320
-   * - Range
-     - 0-18446744073709551615
-
-This variable specifies the maximum amount of memory for the PerconaFT lock
-table.
-
-.. _tokudb_optimize_index_fraction:
-
-.. rubric:: ``tokudb_optimize_index_fraction``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - Yes
-   * - Config file
-     - Yes
-   * - Scope
-     - Session, Global
-   * - Dynamic
-     - Yes
-   * - Data type
-     - Numeric
-   * - Default
-     - 1.000000
-   * - Range
-     - 0.000000 - 1.000000
-
-For patterns where the left side of the tree has many deletions (a common
-pattern with increasing id or date values), it may be useful to delete a
-percentage of the tree. In this case, it's possible to optimize a subset of a
-fractal tree starting at the left side. The
-:ref:`tokudb_optimize_index_fraction` session variable controls the size
-of the sub tree. Valid values are in the range [0.0,1.0] with default 1.0
-(optimize the whole tree).
-
-.. _tokudb_optimize_index_name:
-
-.. rubric:: ``tokudb_optimize_index_name``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - Yes
-   * - Config file
-     - Yes
-   * - Scope
-     - Session, Global
-   * - Dynamic
-     - Yes
-   * - Data type
-     - String
-   * - Default
-     - NULL
-
-This variable can be used to optimize a single index in a table, it can be set
-to select the index by name.
-
-.. _tokudb_optimize_throttle:
-
-.. rubric:: ``tokudb_optimize_throttle``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - Yes
-   * - Config file
-     - Yes
-   * - Scope
-     - Session, Global
-   * - Dynamic
-     - Yes
-   * - Data type
-     - Numeric
-   * - Default
-     - 0
-   * - Range
-     - 0-18446744073709551615
-
-By default, table optimization will run with all available resources. To limit
-the amount of resources, it is possible to limit the speed of table
-optimization. This determines an upper bound on how many fractal tree leaf
-nodes per second are optimized. The default ``0`` imposes no limit.
-
-.. _tokudb_pk_insert_mode:
-
-.. rubric:: ``tokudb_pk_insert_mode``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - Yes
-   * - Config file
-     - Yes
-   * - Scope
-     - Session, Global
-   * - Dynamic
-     - Yes
-   * - Data type
-     - Numeric
-   * - Default
-     - 1
-   * - Range
-     - 0-3
-
-.. note::
-
-  The :ref:`tokudb_pk_insert_mode` session variable was removed
-  and the behavior is now that of the former
-  :ref:`tokudb_pk_insert_mode` set to ``1``. The optimization
-  will be used where safe and not used where not safe.
-
-.. _tokudb_prelock_empty:
-
-.. rubric:: ``tokudb_prelock_empty``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - Yes
-   * - Config file
-     - Yes
-   * - Scope
-     - Session, Global
-   * - Dynamic
-     - Yes
-   * - Data type
-     - Boolean
-   * - Default
-     - ON
-
-By default *TokuDB* preemptively grabs an entire table lock on empty tables. If
-one transaction is doing the loading, such as when the user is doing a table
-load into an empty table, this default provides a considerable speedup.
-
-However, if multiple transactions try to do concurrent operations on an empty
-table, all but one transaction will be locked out. Disabling
-:ref:`tokudb_prelock_empty` optimizes for this multi-transaction case by
-turning off preemptive pre-locking.
-
-.. note::
-
-  If this variable is set to ``OFF``, fast bulk loading is turned off as well.
-
-.. _tokudb_read_block_size:
-
-.. rubric:: ``tokudb_read_block_size``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - Yes
-   * - Config file
-     - Yes
-   * - Scope
-     - Session, Global
-   * - Dynamic
-     - Yes
-   * - Data type
-     - Numeric
-   * - Default
-     - 16384 (16KB)
-   * - Range
-     - 4096 - 4294967295
-
-Fractal tree leaves are subdivided into read blocks, in order to speed up point
-queries. This variable controls the target uncompressed size of the read
-blocks. The units are bytes and the default is 64 KB. A smaller value
-favors read performance for point and small range scans over large range scans
-and higher compression. The minimum value of this variable is 4096 (4KB).
-
-Changing the value of :ref:`tokudb_read_block_size` only affects
-subsequently created tables. The value of this variable cannot be changed for
-an existing table without a dump and reload.
-
-.. _tokudb_read_buf_size:
-
-.. rubric:: ``tokudb_read_buf_size``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - Yes
-   * - Config file
-     - Yes
-   * - Scope
-     - Session, Global
-   * - Dynamic
-     - Yes
-   * - Data type
-     - Numeric
-   * - Default
-     - 131072 (128KB)
-   * - Range
-     - 0 - 1048576
-
-This variable controls the size of the buffer used to store values that are
-bulk fetched as part of a large range query. Its unit is bytes and its default
-value is 131,072 (128 KB).
-
-A value of ``0`` turns off bulk fetching. Each client keeps a thread of this
-size, so it should be lowered if situations where there are a large number of
-clients simultaneously querying a table.
-
-.. _tokudb_read_status_frequency:
-
-.. rubric:: ``tokudb_read_status_frequency``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - Yes
-   * - Config file
-     - Yes
-   * - Scope
-     - Global
-   * - Dynamic
-     - Yes
-   * - Data type
-     - Numeric
-   * - Default
-     - 10000
-   * - Range
-     - 0 - 4294967295
-
-This variable controls in how many reads the progress is measured to display
-``SHOW PROCESSLIST``. Reads are defined as ``SELECT`` queries.
-
-For slow queries, it can be helpful to set this variable and
-:ref:`tokudb_write_status_frequency` to ``1``, and then run ``SHOW
-PROCESSLIST`` several times to understand what progress is being made.
-
-.. _tokudb_row_format:
-
-.. rubric:: ``tokudb_row_format``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - Yes
-   * - Config file
-     - Yes
-   * - Scope
-     - Session, Global
-   * - Dynamic
-     - Yes
-   * - Data type
-     - ENUM
-   * - Default
-     - ``TOKUDB_QUICKLZ``
-   * - Range
-     - ``TOKUDB_DEFAULT``, ``TOKUDB_FAST``, ``TOKUDB_SMALL``, ``TOKUDB_ZLIB``, ``TOKUDB_QUICKLZ``, ``TOKUDB_LZMA``, ``TOKUDB_SNAPPY``, ``TOKUDB_UNCOMPRESSED``
-
-This controls the default compression algorithm used to compress data. For more information
-on compression algorithms see :ref:`Compression Details <tokudb_compression>`.
-
-.. _tokudb_rpl_check_readonly:
-
-.. rubric:: ``tokudb_rpl_check_readonly``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - Yes
-   * - Config file
-     - Yes
-   * - Scope
-     - Session, Global
-   * - Dynamic
-     - Yes
-   * - Data type
-     - Boolean
-   * - Default
-     - ON
-
-The *TokuDB* replication code will run row events from the binary log with
-:ref:`tokudb_read_free_replication` when the replica is in read-only mode. This
-variable is used to disable the replica read only check in the *TokuDB*
-replication code.
-
-This allows Read-Free-Replication to run when the replica is NOT read-only. By
-default, :ref:`tokudb_rpl_check_readonly` is enabled (check that replica is
-read-only). Do **NOT** change this value unless you completely understand the
-implications!
-
-.. _tokudb_rpl_lookup_rows:
-
-.. rubric:: ``tokudb_rpl_lookup_rows``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - Yes
-   * - Config file
-     - Yes
-   * - Scope
-     - Session, Global
-   * - Dynamic
-     - Yes
-   * - Data type
-     - Boolean
-   * - Default
-     - ON
-
-When disabled, *TokuDB* replication replicas skip row lookups for ``delete row``
-log events and ``update row`` log events, which eliminates all associated read
-I/O for these operations.
-
-.. warning::
-
-  *TokuDB* :ref:`tokudb_read_free_replication` will not propagate ``UPDATE``
-  and ``DELETE`` events reliably if *TokuDB* table is missing the primary key
-  which will eventually lead to data inconsistency on the replica.
-
-.. note::
-
-  Optimization is only enabled when :ref:`read_only` is set to ``1`` and
-  :ref:`binlog_format` is ``ROW``.
-
-.. _tokudb_rpl_lookup_rows_delay:
-
-.. rubric:: ``tokudb_rpl_lookup_rows_delay``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - Yes
-   * - Config file
-     - Yes
-   * - Scope
-     - Session, Global
-   * - Dynamic
-     - Yes
-   * - Data type
-     - Numeric
-   * - Default
-     - 0
-   * - Range
-     - 0 - 18446744073709551615
-
-This variable allows for simulation of long disk reads by sleeping for the
-given number of microseconds prior to the row lookup query, it should only be
-set to a non-zero value for testing.
-
-.. _tokudb_rpl_unique_checks:
-
-.. rubric:: ``tokudb_rpl_unique_checks``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - Yes
-   * - Config file
-     - Yes
-   * - Scope
-     - Session, Global
-   * - Dynamic
-     - Yes
-   * - Data type
-     - Boolean
-   * - Default
-     - ON
-
-When disabled, *TokuDB* replication replicas skip uniqueness checks on inserts
-and updates, which eliminates all associated read I/O for these operations.
-
-.. note::
-
-  Optimization is only enabled when :ref:`read_only` is set to ``1`` and
-  :ref:`binlog_format` is ``ROW``.
-
-.. _tokudb_rpl_unique_checks_delay:
-
-.. rubric:: ``tokudb_rpl_unique_checks_delay``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - Yes
-   * - Config file
-     - Yes
-   * - Scope
-     - Session, Global
-   * - Dynamic
-     - Yes
-   * - Data type
-     - Numeric
-   * - Default
-     - 0
-   * - Range
-     - 0 - 18446744073709551615
-
-This variable allows for simulation of long disk reads by sleeping for the
-given number of microseconds prior to the row lookup query, it should only be
-set to a non-zero value for testing.
-
-.. _tokudb_strip_frm_data:
-
-.. rubric:: ``tokudb_strip_frm_data``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - Yes
-   * - Config file
-     - Yes
-   * - Scope
-     - Global
-   * - Dynamic
-     - Yes
-   * - Data type
-     - Boolean
-   * - Default
-     - OFF
-
-When this variable is set to ``ON`` during the startup server will check all
-the status files and remove the embedded :file:`.frm` metadata. This variable
-can be used to assist in *TokuDB* data recovery. **WARNING:** Use this variable
-only if you know what you're doing otherwise it could lead to data loss.
-
-.. _tokudb_support_xa:
-
-.. rubric:: ``tokudb_support_xa``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - Yes
-   * - Config file
-     - Yes
-   * - Scope
-     - Session, Global
-   * - Dynamic
-     - Yes
-   * - Data type
-     - Boolean
-   * - Default
-     - ON
-
-This variable defines whether or not the prepare phase of an XA transaction
-performs an ``fsync()``.
-
-.. _tokudb_tmp_dir:
-
-.. rubric:: ``tokudb_tmp_dir``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - Yes
-   * - Config file
-     - Yes
-   * - Scope
-     - Global
-   * - Dynamic
-     - No
-   * - Data type
-     - String
-
-This variable specifies the directory where the *TokuDB* bulk loader stores
-temporary files. The bulk loader can create large temporary files while it is
-loading a table, so putting these temporary files on a disk separate from the
-data directory can be useful.
-
-For example, it can make sense to use a high-performance disk for the
-data directory and a very inexpensive disk for the temporary
-directory. The default location for TokuDB's temporary files is the
-MySQL data directory.
-
-:ref:`tokudb_load_save_space` determines whether the data is compressed or
-not. The error message ``ERROR 1030 (HY000): Got error 1 from storage engine``
-could indicate that the disk has run out of space.
-
-For more information check :ref:`tokudb_files_and_file_types` and
-:ref:`tokudb_file_management`.
-
-.. _tokudb_version:
-
-.. rubric:: ``tokudb_version``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - No
-   * - Config file
-     - No
-   * - Scope
-     - Global
-   * - Dynamic
-     - No
-   * - Data type
-     - String
-
-This read-only variable documents the version of the *TokuDB* storage engine.
-
-.. _tokudb_write_status_frequency:
-
-.. rubric:: ``tokudb_write_status_frequency``
-
-.. list-table::
-   :header-rows: 1
-
-   * - Option
-     - Description
-   * - Command-line
-     - Yes
-   * - Config file
-     - Yes
-   * - Scope
-     - Global
-   * - Dynamic
-     - Yes
-   * - Data type
-     - Numeric
-   * - Default
-     - 1000
-   * - Range
-     - 0 - 4294967295       
-
-This variable controls in how many writes the progress is measured to display
-``SHOW PROCESSLIST``. Writes are defined as ``INSERT``, ``UPDATE`` and
-``DELETE`` queries.
-
-For slow queries, it can be helpful to set this variable and
-:ref:`tokudb_read_status_frequency` to 1, and then run ``SHOW
-PROCESSLIST`` several times to understand what progress is being made.
diff --git a/doc/source/tokudb/using_tokudb.rst b/doc/source/tokudb/using_tokudb.rst
deleted file mode 100644
index f21daf60905b..000000000000
--- a/doc/source/tokudb/using_tokudb.rst
+++ /dev/null
@@ -1,474 +0,0 @@
-.. _using_tokudb:
-
-============
-Using TokuDB
-============
-
-.. Important:: 
-
-   Starting with :ref:`8.0.28-19`, the TokuDB storage engine is no longer supported. We have removed the storage engine from the installation packages and disabled the storage engine in our binary builds.
-
-   Starting with :ref:`8.0.26-16`, the binary builds and packages include but disable the TokuDB storage engine plugins. The ``tokudb_enabled`` option and the ``tokudb_backup_enabled`` option control the state of the plugins and have a default setting of ``FALSE``. The result of attempting to load the plugins are the plugins fail to initialize and print a deprecation message.
-
-   We recommend :ref:`migrate-myrocks`. To enable the plugins to migrate to another storage engine, set the ``tokudb_enabled`` and ``tokudb_backup_enabled`` options to ``TRUE`` in your ``my.cnf`` file and restart your server instance. Then, you can load the plugins.
-
-   The TokuDB Storage Engine was `declared as deprecated <https://www.percona.com/doc/percona-server/8.0/release-notes/Percona-Server-8.0.13-3.html>`__ in Percona Server for MySQL 8.0. For more information, see the Percona blog post: `Heads-Up: TokuDB Support Changes and Future Removal from Percona Server for MySQL 8.0 <https://www.percona.com/blog/2021/05/21/tokudb-support-changes-and-future-removal-from-percona-server-for-mysql-8-0/>`__.
-
- .. warning:: 
- 
-    Do not move or modify any *TokuDB* files. You will break the database, and
-    must recover the database from a backup.
- 
-Fast Insertions and Richer Indexes
-----------------------------------
-
-TokuDB's fast indexing enables fast queries through the use of rich indexes,
-such as covering and clustering indexes. It's worth investing some time to
-optimize index definitions to get the best performance from *MySQL* and
-*TokuDB*. Here are some resources to get you started:
-
-* "Understanding Indexing" by Zardosht Kasheff (`video
-  <http://vimeo.com/26454091>`_)
-
-* `Rule of Thumb for Choosing Column Order in Indexes
-  <http://www.mysqlperformanceblog.com/2009/06/05/a-rule-of-thumb-for-choosing-column-order-in-indexes/>`_
-
-* `Covering Indexes: Orders-of-Magnitude Improvements
-  <https://www.percona.com/blog/2009/05/14/covering_indexes_orders_of_magnitude_improvements/>`_
-
-* `Introducing Multiple Clustering Indexes
-  <https://www.percona.com/blog/2009/05/27/introducing_multiple_clustering_indexes/>`_
-
-* `Clustering Indexes vs. Covering Indexes
-  <https://www.percona.com/blog/2009/05/28/clustering_indexes_vs_covering_indexes/>`_
-
-* `How Clustering Indexes Sometimes Helps UPDATE and DELETE Performance
-  <https://www.percona.com/blog/2009/06/04/how_clustering_indexes_sometimes_help_update_and_delete_performance/>`_
-
-* *High Performance MySQL, 3rd Edition* by Baron Schwartz, Peter Zaitsev, Vadim
-  Tkachenko, Copyright 2012, O'Reilly Media. See Chapter 5, *Indexing for High
-  Performance*.
-
-.. _tokudb_multiple_clustering_keys:
-
-Clustering Secondary Indexes
-----------------------------
-
-One of the keys to exploiting TokuDB's strength in indexing is to make use of
-clustering secondary indexes.
-
-*TokuDB* allows a secondary key to be defined as a clustering key. This means
-that all of the columns in the table are clustered with the secondary
-key. *Percona Server for MySQL* parser and query optimizer support Multiple Clustering
-Keys when *TokuDB* engine is used. This means that the query optimizer will
-avoid primary clustered index reads and replace them by secondary clustered
-index reads in certain scenarios.
-
-The parser has been extended to support following syntax:
-
-.. code-block:: mysql
-
-   CREATE TABLE ... ( ..., CLUSTERING KEY identifier (column list), ...
-   CREATE TABLE ... ( ..., UNIQUE CLUSTERING KEY identifier (column list), ...
-   CREATE TABLE ... ( ..., CLUSTERING UNIQUE KEY identifier (column list), ...
-   CREATE TABLE ... ( ..., CONSTRAINT identifier UNIQUE CLUSTERING KEY identifier (column list), ...
-   CREATE TABLE ... ( ..., CONSTRAINT identifier CLUSTERING UNIQUE KEY identifier (column list), ...
-   
-   CREATE TABLE ... (... column type CLUSTERING [UNIQUE] [KEY], ...)
-   CREATE TABLE ... (... column type [UNIQUE] CLUSTERING [KEY], ...)
-   
-   ALTER TABLE ..., ADD CLUSTERING INDEX identifier (column list), ...
-   ALTER TABLE ..., ADD UNIQUE CLUSTERING INDEX identifier (column list), ...
-   ALTER TABLE ..., ADD CLUSTERING UNIQUE INDEX identifier (column list), ...
-   ALTER TABLE ..., ADD CONSTRAINT identifier UNIQUE CLUSTERING INDEX identifier (column list), ...
-   ALTER TABLE ..., ADD CONSTRAINT identifier CLUSTERING UNIQUE INDEX identifier (column list), ...
-   
-   CREATE CLUSTERING INDEX identifier ON ...
-
-To define a secondary index as clustering, simply add the word ``CLUSTERING``
-before the key definition. For example:
-
-.. code-block:: mysql
-
-   CREATE TABLE foo (
-     column_a INT,
-     column_b INT,
-     column_c INT,
-     PRIMARY KEY index_a (column_a),
-     CLUSTERING KEY index_b (column_b)) ENGINE = TokuDB;
-
-In the previous example, the primary table is indexed on
-*column_a*. Additionally, there is a secondary clustering index (named
-*index_b*) sorted on *column_b*. Unlike non-clustered indexes, clustering
-indexes include all the columns of a table and can be used as covering
-indexes. For example, the following query will run very fast using the
-clustering *index_b*:
-
-.. code-block:: mysql
-
- SELECT column_c
-   FROM foo
-   WHERE column_b BETWEEN 10 AND 100;
-
-This index is sorted on *column_b*, making the ``WHERE`` clause fast, and
-includes *column_c*, which avoids lookups in the primary table to satisfy the
-query.
-
-*TokuDB* makes clustering indexes feasible because of its excellent compression
-and very high indexing rates. For more information about using clustering
-indexes, see `Introducing Multiple Clustering Indexes
-<https://www.percona.com/blog/2009/05/27/introducing_multiple_clustering_indexes/>`_.
-
-Hot Index Creation
-------------------
-
-TokuDB enables you to add indexes to an existing table and still perform inserts
-and queries on that table while the index is being created.
-
-The ``ONLINE`` keyword is not used. Instead, the value of the
-:ref:`tokudb_create_index_online` client session variable is examined.
-
-Hot index creation is invoked using the ``CREATE INDEX`` command after setting
-:ref:`tokudb_create_index_online` to ``on`` as follows:
-
-.. code-block:: mysql
-
-   mysql> SET tokudb_create_index_online=on;
-   Query OK, 0 rows affected (0.00 sec)
-
-   mysql> CREATE INDEX index ON foo (field_name);
-
-Alternatively, using the ``ALTER TABLE`` command for creating an index will
-create the index offline (with the table unavailable for inserts or queries),
-regardless of the value of :ref:`tokudb_create_index_online`. The only way
-to hot create an index is to use the ``CREATE INDEX`` command.
-
-Hot creating an index will be slower than creating the index offline, and
-progress depends how busy the mysqld server is with other tasks. Progress of the
-index creation can be seen by using the ``SHOW PROCESSLIST`` command (in another
-client). Once the index creation completes, the new index will be used in future
-query plans.
-
-If more than one hot ``CREATE INDEX`` is issued for a particular table, the
-indexes will be created serially. An index creation that is waiting for another
-to complete will be shown as *Locked* in ``SHOW PROCESSLIST``. We recommend that
-each ``CREATE INDEX`` be allowed to complete before the next one is started.
-
-Hot Column Add, Delete, Expand, and Rename (HCADER)
----------------------------------------------------
-
-*TokuDB* enables you to add or delete columns in an existing table, expand
-``char``, ``varchar``, ``varbinary``, and ``integer`` type columns in an
-existing table, or rename an existing column in a table with little blocking of
-other updates and queries. HCADER typically blocks other queries with a table
-lock for no more than a few seconds. After that initial short-term table
-locking, the system modifies each row (when adding, deleting, or expanding
-columns) later, when the row is next brought into main memory from disk. For
-column rename, all the work is done during the seconds of downtime. On-disk rows
-need not be modified.
-
-To get good performance from HCADER, observe the following guidelines:
-
-* The work of altering the table for column addition, deletion, or expansion is
-  performed as subsequent operations touch parts of the Fractal Tree, both in
-  the primary index and secondary indexes.
-
-  You can force the column addition, deletion, or expansion work to be performed
-  all at once using the standard syntax of ``OPTIMIZE TABLE X``, when a column
-  has been added to, deleted from, or expanded in table X. It is important to
-  note that as of *TokuDB* version 7.1.0, ``OPTIMIZE TABLE`` is also hot, so
-  that a table supports updates and queries without blocking while an ``OPTIMIZE
-  TABLE`` is being performed. Also, a hot ``OPTIMIZE TABLE`` does not rebuild
-  the indexes, since *TokuDB* indexes do not age. Rather, they flush all
-  background work, such as that induced by a hot column addition, deletion, or
-  expansion.
-
-* Each hot column addition, deletion, or expansion operation must be performed
-  individually (with its own SQL statement). If you want to add, delete, or
-  expand multiple columns use multiple statements.
-
-* Avoid adding, deleting, or expanding a column at the same time as adding or dropping an index.
-
-* The time that the table lock is held can vary. The table-locking time for
-  HCADER is dominated by the time it takes to flush dirty pages, because MySQL
-  closes the table after altering it. If a checkpoint has happened recently,
-  this operation is fast (on the order of seconds). However, if the table has
-  many dirty pages, then the flushing stage can take on the order of minutes.
-
-* Avoid dropping a column that is part of an index. If a column to be dropped is
-  part of an index, then dropping that column is slow. To drop a column that is
-  part of an index, first drop the indexes that reference the column in one
-  alter table statement, and then drop the column in another statement.
-
-* Hot column expansion operations are only supported to ``char``, ``varchar``,
-  ``varbinary``, and ``integer`` data types. Hot column expansion is not
-  supported if the given column is part of the primary key or any secondary
-  keys.
-
-* Rename only one column per statement. Renaming more than one column will
-  revert to the standard MySQL blocking behavior. The proper syntax is as
-  follows:
-
-  .. code-block:: mysql
-
-   ALTER TABLE table
-     CHANGE column_old column_new
-     DATA_TYPE REQUIRED_NESS DEFAULT
-
-  Here's an example of how that might look:
-
-  .. code-block:: mysql
-
-   ALTER TABLE table
-     CHANGE column_old column_new 
-     INT(10) NOT NULL;
-
-Notice that all of the column attributes must be specified. ``ALTER TABLE table
-CHANGE column_old column_new;`` induces a slow, blocking column rename.
-
-* Hot column rename does not support the following data types: ``TIME``,
-  ``ENUM``, ``BLOB``, ``TINYBLOB``, ``MEDIUMBLOB``, ``LONGBLOB``. Renaming
-  columns of these types will revert to the standard MySQL blocking behavior.
-
-* Temporary tables cannot take advantage of HCADER. Temporary tables are
-  typically small anyway, so altering them using the standard method is usually
-  fast.
-
-.. _tokudb_compression:
-
-Compression Details
--------------------
-
-*TokuDB* offers different levels of compression, which trade off between the
-amount of CPU used and the compression achieved. Standard compression uses less
-CPU but generally compresses at a lower level, high compression uses more CPU
-and generally compresses at a higher level. We have seen compression up to 25x
-on customer data.
-
-Compression in *TokuDB* occurs on background threads, which means that high
-compression need not slow down your database. Indeed, in some settings, we've
-seen higher overall database performance with high compression.
-
-.. note::
-
-   We recommend that users use standard compression on machines with six or
-   fewer cores, and high compression on machines with more than six cores.
-
-The ultimate choice depends on the particulars of how a database is used, and we
-recommend that users use the default settings unless they have profiled their
-system with high compression in place.
-
-The table is compressed using whichever row format is specified in the session
-variable :ref:`tokudb_row_format`. If no row format is set nor is
-:ref:`tokudb_row_format`, the ``QUICKLZ`` compression algorithm is used.
-
-The :ref:`row_format` and :ref:`tokudb_row_format` variables accept
-the following values:
-
-.. list-table::
-   :widths: 25 75
-   :header-rows: 1
-
-   * - Value
-     - Description
-   * - TOKUDB_DEFAULT 
-     - Sets the compression to the default behavior. As of TokuDB 7.1.0, the
-       default behavior is to compress using the zlib library. In the future
-       this behavior may change.
-   * - TOKUDB_FAST
-     - Sets the compression to use the ``quicklz`` library.
-   * - TOKUDB_SMALL
-     - Sets the compression to use the ``lzma`` library.
-   * - TOKUDB_ZLIB
-     - Compress using the zlib library, which provides mid-range compression and
-       CPU utilization.
-   * - TOKUDB_QUICKLZ
-     - Compress using the quicklz library, which provides light compression and
-       low CPU utilization.
-   * - TOKUDB_LZMA
-     - Compress using the lzma library, which provides the highest compression
-       and high CPU utilization.
-   * - TOKUDB_SNAPPY
-     - This compression is using `snappy <http://google.github.io/snappy/>`_
-       library and aims for very high speeds and reasonable compression.
-   * - TOKUDB_UNCOMPRESSED
-     - This setting turns off compression and is useful for tables with data
-       that cannot be compressed.
-
-.. _tokudb_read_free_replication:
-
-Read Free Replication
----------------------
-
-*TokuDB* replicas can be configured to perform significantly less read IO in order
-to apply changes from the source. By utilizing the power of Fractal Tree
-indexes:
-
-* insert/update/delete operations can be configured to eliminate
-  read-modify-write behavior and simply inject messages into the appropriate
-  Fractal Tree indexes
-
-* update/delete operations can be configured to eliminate the IO required for
-  uniqueness checking
-
-To enable Read Free Replication, the servers must be configured as follows:
-
-* On the replication source:
-
-  * Enable row based replication: set ``BINLOG_FORMAT=ROW``
-
-* On the replication replica(s):
-
-  * The replica must be in read-only mode: set ``read_only=1``
-
-  * Disable unique checks: set ``tokudb_rpl_unique_checks=0``
-
-  * Disable lookups (read-modify-write): set ``tokudb_rpl_lookup_rows=0``
-
-.. note::
-   
-   You can modify one or both behaviors on the replica(s).
-
-.. note::
-
-   As long as the source is using row based replication, this optimization is
-   available on a *TokuDB* replica. This means that it's available even if the
-   source is using *InnoDB* or *MyISAM* tables, or running non-TokuDB binaries.
-
-.. warning::
-
-   *TokuDB* Read Free Replication will not propagate ``UPDATE`` and ``DELETE``
-   events reliably if *TokuDB* table is missing the primary key which will
-   eventually lead to data inconsistency on the replica.
-
-Transactions and ACID-compliant Recovery
-----------------------------------------
-
-By default, *TokuDB* checkpoints all open tables regularly and logs all changes
-between checkpoints, so that after a power failure or system crash, *TokuDB*
-will restore all tables into their fully ACID-compliant state. That is, all
-committed transactions will be reflected in the tables, and any transaction not
-committed at the time of failure will be rolled back.
-
-The default checkpoint period is every 60 seconds, and this specifies the time
-from the beginning of one checkpoint to the beginning of the next. If a
-checkpoint requires more than the defined checkpoint period to complete, the
-next checkpoint begins immediately. It is also related to the frequency with
-which log files are trimmed, as described below. The user can induce a
-checkpoint at any time by issuing the ``FLUSH LOGS`` command. When a database is
-shut down normally it is also checkpointed and all open transactions are
-aborted. The logs are trimmed at startup.
-
-Managing Log Size
------------------
-
-*TokuDB* keeps log files back to the most recent checkpoint. Whenever a log file
-reaches 100 MB, a new log file is started. Whenever there is a checkpoint, all
-log files older than the checkpoint are discarded. If the checkpoint period is
-set to be a very large number, logs will get trimmed less frequently. This value
-is set to 60 seconds by default.
-
-*TokuDB* also keeps rollback logs for each open transaction. The size of each
-log is proportional to the amount of work done by its transaction and is stored
-compressed on disk. Rollback logs are trimmed when the associated transaction
-completes.
-
-Recovery
---------
-
-Recovery is fully automatic with *TokuDB*. *TokuDB* uses both the log files and
-rollback logs to recover from a crash. The time to recover from a crash is
-proportional to the combined size of the log files and uncompressed size of
-rollback logs. Thus, if there were no long-standing transactions open at the
-time of the most recent checkpoint, recovery will take less than a minute.
-
-Disabling the Write Cache
--------------------------
-
-When using any transaction-safe database, it is essential that you understand
-the write-caching characteristics of your hardware. *TokuDB* provides
-transaction safe (ACID compliant) data storage for *MySQL*. However, if the
-underlying operating system or hardware does not actually write data to disk
-when it says it did, the system can corrupt your database when the machine
-crashes. For example, *TokuDB* can not guarantee proper recovery if it is
-mounted on an NFS volume. It is always safe to disable the write cache, but you
-may be giving up some performance.
-
-For most configurations you must disable the write cache on your disk drives. On
-ATA/SATA drives, the following command should disable the write cache:
-
-.. code-block:: bash
-
-   $ hdparm -W0 /dev/hda
-
-There are some cases when you can keep the write cache, for example:
-
-* Write caching can remain enabled when using XFS, but only if XFS reports that
-  disk write barriers work. If you see one of the following messages in
-  /var/log/messages, then you must disable the write cache:
-
-  * ``Disabling barriers, not supported with external log device``
-
-  * ``Disabling barriers, not supported by the underlying device``
-
-  * ``Disabling barriers, trial barrier write failed``
-
-  XFS write barriers appear to succeed for single disks (with no LVM), or for
-  very recent kernels (such as that provided by Fedora 12). For more
-  information, see the `XFS FAQ
-  <http://xfs.org/index.php/XFS_FAQ#Q:_How_can_I_tell_if_I_have_the_disk_write_cache_enabled.3F>`_.
-
-In the following cases, you must disable the write cache:
-
-* If you use the ext3 filesystem
-
-* If you use LVM (although recent Linux kernels, such as Fedora 12, have fixed
-  this problem)
-
-* If you use Linux's software RAID
-
-* If you use a RAID controller with battery-backed-up memory. This may seem
-  counter-intuitive. For more information, see the `XFS FAQ
-  <http://xfs.org/index.php/XFS_FAQ#Q:_How_can_I_tell_if_I_have_the_disk_write_cache_enabled.3F>`_
-
-In summary, you should disable the write cache, unless you have a very specific reason not to do so.
-
-Progress Tracking
------------------
-
-*TokuDB* has a system for tracking progress of long running statements, thereby
-removing the need to define triggers to track statement execution, as follows:
-
-* Bulk Load: When loading large tables using ``LOAD DATA INFILE`` commands,
-  doing a ``SHOW PROCESSLIST`` command in a separate client session shows
-  progress. There are two progress stages. The first will state something like
-  ``Inserted about 1000000 rows``. After all rows are processed like this, the
-  next stage tracks progress by showing what fraction of the work is done
-  (e.g. ``Loading of data about 45% done``)
-
-* Adding Indexes: When adding indexes via ``ALTER TABLE`` or ``CREATE INDEX``,
-  the command ``SHOW PROCESSLIST`` shows progress. When adding indexes via
-  ``ALTER TABLE`` or ``CREATE INDEX``, the command ``SHOW PROCESSLIST`` will
-  include an estimation of the number of rows processed. Use this information to
-  verify progress is being made. Similar to bulk loading, the first stage shows
-  how many rows have been processed, and the second stage shows progress with a
-  fraction.
-
-* Commits and Aborts: When committing or aborting a transaction, the command
-  ``SHOW PROCESSLIST`` will include an estimate of the transactional operations
-  processed.
-
-Migrating to TokuDB
--------------------
-
-To convert an existing table to use the *TokuDB* engine, run ``ALTER
-TABLE... ENGINE=TokuDB``. If you wish to load from a file, use ``LOAD DATA
-INFILE`` and not ``mysqldump``. Using ``mysqldump`` will be much slower. To
-create a file that can be loaded with ``LOAD DATA INFILE``, refer to the ``INTO
-OUTFILE`` option of the `SELECT Syntax
-<http://dev.mysql.com/doc/refman/8.0/en/select.html>`_.
-
-.. note::
-
-   Creating this file does not save the schema of your table, so you may want to
-   create a copy of that as well.
diff --git a/doc/source/trademark-policy.rst b/doc/source/trademark-policy.rst
deleted file mode 100644
index 0ea92f6dbb4e..000000000000
--- a/doc/source/trademark-policy.rst
+++ /dev/null
@@ -1,23 +0,0 @@
-================
-Trademark Policy
-================
-
-This Trademark Policy is to ensure that users of Percona-branded products or services know that what they receive has really been developed, approved, tested and maintained by Percona. Trademarks help to prevent confusion in the marketplace, by distinguishing one company's or person’s products and services from another's.
-
-Percona owns a number of marks, including but not limited to Percona, XtraDB, Percona XtraDB, XtraBackup, Percona XtraBackup, |Percona Server|, and Percona Live, plus the distinctive visual icons and logos associated with these marks. Both the unregistered and registered marks of Percona are protected.
-
-Use of any Percona trademark in the name, URL, or other identifying characteristic of any product, service, website, or other use is not permitted without Percona's written permission with the following three limited exceptions.
-
-*First*, you may use the appropriate Percona mark when making a nominative fair use reference to a bona fide Percona product.
-
-*Second*, when Percona has released a product under a version of the GNU General Public License ("GPL"), you may use the appropriate Percona mark when distributing a verbatim copy of that product in accordance with the terms and conditions of the GPL.
-
-*Third*, you may use the appropriate Percona mark to refer to a distribution of GPL-released  Percona software that has been modified with minor changes for the sole purpose of allowing the software to operate on an operating system or hardware platform for which Percona has not yet released the software, provided that those third party changes do not affect the behavior, functionality, features, design or performance of the software. Users who acquire this Percona-branded software receive substantially exact implementations of the Percona software.
-
-Percona reserves the right to revoke this authorization at any time in its sole discretion.  For example, if Percona believes that your modification is beyond the scope of the limited license granted in this Policy or that your use of the Percona mark is detrimental to Percona, Percona will revoke this authorization.  Upon revocation, you must immediately cease using the applicable Percona mark.  If you do not immediately cease using the Percona mark upon revocation, Percona may take action to protect its rights and interests in the Percona mark.  Percona does not grant any license to use any Percona mark for any other modified versions of Percona software; such use will require our prior written permission.
-
-Neither trademark law nor any of the exceptions set forth in this Trademark Policy permit you to truncate, modify or otherwise use any Percona mark as part of your own brand.  For example, if XYZ creates a modified version of the |Percona Server|, XYZ may not brand that modification as "XYZ Percona Server" or "Percona XYZ Server", even if that modification otherwise complies with the third exception noted above.
-
-In all cases, you must comply with applicable law, the underlying license, and this Trademark Policy, as amended from time to time.  For instance, any mention of Percona trademarks should include the full trademarked name, with proper spelling and capitalization, along with attribution of ownership to Percona Inc.  For example, the full proper name for XtraBackup is Percona XtraBackup. However, it is acceptable to omit the word "Percona" for brevity on the second and subsequent uses, where such omission does not cause confusion.
-
-In the event of doubt as to any of the conditions or exceptions outlined in this Trademark Policy, please contact trademarks@percona.com for assistance and we will do our very best to be helpful.
diff --git a/doc/source/upgrading_guide.rst b/doc/source/upgrading_guide.rst
deleted file mode 100644
index b6e6a329003f..000000000000
--- a/doc/source/upgrading_guide.rst
+++ /dev/null
@@ -1,67 +0,0 @@
-.. _upgrading_guide:
-
-======================================================================
-*Percona Server for MySQL* In-Place Upgrading Guide: From 5.7 to 8.0
-======================================================================
-
-An in-place upgrade is performed by using existing data on the server and involves the following actions:
-
-* Stopping the MySQL 5.7 server
-* Replacing the old binaries with MySQL 8.0 binaries
-* Starting the MySQL 8.0 server with the same data files.
-
-While an in-place upgrade may not be suitable for all environments, especially those environments with many variables to consider, the upgrade should work in most cases.
-
-The following list summarizes a number of the changes in the 8.0 series and has useful guides that can help you perform a smooth upgrade. We strongly recommend reading this information:
-
-* `Upgrading MySQL <http://dev.mysql.com/doc/refman/8.0/en/upgrading.html>`_
-* `Before You Begin <https://dev.mysql.com/doc/refman/8.0/en/upgrade-before-you-begin.html>`_
-* `Upgrade Paths <https://dev.mysql.com/doc/refman/8.0/en/upgrade-paths.html>`_
-* `Changes in MySQL 8.0 <https://dev.mysql.com/doc/refman/8.0/en/upgrading-from-previous-series.html>`_ 
-* `Preparing your Installation for Upgrade <https://dev.mysql.com/doc/refman/8.0/en/upgrade-prerequisites.html>`_
-* `MySQL 8 Minor Version Upgrades Are ONE-WAY Only <https://www.percona.com/blog/2020/01/10/mysql-8-minor-version-upgrades-are-one-way-only/>`_
-* `Percona Utilities That Make Major MySQL Version Upgrades Easier <https://www.percona.com/blog/percona-utilities-that-make-major-mysql-version-upgrades-easier/>`_
-* :ref:`release_notes_index`   
-* `Upgrade Troubleshooting <https://dev.mysql.com/doc/refman/8.0/en/upgrade-troubleshooting.html>`_
-* `Rebuilding or Repairing Tables or Indexes <https://dev.mysql.com/doc/refman/8.0/en/rebuilding-tables.html>`_
-
-.. note::
-
-   Review other `Percona blogs <https://www.percona.com/blog/>`__ that contain upgrade information.
-
-Implemented in release :ref:`8.0.15-5`, *Percona Server for MySQL* uses the upstream
-implementation of binary log file encryption and relay log file encryption.
-
-The :ref:`encrypt-binlog` variable is
-removed, and the related command-line option `--encrypt-binlog` is not
-supported. It is important to remove the `encrypt-binlog` variable from your
-configuration file before you attempt to upgrade either from another release
-in the *Percona Server for MySQL* 8.0 series or from *Percona Server for MySQL* 5.7.
-Otherwise, a server boot error is generated, and reports an unknown
-variable.
-
-The implemented binary log file encryption is compatible with the older
-format. The encrypted binary log file used in a previous version of MySQL 8.0
-series or Percona Server for MySQL series is supported.
-
-.. seealso::
-
-   *MySQL* Documentation
-      - `Encrypting Binary Log Files and Relay Log Files
-        <https://dev.mysql.com/doc/refman/8.0/en/replication-binlog-encryption.html>`_
-      - `binlog_encryption variable
-        <https://dev.mysql.com/doc/refman/8.0/en/replication-options-binary-log.html#sysvar_binlog_encryption>`_
-
-Before you start the upgrade process, it is recommended to make a full backup of your database. 
-Copy the database configuration file, for example, ``my.cnf``, to another directory to save it.
-
-.. warning::
-
-   Do not upgrade from 5.7 to 8.0 on a crashed instance. If the server instance
-   has crashed, run the crash recovery before proceeding with the upgrade.
-
-You can select one of the following ways to upgrade *Percona Server for MySQL* from 5.7 to 8.0:
-
-* :ref:`upgrading_using_percona_repos`
-* :ref:`upgrading_tokudb_myrocks`
-* :ref:`upgrading_using_standalone_packages`
diff --git a/doc/source/upgrading_tokudb_myrocks.rst b/doc/source/upgrading_tokudb_myrocks.rst
deleted file mode 100644
index 14b7cce91aa8..000000000000
--- a/doc/source/upgrading_tokudb_myrocks.rst
+++ /dev/null
@@ -1,69 +0,0 @@
-.. _upgrading_tokudb_myrocks:
-
-=================================================================================================
-Upgrading from Systems that Use the *MyRocks* or *TokuDB* Storage Engine and Partitioned Tables
-=================================================================================================
-
-Due to the limitation imposed by *MySQL*, the storage engine provides support for partitioning. *MySQL* 8.0 only provides support for
-partitioned table for the *InnoDB* storage engine. 
-
-If you use partitioned tables with the *MyRocks* or *TokuDB* storage engine, the
-upgrade may fail if you do not enable the native partitioning provided by the storage engine.
-
-*TokuDB* is deprecated. For more information, see :ref:`tokudb_intro`.
-
-Before you attempt the upgrade, check whether you have any tables that are not using the native partitioning.
-
-.. code-block:: bash
-
-   $ mysqlcheck -u root --all-databases --check-upgrade
-
-If tables are found, **mysqlcheck** issues a warning:
-
-.. admonition:: Output of **mysqlcheck** detecting a table that is not using the native partitioning
-
-   .. code-block:: bash
-
-      | comp_test.t1_RocksDB_lz4     OK
-      | warning  : The partition engine, used by table '<table-name>',
-      | is deprecated and will be removed in a future release. Please use native partitioning instead.
-
-Enable either the `rocksdb_enable_native_partition` variable or
-the `tokudb_enable_native_partition` variable depending on the storage
-engine and restart the server. 
-
-.. important::
-
-   The `rocksdb_enable_native_partition` variable is **experimental** and should not be used in a production environment in **Percona Server for MySQL** 5.7 unless that environment is being upgraded.
-
-Your next step is to alter the tables that are not using the native partitioning with the
-:mysql:`UPGRADE PARTITIONING` clause:
-
-.. code-block:: mysql
-
-   ALTER TABLE <table-name> UPGRADE PARTITIONING
-
-Complete these steps for each table that **mysqlcheck** list. Otherwise, the upgrade to 8.0 fails and your error log contains messages like the following:
-
-.. code-block:: mysql
-
-   2018-12-17T18:34:14.152660Z 2 [ERROR] [MY-013140] [Server] The 'partitioning' feature is not available; you need to remove '--skip-partition' or use MySQL built with '-DWITH_PARTITION_STORAGE_ENGINE=1'
-   2018-12-17T18:34:14.152679Z 2 [ERROR] [MY-013140] [Server] Can't find file: './comp_test/t1_RocksDB_lz4.frm' (errno: 0 - Success)
-   2018-12-17T18:34:14.152691Z 2 [ERROR] [MY-013137] [Server] Can't find file: './comp_test/t1_RocksDB_lz4.frm' (OS errno: 0 - Success)
-
-.. seealso::
-
-   *MySQL* Documentation: Partitioning Limitations Relating to Storage Engines
-      https://dev.mysql.com/doc/refman/8.0/en/partitioning-limitations-storage-engines.html
-
-Performing a Distribution upgrade in-place on a System with installed Percona packages
---------------------------------------------------------------------------------------------
-The recommended process for performing a distribution upgrade on a system with
-the Percona packages installed is the following:
-
-    1. Record the installed Percona packages.
-    2. Backup the data and configurations.
-    3. Uninstall the Percona packages without removing the configuration file or data.
-    4. Perform the upgrade by following the distribution upgrade instructions
-    5. Reboot the system.
-    6. Install the Percona packages intended for the upgraded version of the distribution.
\ No newline at end of file
diff --git a/doc/source/upgrading_using_percona_repos.rst b/doc/source/upgrading_using_percona_repos.rst
deleted file mode 100644
index 46d140759fc6..000000000000
--- a/doc/source/upgrading_using_percona_repos.rst
+++ /dev/null
@@ -1,197 +0,0 @@
-.. _upgrading_using_percona_repos:
-
-==========================================
-Upgrading using the Percona repositories
-==========================================
-
-Upgrading using the Percona repositories is the easiest and recommended way.
-
-Find the instructions on how to enable the repositories in the following documents:
-
-* :doc:`Percona APT Repository <installation/apt_repo>`
-* :doc:`Percona YUM Repository <installation/yum_repo>`
-
-DEB-based distributions
--------------------------
-
-Run the following commands as root or by using the :program:`sudo` command.
-
-1. Make a full backup (or dump if possible) of you database. Move the database configuration file, ``my.cnf``, to another direction to save it.
-2. Stop the server with :bash:`/etc/init.d/mysql stop`.
-
-.. note::
-
-   If you are running *Debian*/*Ubuntu* system with `systemd
-   <http://freedesktop.org/wiki/Software/systemd/>`_ as the default system and
-   service manager, you can invoke the above command with :program:`systemctl`
-   instead of :program:`service`. Currently both are supported.
-   
-3. Do the required modifications in the database configuration file ``my.cnf``.
-
-4. Install *Percona Server for MySQL*: 
-
-.. code-block:: bash
-
-   $ sudo dpkg -i *.deb
-
-5. Enable the repository:
-
-.. code-block:: bash
-
-   $ percona-release enable ps-80 release
-   $ apt-get update
-
-6. Install the server package:
-
-.. code-block:: bash
-
-   $ apt-get install percona-server-server
-
-7. Install the storage engin packages. 
-
-*TokuDB* is deprecated. For more information, see :ref:`tokudb_intro`. If you used *TokuDB* storage engine in *Percona Server for MySQL* 5.7, install the ``percona-server-tokudb`` package:
-
-.. code-block:: bash
-
-   $ apt install percona-server-tokudb
-
-If you used the *MyRocks* storage engine in *Percona Server for MySQL* 5.7, install the ``percona-server-rocksdb`` package:
-
-.. code-block:: bash
-
-   $ apt install percona-server-rocksdb
-
-8. Running the upgrade:
-
-Starting with *Percona Server for MySQL* 8.0.16-7, the :command:`mysql_upgrade` is deprecated. The functionality was moved to the `mysqld` binary which automatically runs the upgrade process, if needed. If you attempt to run `mysql_upgrade`, no operation happens and the following message appears: "The mysql_upgrade client is now deprecated. The actions executed by the upgrade client are now done by the server." To find more information, see `MySQL Upgrade Process Upgrades <https://dev.mysql.com/doc/refman/8.0/en/upgrading-what-is-upgraded.html>`__
- 
-If you are upgrading to a *Percona Server for MySQL* version before 8.0.16-7, the installation script will *NOT* run automatically :command:`mysql_upgrade`. You must run the :command:`mysql_upgrade` manually.
-
-.. code-block:: bash
-
-   $ mysql_upgrade
-
-   Checking if update is needed.
-   Checking server version.
-   Running queries to upgrade MySQL server.
-   Checking system database.
-   mysql.columns_priv                                 OK
-   mysql.db                                           OK
-   mysql.engine_cost                                  OK
-   ...
-   Upgrade process completed successfully.
-   Checking if update is needed.
-
- 9. Restart the service with :bash:`service mysql restart`.
-     
-After the service has been successfully restarted you can use the new *Percona Server for MySQL* 8.0.
-
-RPM-based distributions
----------------------------
-
-Run the following commands as root or by using the :program:`sudo` command.
-
-1. Make a full backup (or dump if possible) of you database. Copy the database configuration file, for example, ``my.cnf``, to another directory to save it.
-2. Stop the server with :bash:`/etc/init.d/mysql stop`.
-   
-.. note::
-
-   If you are running *RHEL*/*CentOS* system with `systemd
-   <http://freedesktop.org/wiki/Software/systemd/>`_ as the default system and
-   service manager you can invoke the above command with :program:`systemctl`
-   instead of :program:`service`. Currently both are supported.
-
-4. Check your installed packages with :bash:`rpm -qa | grep Percona-Server`.
-
-.. admonition:: Output of :bash:`rpm -qa | grep Percona-Server`
-
-   .. code-block:: bash
-
-      Percona-Server-57-debuginfo-5.7.10-3.1.el7.x86_64
-      Percona-Server-client-57-5.7.10-3.1.el7.x86_64
-      Percona-Server-devel-57-5.7.10-3.1.el7.x86_64
-      Percona-Server-server-57-5.7.10-3.1.el7.x86_64
-      Percona-Server-shared-57-5.7.10-3.1.el7.x86_64
-      Percona-Server-shared-compat-57-5.7.10-3.1.el7.x86_64
-      Percona-Server-test-57-5.7.10-3.1.el7.x86_64
-      Percona-Server-tokudb-57-5.7.10-3.1.el7.x86_64
-
-5. Remove the packages without dependencies. This command only removes the specified packages and leaves any dependent packages. The command does not prompt for confirmation:
-
-.. code-block:: bash
-
-   $ rpm -qa | grep Percona-Server | xargs rpm -e --nodeps
-
-It is important to remove the packages without dependencies as many packages may
-depend on these (as they replace ``mysql``) and will be removed if omitted.
-
-Substitute :bash:`grep '^mysql-'` for :bash:`grep 'Percona-Server'` in the previous command and
-remove the listed packages.
-
-.. important::
-
-   In CentOS 7, the :file:`/etc/my.cnf` configuration file is backed up when you
-   uninstall the *Percona Server for MySQL* packages with the :bash:`rpm -e --nodeps` command.
-
-   The backup file is stored in the same directory with the `_backup` suffix
-   followed by a timestamp: :file:`etc/my.cnf_backup-20181201-1802`.
-
-6. Install the ``percona-server-server`` package:
-
-.. code-block:: bash
-
-   $ yum install percona-server-server
-
-7. Install the storage engine packages. 
-
-*TokuDB* is deprecated. For more information, see :ref:`tokudb_intro`. If you used *TokuDB* storage engine in *Percona Server for MySQL* 5.7, install the ``percona-server-tokudb`` package:
-
-.. code-block:: bash
-
-   $ yum install percona-server-tokudb
- 
-If you used the *MyRocks* storage engine in *Percona Server for MySQL* 5.7, install the ``percona-server-rocksdb`` package:
-
-.. code-block:: bash
-
-   $ apt-get install percona-server-rocksdb
-
-8. Modify your configuration file, :file:`my.cnf`, and reinstall the plugins if necessary.
-
-.. note::
-
-   If you are using *TokuDB* storage engine you need to comment out all the
-   *TokuDB* specific variables in your configuration file(s) before starting the
-   server, otherwise the server is not able to start. *RHEL*/*CentOS* 7
-   automatically backs up the previous configuration file to
-   :file:`/etc/my.cnf.rpmsave` and installs the default :file:`my.cnf`. After
-   upgrade/install process completes you can move the old configuration file
-   back (after you remove all the unsupported system variables).
-
-9. Running the upgrade
-
-Starting with Percona Server 8.0.16-7, the :command:`mysql_upgrade` is deprecated. The functionality was moved to the `mysqld` binary which automatically runs the upgrade process, if needed. If you attempt to run `mysql_upgrade`, no operation happens and the following message appears: "The mysql_upgrade client is now deprecated. The actions executed by the upgrade client are now done by the server." To find more information, see `MySQL Upgrade Process Upgrades <https://dev.mysql.com/doc/refman/8.0/en/upgrading-what-is-upgraded.html>`__
-
-If you are upgrading to a *Percona Server for MySQL* version before 8.0.16-7, you can start the mysql service using :command:`service mysql start`. Use :command:`mysql_upgrade` to migrate to the new grant tables. The :command:`mysql_upgrade` rebuilds the required indexes and does the required modifications:
-
-.. code-block:: bash
-
-   $ mysql_upgrade
-
-.. admonition:: Output
-
-   .. code-block:: bash
-
-      Checking if update is needed.
-      Checking server version.
-      Running queries to upgrade MySQL server.
-      Checking system database.
-      mysql.columns_priv                                 OK
-      mysql.db                                           OK
-      ...
-      pgrade process completed successfully.
-      Checking if update is needed.
-
-10. Restart the service with :bash:`service mysql restart`.
-     
-After the service has been successfully restarted you can use the new *Percona Server for MySQL* 8.0.
\ No newline at end of file
diff --git a/doc/source/upgrading_using_standalone_packages.rst b/doc/source/upgrading_using_standalone_packages.rst
deleted file mode 100644
index 456e683a1226..000000000000
--- a/doc/source/upgrading_using_standalone_packages.rst
+++ /dev/null
@@ -1,211 +0,0 @@
-.. _upgrading_using_standalone_packages:
-
-=====================================
-Upgrading using Standalone Packages
-=====================================
-
-DEB-based distributions
--------------------------
-
-1. Make a full backup (or dump if possible) of you database. Move the database configuration file, ``my.cnf``, to another direction to save it.
-2. Stop the server with :bash:`/etc/init.d/mysql stop`.
-3. Remove the installed packages with their dependencies: :bash:`apt-get autoremove percona-server percona-client`
-4. Do the required modifications in the database configuration file ``my.cnf``.
-5. Download the following packages for your architecture:
-
-* ``percona-server-server``
-* ``percona-server-client``
-* ``percona-server-common``
-* ``libperconaserverclient21``
-
-The following example will download :ref:`8.0.13-3` release
-packages for *Debian* 9.0:
-
-.. code-block:: bash
-
-   $ wget https://www.percona.com/downloads/Percona-Server-8.9/Percona-Server-8.0.13-3/binary/debian/stretch/x86_64/percona-server-8.0.13-3-r63dafaf-stretch-x86_64-bundle.tar
-
-6. Unpack the bundle to get the packages: :bash:`tar xvf Percona-Server-8.0.13-3-r63dafaf-stretch-x86_64-bundle.tar`
-
-After you unpack the bundle, you should see the following packages:
-
-.. code-block:: bash
-
-   $ ls *.deb
-
-   libperconaserverclient21-dev_8.0.13-3-1.stretch_amd64.deb
-   libperconaserverclient21_8.0.13-3-1.stretch_amd64.deb
-   percona-server-dbg_8.0.13-3-1.stretch_amd64.deb
-   percona-server-client_8.0.13-3-1.stretch_amd64.deb
-   percona-server-common_8.0.13-3-1.stretch_amd64.deb
-   percona-server-server_8.0.13-3-1.stretch_amd64.deb
-   percona-server-source_8.0.13-3-1.stretch_amd64.deb
-   percona-server-test_8.0.13-3-1.stretch_amd64.deb
-   percona-server-tokudb_8.0.13-3-1.stretch_amd64.deb
-
-7. Install *Percona Server for MySQL*:
-
-.. code-block:: bash
-
-   $ sudo dpkg -i *.deb
-
-This will install all the packages from the bundle. Another option is to
-download/specify only the packages you need for running *Percona Server for MySQL*
-installation (``libperconaserverclient21_8.0.13-3.stretch_amd64.deb``,
-``percona-server-client-8.0.13-3.stretch_amd64.deb``,
-``percona-server-common-8.0.13-3.stretch_amd64.deb``, and
-``percona-server-server-8.0.13-3.stretch_amd64.deb``. Optionally you can
-install ``percona-server-tokudb-8.0.13-3.stretch_amd64.deb`` if you want
-*TokuDB* storage engine).
-
-
-.. Important:: 
-
-   The TokuDB Storage Engine was `declared as deprecated <https://www.percona.com/doc/percona-server/8.0/release-notes/Percona-Server-8.0.13-3.html>`__ in Percona Server for MySQL 8.0. For more information, see the Percona blog post: `Heads-Up: TokuDB Support Changes and Future Removal from Percona Server for MySQL 8.0 <https://www.percona.com/blog/2021/05/21/tokudb-support-changes-and-future-removal-from-percona-server-for-mysql-8-0/>`__.
-    
-   Starting with :ref:`8.0.26-16`, the binary builds and packages include but disable the TokuDB storage engine plugins. The ``tokudb_enabled`` option and the ``tokudb_backup_enabled`` option control the state of the plugins and have a default setting of ``FALSE``. The result of attempting to load the plugins are the plugins fail to initialize and print a deprecation message.
-
-   To enable the plugins to migrate to another storage engine, set the ``tokudb_enabled`` and ``tokudb_backup_enabled`` options to ``TRUE`` in your ``my.cnf`` file and restart your server instance. Then, you can load the plugins.
-   
-   We recommend :ref:`migrate-myrocks`.
-   
-   Starting with Percona 8.0.26, **the TokuDB storage engine is no longer supported and is removed from the installation packages and not enabled in our binary builds**.
-
-.. warning::
-
-   When installing packages manually, you must resolve all the dependencies and install missing packages yourself. At least
-   the following packages should be installed before installing *Percona Server for MySQL* 8.0: 
-   * ``libmecab2``, 
-   * ``libjemalloc1``, 
-   * ``zlib1g-dev``, 
-   * ``libaio1``.
-
-8. Running the upgrade:
-   
-Starting with Percona Server 8.0.16-7, the :command:`mysql_upgrade` is deprecated. The functionality was moved to the `mysqld` binary which automatically runs the upgrade process, if needed. If you attempt to run `mysql_upgrade`, no operation happens and the following message appears: "The mysql_upgrade client is now deprecated. The actions executed by the upgrade client are now done by the server." To find more information, see `MySQL Upgrade Process Upgrades <https://dev.mysql.com/doc/refman/8.0/en/upgrading-what-is-upgraded.html>`__
-
-If you are upgrading to a *Percona Server for MySQL* version before 8.0.16-7, the installation script will *NOT* run automatically :command:`mysql_upgrade`. You must run the :command:`mysql_upgrade` manually.
-
-.. code-block:: bash
-
-   $ mysql_upgrade
-
-   Checking if update is needed.
-   Checking server version.
-   Running queries to upgrade MySQL server.
-   Checking system database.
-   mysql.columns_priv                                 OK
-   mysql.db                                           OK
-   mysql.engine_cost                                  OK
-   ...
-   Upgrade process completed successfully.
-   Checking if update is needed.
-
-9. Restart the service with :bash:`service mysql restart`.
-     
-After the service has been successfully restarted you can use the new *Percona Server for MySQL* 8.0.
-
-RPM-based distributions
------------------------
-
-1. Make a full backup (or dump if possible) of you database. Move the database configuration file, ``my.cnf``, to another direction to save it.
-2. Stop the server with :bash:`/etc/init.d/mysql stop`. 
-3. Check the installed packages:
-   
-.. code-block:: bash
-
-   $ rpm -qa | grep Percona-Server
-
-   Percona-Server-57-debuginfo-5.7.10-3.1.el7.x86_64
-   Percona-Server-client-57-5.7.10-3.1.el7.x86_64
-   Percona-Server-devel-57-5.7.10-3.1.el7.x86_64
-   Percona-Server-server-57-5.7.10-3.1.el7.x86_64
-   Percona-Server-shared-57-5.7.10-3.1.el7.x86_64
-   Percona-Server-shared-compat-57-5.7.10-3.1.el7.x86_64
-   Percona-Server-test-57-5.7.10-3.1.el7.x86_64
-   Percona-Server-tokudb-57-5.7.10-3.1.el7.x86_64
-
-You may have the ``shared-compat`` package, which is required for compatibility.
-
-5. Remove the packages without dependencies with :bash:`rpm -qa | grep percona-server | xargs rpm -e --nodeps`.
-   
-It is important that you remove the packages without dependencies as many packages may
-depend on these (as they replace ``mysql``) and will be removed if ommited.
-
-Substitute :bash:`grep '^mysql-'` for :bash:`grep 'Percona-Server'` in the previous command and
-remove the listed packages.
-
-7. Download the packages of the desired series for your architecture from the
-`download page <http://www.percona.com/downloads/Percona-Server-8.0/>`_. The
-easiest way is to download bundle which contains all the packages. The following
-example will download *Percona Server for MySQL* 8.0.13-3 release packages for *CentOS* 7:
-
-.. code-block:: bash
-
-   $ wget https://www.percona.com/downloads/Percona-Server-8.0/Percona-Server-8.0.13-3/binary/redhat/7/x86_64/Percona-Server-8.0.13-3-r63dafaf-el7-x86_64-bundle.tar
-
-8. Unpack the bundle to get the packages with :bash:`tar xvf Percona-Server-8.0.13-3-r63dafaf-el7-x86_64-bundle.tar`.
-
-After you unpack the bundle, you should see the following packages: :bash:`ls *.rpm`
-
-.. admonition:: Output
-
-   .. code-block:: bash
-
-      percona-server-debuginfo-8.0.13-3.1.el7.x86_64.rpm
-      percona-server-client-8.0.13-3.1.el7.x86_64.rpm
-      percona-server-devel-8.0.13-3.1.el7.x86_64.rpm
-      percona-server-server-8.0.13-3.1.el7.x86_64.rpm
-      percona-server-shared-8.0.13-3.1.el7.x86_64.rpm
-      percona-server-shared-compat-8.0.13-3.1.el7.x86_64.rpm
-      percona-server-test-8.0.13-3.1.el7.x86_64.rpm
-      percona-server-tokudb-8.0.13-3.1.el7.x86_64.rpm
-
-9. Install *Percona Server for MySQL*:
-
-.. code-block:: bash
-
-   rpm -ivh percona-server-server_8.0.13-3.el7.x86_64.rpm \
-   percona-server-client_8.0.13-3.el7.x86_64.rpm \
-   percona-server-shared_8.0.13-3.el7.x86_64.rpm
-
-This command will install only packages required to run the *Percona Server for MySQL*
-8.0. Optionally you can install :ref:`TokuDB <tokudb_intro>` storage engine by
-adding the ``percona-server-tokudb-8.0.13-3.el7.x86_64.rpm`` to the command
-above. You can find more information on how to install and enable the *TokuDB*
-storage in the :ref:`tokudb_installation` guide.
-
-.. Important:: 
-
-   The TokuDB Storage Engine was `declared as deprecated <https://www.percona.com/doc/percona-server/8.0/release-notes/Percona-Server-8.0.13-3.html>`__ in Percona Server for MySQL 8.0. For more information, see the Percona blog post: `Heads-Up: TokuDB Support Changes and Future Removal from Percona Server for MySQL 8.0 <https://www.percona.com/blog/2021/05/21/tokudb-support-changes-and-future-removal-from-percona-server-for-mysql-8-0/>`__.
-    
-   Starting with :ref:`8.0.26-16`, the binary builds and packages include but disable the TokuDB storage engine plugins. The ``tokudb_enabled`` option and the ``tokudb_backup_enabled`` option control the state of the plugins and have a default setting of ``FALSE``. The result of attempting to load the plugins are the plugins fail to initialize and print a deprecation message.
-
-   To enable the plugins to migrate to another storage engine, set the ``tokudb_enabled`` and ``tokudb_backup_enabled`` options to ``TRUE`` in your ``my.cnf`` file and restart your server instance. Then, you can load the plugins.
-
-   We recommend :ref:`migrate-myrocks`.
-
-   Starting with Percona 8.0.26, **the TokuDB storage engine is no longer supported and is removed from the installation packages and not enabled in our binary builds**.
-
-10. You can install all the packages (for debugging, testing, etc.) with :bash:`rpm -ivh *.rpm`.
-
-.. note::
-
-   When installing packages manually, you must
-   resolve all the dependencies and install missing packages.
-
-11. Modify your configuration file, :file:`my.cnf`, and install the plugins if necessary. If you are using *TokuDB* storage engine you must comment out all the *TokuDB* specific variables in your configuration file(s) before starting the server, otherwise server will not start. *RHEL*/*CentOS* 7 automatically backs up the previous configuration file to :file:`/etc/my.cnf.rpmsave` and installs the default :file:`my.cnf`. After upgrade/install process completes you can move the old configuration file back (after you remove all the unsupported system variables).
-
-12. As the schema of the grant table has changed, the server must be started without reading them with :bash:`service mysql start`.
-
-13. Running the upgrade:
-
-Starting with Percona Server 8.0.16-7, the :command:`mysql_upgrade` is deprecated. The functionality was moved to the `mysqld` binary which automatically runs the upgrade process, if needed. If you attempt to run `mysql_upgrade`, no operation happens and the following message appears: "The mysql_upgrade client is now deprecated. The actions executed by the upgrade client are now done by the server." To find more information, see `MySQL Upgrade Process Upgrades <https://dev.mysql.com/doc/refman/8.0/en/upgrading-what-is-upgraded.html>`__ 
-
-If you are upgrading to a *Percona Server for MySQL* version before 8.0.16-7, run
-:command:`mysql_upgrade` to migrate to the new grant tables. :command:`mysql_upgrade` will
-rebuild the required indexes and do the required modifications.
-
-14. Restart the server with :bash:`service mysql restart`.
-
-After the service has been successfully restarted you can use the new *Percona Server for MySQL* 8.0.
diff --git a/doc/source/upstream-bug-fixes.rst b/doc/source/upstream-bug-fixes.rst
deleted file mode 100644
index 95bcb4c5de6f..000000000000
--- a/doc/source/upstream-bug-fixes.rst
+++ /dev/null
@@ -1,187 +0,0 @@
-.. _upstream_bug_fixes:
-
-================================================================================
-List of upstream *MySQL* bugs fixed in *Percona Server for MySQL*  8.0
-================================================================================
-
-+-------------------------------------------------------------------------------------------------------------+
-|:Upstream Bug: :mysqlbug:`93788` - main.mysqldump is failing because of dropped event                        |
-|:JIRA bug: :psbug:`5268`                                                                                     |
-|:Upstream State: Duplicate (checked on 2019-01-16)                                                           |
-|:Fix Released: :ref:`8.0.13-4`                                                                               |
-|:Upstream Fix: N/A                                                                                           |
-+-------------------------------------------------------------------------------------------------------------+
-|:Upstream Bug: :mysqlbug:`93708` -   Page Cleaner will sleep for long time if clock changes                  |
-|:JIRA bug: :psbug:`5221`                                                                                     |
-|:Upstream State: Verified (checked on 2019-03-11)                                                            |
-|:Fix Released: :ref:`8.0.15-5`                                                                               |
-|:Upstream Fix: N/A                                                                                           |
-+-------------------------------------------------------------------------------------------------------------+
-|:Upstream Bug: :mysqlbug:`93703` - EXPLAIN SELECT returns inconsistent number of ROWS in main.group_by       |
-|:JIRA bug: :psbug:`5306`                                                                                     |
-|:Upstream State: Need Feedback (checked on 2019-01-16)                                                       |
-|:Fix Released: :ref:`8.0.13-4`                                                                               |
-|:Upstream Fix: N/A                                                                                           |
-+-------------------------------------------------------------------------------------------------------------+
-|:Upstream Bug: :mysqlbug:`93686` - innodb.upgrade_orphan fails because of left files                         |
-|:JIRA bug: :psbug:`5209`                                                                                     |
-|:Upstream State: Verified (checked on 2019-01-16)                                                            |
-|:Fix Released: :ref:`8.0.13-4`                                                                               |
-|:Upstream Fix: N/A                                                                                           |
-+-------------------------------------------------------------------------------------------------------------+
-|:Upstream Bug: :mysqlbug:`93544` -  SHOW BINLOG EVENTS FROM <bad offset> is not diagnosed                    |
-|:JIRA bug: :psbug:`5126`                                                                                     |
-|:Upstream State: Verified (checked on 2019-01-16)                                                            |
-|:Fix Released: :ref:`8.0.13-4`                                                                               |
-|:Upstream Fix: N/A                                                                                           |
-+-------------------------------------------------------------------------------------------------------------+
-|:Upstream Bug: :mysqlbug:`89840` - 60-80k connections causing empty reply for select                         |
-|:JIRA bug: :psbug:`314`                                                                                      |
-|:Upstream State: Verified (checked on 2018-11-20)                                                            |
-|:Fix Released: :ref:`8.0.12-2rc1`                                                                            |
-|:Upstream Fix: N/A                                                                                           |
-+-------------------------------------------------------------------------------------------------------------+
-|:Upstream Bug: :mysqlbug:`89607` - MySQL crash in debug, PFS thread not handling singals.                    |
-|:JIRA bug: :psbug:`311`                                                                                      |
-|:Upstream State: Verified (checked on 2018-11-20)                                                            |
-|:Fix Released: :ref:`8.0.12-2rc1`                                                                            |
-|:Upstream Fix: N/A                                                                                           |
-+-------------------------------------------------------------------------------------------------------------+
-|:Upstream Bug: :mysqlbug:`89598` - plugin_mecab.cc:54:19: warning: unused variable 'bundle_mecab'            |
-|:JIRA bug: :psbug:`3804`                                                                                     |
-|:Upstream State: Closed                                                                                      |
-|:Fix Released: :ref:`8.0.12-2rc1`                                                                            |
-|:Upstream Fix: 8.0                                                                                           |
-+-------------------------------------------------------------------------------------------------------------+
-|:Upstream Bug: :mysqlbug:`89467` - Redundant GTID unsafe mark for CREATE/DROP TEMPORARY TABLE in RBR/MBR     |
-|:JIRA bug: :psbug:`1816`                                                                                     |
-|:Upstream State: Verified (checked on 2018-11-20)                                                            |
-|:Fix Released: :ref:`8.0.12-2rc1`                                                                            |
-|:Upstream Fix: N/A                                                                                           |
-+-------------------------------------------------------------------------------------------------------------+
-|:Upstream Bug: :mysqlbug:`89313` - 60-80k connections causing empty reply for select                         |
-|:JIRA bug: :psbug:`314`                                                                                      |
-|:Upstream State: N/A                                                                                         |
-|:Fix Released: :ref:`8.0.12-2rc1`                                                                            |
-|:Upstream Fix: N/A                                                                                           |
-+-------------------------------------------------------------------------------------------------------------+
-|:Upstream Bug: :mysqlbug:`88720` - Inconsistent and unsafe FLUSH behavior in terms of replication            |
-|:JIRA bug: :psbug:`1827`                                                                                     |
-|:Upstream State: Verified (checked on 2019-03-11)                                                            |
-|:Fix Released: :ref:`8.0.15-5`                                                                               |
-|:Upstream Fix: N/A                                                                                           |
-+-------------------------------------------------------------------------------------------------------------+
-|:Upstream Bug: :mysqlbug:`88057` - Intermediary slave does not log master changes with ...                   |
-|:JIRA bug: :psbug:`1119`                                                                                     |
-|:Upstream State: Verified (checked on 2018-11-20)                                                            |
-|:Fix Released: :ref:`8.0.12-2rc1`                                                                            |
-|:Upstream Fix: N/A                                                                                           |
-+-------------------------------------------------------------------------------------------------------------+
-|:Upstream Bug: :mysqlbug:`85208` - A follow-up fix for buffer pool mutex split patch might be suboptimal, ...|
-|:JIRA bug: :psbug:`3755`                                                                                     |
-|:Upstream State: Verified (checked on 2018-11-20)                                                            |
-|:Fix Released: :ref:`8.0.12-2rc1`                                                                            |
-|:Upstream Fix: N/A                                                                                           |
-+-------------------------------------------------------------------------------------------------------------+
-|:Upstream Bug: :mysqlbug:`85205` - A follow-up fix for buffer pool mutex split patch might be suboptimal, ...|
-|:JIRA bug: :psbug:`3754`                                                                                     |
-|:Upstream State: Verified (checked on 2018-11-20)                                                            |
-|:Fix Released: :ref:`8.0.12-2rc1`                                                                            |
-|:Upstream Fix: N/A                                                                                           |
-+-------------------------------------------------------------------------------------------------------------+
-|:Upstream Bug: :mysqlbug:`84366` - InnoDB index dives do not detect concurrent tree changes, return bogus ...|
-|:JIRA bug: :psbug:`1743`                                                                                     |
-|:Upstream State: Verified (checked on 2018-11-20)                                                            |
-|:Fix Released: :ref:`8.0.12-2rc1`                                                                            |
-|:Upstream Fix: N/A                                                                                           |
-+-------------------------------------------------------------------------------------------------------------+
-|:Upstream Bug: :mysqlbug:`83648` - Assertion failure in thread x in file fts0que.cc line 3659                |
-|:JIRA bug: :psbug:`1023`                                                                                     |
-|:Upstream State: N/A                                                                                         |
-|:Fix Released: :ref:`8.0.12-2rc1`                                                                            |
-|:Upstream Fix: N/A                                                                                           |
-+-------------------------------------------------------------------------------------------------------------+
-|:Upstream Bug: :mysqlbug:`82935` - Cipher ECDHE-RSA-AES128-GCM-SHA256 listed in man/Ssl_cipher_list, not ... |
-|:JIRA bug: :psbug:`1737`                                                                                     |
-|:Upstream State: Verified (checked on 2018-11-20)                                                            |
-|:Fix Released: :ref:`8.0.12-2rc1                                                                             |
-|:Upstream Fix: N/A                                                                                           |
-+-------------------------------------------------------------------------------------------------------------+
-|:Upstream Bug: :mysqlbug:`82480` - Incorrect schema mismatch error message when importing mismatched tables  |
-|:JIRA bug: :psbug:`1697`                                                                                     |
-|:Upstream State: Verified (checked on 2018-11-20)                                                            |
-|:Fix Released: :ref:`8.0.12-2rc1`                                                                            |
-|:Upstream Fix: N/A                                                                                           |
-+-------------------------------------------------------------------------------------------------------------+
-|:Upstream Bug: :mysqlbug:`80496` - buf_dblwr_init_or_load_pages now returns an error code, but caller not ...|
-|:JIRA bug: :psbug:`3384`                                                                                     |
-|:Upstream State: Verified (checked on 2018-11-20)                                                            |
-|:Fix Released: :ref:`8.0.12-2rc1`                                                                            |
-|:Upstream Fix: N/A                                                                                           |
-+-------------------------------------------------------------------------------------------------------------+
-|:Upstream Bug: :mysqlbug:`77591` - ALTER TABLE does not allow to change NULL/NOT NULL if foreign key exists  |
-|:JIRA bug: :psbug:`1635`                                                                                     |
-|:Upstream State: Verified (checked on 2018-11-20)                                                            |
-|:Fix Released: :ref:`8.0.12-2rc1`                                                                            |
-|:Upstream Fix: N/A                                                                                           |
-+-------------------------------------------------------------------------------------------------------------+
-|:Upstream Bug: :mysqlbug:`77399` - Deadlocks missed by INFORMATION_SCHEMA.INNODB_METRICS lock_deadlocks ...  |
-|:JIRA bug: :psbug:`1632`                                                                                     |
-|:Upstream State: Verified (checked on 2018-11-20)                                                            |
-|:Fix Released: :ref:`8.0.12-2rc1`                                                                            |
-|:Upstream Fix: N/A                                                                                           |
-+-------------------------------------------------------------------------------------------------------------+
-|:Upstream Bug: :mysqlbug:`76418` - Server crashes when querying partitioning table MySQL_5.7.14              |
-|:JIRA bug: :psbug:`1050`                                                                                     |
-|:Upstream State: N/A                                                                                         |
-|:Fix Released: :ref:`8.0.12-2rc1`                                                                            |
-|:Upstream Fix: N/A                                                                                           |
-+-------------------------------------------------------------------------------------------------------------+
-|:Upstream Bug: :mysqlbug:`76142` - InnoDB tablespace import fails when importing table w/ different data ... |
-|:JIRA bug: :psbug:`1697`                                                                                     |
-|:Upstream State: Verified (checked on 2018-11-20)                                                            |
-|:Fix Released: :ref:`8.0.12-2rc1`                                                                            |
-|:Upstream Fix: N/A                                                                                           |
-+-------------------------------------------------------------------------------------------------------------+
-|:Upstream Bug: :mysqlbug:`76020` - InnoDB does not report filename in I/O error message for reads            |
-|:JIRA bug: :psbug:`2455`                                                                                     |
-|:Upstream State: Verified (checked on 2019-03-11)                                                            |
-|:Fix Released: :ref:`8.0.15-5`                                                                               |
-|:Upstream Fix: N/A                                                                                           |
-+-------------------------------------------------------------------------------------------------------------+
-|:Upstream Bug: :mysqlbug:`75480` - Selecting wrong pos with SHOW BINLOG EVENTS causes a potentially ...      |
-|:JIRA bug: :psbug:`1600`                                                                                     |
-|:Upstream State: N/A                                                                                         |
-|:Fix Released: :ref:`8.0.12-2rc1`                                                                            |
-|:Upstream Fix: N/A                                                                                           |
-+-------------------------------------------------------------------------------------------------------------+
-|:Upstream Bug: :mysqlbug:`75311` - Error for SSL cipher is unhelpful                                         |
-|:JIRA bug: :psbug:`1779`                                                                                     |
-|:Upstream State: Verified (checked on 2018-11-20)                                                            |
-|:Fix Released: :ref:`8.0.12-2rc1`                                                                            |
-|:Upstream Fix: N/A                                                                                           |
-+-------------------------------------------------------------------------------------------------------------+
-|:Upstream Bug: :mysqlbug:`71761` - ANALYZE TABLE should remove its table from background stat processing ... |
-|:JIRA bug: :psbug:`1749`                                                                                     |
-|:Upstream State: Verified (checked on 2018-11-20)                                                            |
-|:Fix Released: :ref:`8.0.12-2rc1`                                                                            |
-|:Upstream Fix: N/A                                                                                           |
-+-------------------------------------------------------------------------------------------------------------+
-|:Upstream Bug: :mysqlbug:`71411` - buf_flush_LRU() does not return correct number in case of compressed ...  |
-|:JIRA bug: :psbug:`2053`                                                                                     |
-|:Upstream State: Verified (checked on 2018-11-20)                                                            |
-|:Fix Released: :ref:`8.0.12-2rc1`                                                                            |
-|:Upstream Fix: N/A                                                                                           |
-+-------------------------------------------------------------------------------------------------------------+
-|:Upstream bug: :mysqlbug:`71217` - Threadpool - add thd_wait_begin/thd_wait_end to the network IO functions  |
-|:JIRA bug: :psbug:`1343`                                                                                     |
-|:Upstream state: Open (checked on 2018-05-24)                                                                |
-|:Fix Released: :ref:`8.0.13-3`                                                                               |
-|:Upstream Fix: N/A                                                                                           |
-+-------------------------------------------------------------------------------------------------------------+
-|:Upstream Bug: :mysqlbug:`53588` - Blackhole : Specified key was too long; max key length is 1000 bytes      |
-|:JIRA bug: :psbug:`1126`                                                                                     |
-|:Upstream State: Verified (checked on 2018-11-20)                                                            |
-|:Fix Released: :ref:`8.0.12-2rc1`                                                                            |
-|:Upstream Fix: N/A                                                                                           |
-+-------------------------------------------------------------------------------------------------------------+
\ No newline at end of file
diff --git a/doc/source/percona-server-logo.jpg b/percona-server-logo.jpg
similarity index 100%
rename from doc/source/percona-server-logo.jpg
rename to percona-server-logo.jpg