Skip to content

Commit 93d86f3

Browse files
author
Alina Derkach
committed
PS 8408 Update .md version of docs (8.0)
renamed: docs/_resource/overrides/404.html -> _resource/overrides/404.html renamed: docs/_resource/overrides/main.html -> _resource/overrides/main.html renamed: docs/_resource/overrides/partials/header.html -> _resource/overrides/partials/header.html renamed: docs/_resource/overrides/partials/nav.html -> _resource/overrides/partials/nav.html renamed: docs/_resource/templates/styles.scss -> _resource/templates/styles.scss renamed: docs/_resource/theme/main.html -> _resource/theme/main.html
1 parent ffd7a87 commit 93d86f3

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

44 files changed

+401
-940
lines changed
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.

docs/changed_in_version.md

+32-32
Original file line numberDiff line numberDiff line change
@@ -21,102 +21,102 @@ The features are listed within the following sections:
2121
### Performance
2222

2323

24-
* Prefix Index Queries Optimization
24+
* [Prefix Index Queries Optimization](performance/prefix_index_queries_optimization.md#prefix-index-queries-optimization)
2525

2626

27-
* Multiple page asynchronous I/O requests
27+
* [Multiple page asynchronous I/O requests](performance/aio_page_requests.md#aio-page-requests)
2828

2929

30-
* Thread Pool
30+
* [Thread Pool](performance/threadpool.md#threadpool)
3131

3232

33-
* Priority refill for the buffer pool free list
33+
* [Priority refill for the buffer pool free list](performance/xtradb_performance_improvements_for_io-bound_highly-concurrent_workloads.md#ps-buffer-pool-free-list-priority-refill)
3434

3535

36-
* Multi-threaded LRU flusher
36+
* [Multi-threaded LRU flusher](performance/xtradb_performance_improvements_for_io-bound_highly-concurrent_workloads.md#lru-manager-threads)
3737

3838
### Flexibility
3939

4040

41-
* InnoDB Full-Text Search Improvements
41+
* [InnoDB Full-Text Search Improvements](flexibility/innodb_fts_improvements.md#innodb-fts-improvements)
4242

4343

44-
* Improved MEMORY Storage Engine
44+
* [Improved MEMORY Storage Engine](flexibility/improved_memory_engine.md#improved-memory-engine)
4545

4646

47-
* Extended mysqldump
47+
* [Extended mysqldump](flexibility/extended_mysqldump.md#extended-mysqldump)
4848

4949

50-
* Extended SELECT INTO OUTFILE/DUMPFILE
50+
* [Extended SELECT INTO OUTFILE/DUMPFILE](flexibility/extended_select_into_outfile.md#extended-select-into-outfile)
5151

5252

53-
* Support for PROXY protocol
53+
* [Support for PROXY protocol](flexibility/proxy_protocol_support.md#proxy-protocol-support)
5454

5555

56-
* Compressed columns with dictionaries
56+
* [Compressed columns with dictionaries](flexibility/compressed_columns.md#compressed-columns)
5757

5858
### Management
5959

6060

61-
* Percona Toolkit UDFs
61+
* [Percona Toolkit UDFs](management/udf_percona_toolkit.md#udf-percona-toolkit)
6262

6363

64-
* Kill Idle Transactions
64+
* [Kill Idle Transactions](management/kill_idle_trx.md)
6565

6666

67-
* XtraDB changed page tracking
67+
* [XtraDB changed page tracking](management/changed_page_tracking.md)
6868

6969

70-
* PAM Authentication Plugin
70+
* [PAM Authentication Plugin](management/pam_plugin.md)
7171

7272

73-
* Expanded Fast Index Creation
73+
* [Expanded Fast Index Creation](management/innodb_expanded_fast_index_creation.md)
7474

7575

76-
* Backup Locks
76+
* [Backup Locks](management/backup_locks.md)
7777

7878

79-
* Audit Log Plugin
79+
* [Audit Log Plugin](management/audit_log_plugin.md)
8080

8181

82-
* Start transaction with consistent snapshot
82+
* [Start transaction with consistent snapshot](management/start_transaction_with_consistent_snapshot.md)
8383

8484

85-
* Extended SHOW GRANTS
85+
* [Extended SHOW GRANTS](management/extended_show_grants.md)
8686

8787

88-
* Data at Rest Encryption
88+
* [Data at Rest Encryption](security/data-at-rest-encryption.md#data-at-rest-encryption)
8989

9090
### Reliability
9191

9292

93-
* Handle Corrupted Tables
93+
* [Handle Corrupted Tables](reliability/innodb_corrupt_table_action.md)
9494

9595

96-
* Too Many Connections Warning
96+
* [Too Many Connections Warning](reliability/log_connection_error.md)
9797

9898
### Diagnostics
9999

100100

101-
* User Statistics
101+
* [User Statistics](diagnostics/user_stats.md)
102102

103103

104-
* Slow Query Log
104+
* [Slow Query Log](diagnostics/slow_extended.md#slow-extended)
105105

106106

107-
* Show Storage Engines
107+
* [Show Storage Engines](diagnostics/show_engines.md)
108108

109109

110-
* Process List
110+
* [Process List](diagnostics/process_list.md)
111111

112112

113-
* INFORMATION_SCHEMA.[GLOBAL_]TEMP_TABLES
113+
* [INFORMATION_SCHEMA.[GLOBAL_]TEMP_TABLES](diagnostics/misc_info_schema_tables.md)
114114

115115

116-
* Thread Based Profiling
116+
* [Thread Based Profiling](diagnostics/thread_based_profiling.md)
117117

118118

119-
* InnoDB Page Fragmentation Counters
119+
* [InnoDB Page Fragmentation Counters](diagnostics/innodb_fragmentation_count.md)
120120

121121
#### Features Removed from *Percona Server for MySQL* 8.0
122122

@@ -205,6 +205,6 @@ which was an alias to the `kill_idle_trx` system variable
205205

206206
* 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.
207207

208-
> We recommend migrating to the MyRocks Storage Engine.
208+
We recommend migrating to the MyRocks Storage Engine.
209209

210-
> 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/).
210+
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/).

docs/development.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
# Development of *Percona Server for MySQL*
1+
# Development of Percona Server for MySQL
22

33
*Percona Server for MySQL* is an open source project to produce a distribution
44
of the *MySQL* Server with improved performance, scalability and

docs/faq.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ Support team members that they have customers who use *Percona Server for MySQL*
1010
## Q: Will we have to *GPL* our whole application if we use *Percona Server for MySQL* with *XtraDB*?
1111

1212
A: This is a common misconception about the *GPL*. We suggest reading the *Free
13-
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
13+
Software Foundation* ‘s excellent reference material on the [GPL Version 2](https://www.gnu.org/licenses/old-licenses/gpl-2.0.html), which is the license
1414
that applies to *MySQL* and therefore to *Percona Server for MySQL* with *XtraDB*. That
1515
document contains links to many other documents which should answer your
1616
questions. *Percona* is unable to give legal advice about the *GPL*.

docs/feature_comparison.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
# *Percona Server for MySQL* Feature Comparison
1+
# Percona Server for MySQL Feature Comparison
22

33
*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.
44

docs/flexibility/extended_mysqlbinlog.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
# Extended `mysqlbinlog`
1+
# Extended mysqlbinlog
22

33
*Percona Server for MySQL* has implemented compression support for
44
**mysqlbinlog**. This is similar to support that both `mysql` and

docs/flexibility/extended_mysqldump.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
# Extended `mysqldump`
1+
# Extended mysqldump
22

33
## Backup Locks support
44

docs/glossary.md

+10-10
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22

33
## ACID
44

5-
Set of properties that guarantee database transactions are processed reliably. Stands for [Atomicity](#term-Atomicity), [Consistency](#term-Consistency), [Isolation](#term-Isolation), [Durability](#term-Durability).
5+
Set of properties that guarantee database transactions are processed reliably. Stands for [Atomicity](#Atomicity), [Consistency](#Consistency), [Isolation](#Isolation), [Durability](#Durability).
66

77
## Atomicity
88

@@ -26,39 +26,39 @@ The Isolation requirement means that no transaction can interfere with another.
2626

2727
## InnoDB
2828

29-
A [Storage Engine](#term-Storage-Engine) for MySQL and derivatives ([Percona Server](#term-Percona-Server), [MariaDB](#term-MariaDB)) originally written by Innobase Oy, since acquired by Oracle. It provides [ACID](#term-ACID) compliant storage engine with [foreign key](#term-Foreign-Key) support. As of [MySQL](#term-MySQL) version 5.5, InnoDB became the default storage engine on all platforms.
29+
A [Storage Engine](#Storage-Engine) for MySQL and derivatives ([Percona Server](#Percona-Server), [MariaDB](#MariaDB)) originally written by Innobase Oy, since acquired by Oracle. It provides [ACID](#ACID) compliant storage engine with [foreign key](#Foreign-Key) support. As of [MySQL](#MySQL) version 5.5, InnoDB became the default storage engine on all platforms.
3030

3131
## Jenkins
3232

33-
[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:
33+
[Jenkins](https://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:
3434

3535
* no failed tests in the trunk on any platform,
3636
* aid developers in ensuring merge requests build and test on all platforms,
3737
* no known performance regressions (without a damn good explanation).
3838

3939
## LSN
4040

41-
Log Serial Number. A term used in relation to the [InnoDB](#term-InnoDB) or [XtraDB](#term-XtraDB) storage engines.
41+
Log Serial Number. A term used in relation to the [InnoDB](#InnoDB) or [XtraDB](#XtraDB) storage engines.
4242

4343
## MariaDB
4444

45-
A fork of [MySQL](#term-MySQL) that is maintained primarily by Monty Program AB. It aims to add features, and fix bugs while maintaining 100% backward compatibility with MySQL.
45+
A fork of [MySQL](#MySQL) that is maintained primarily by Monty Program AB. It aims to add features, and fix bugs while maintaining 100% backward compatibility with MySQL.
4646

4747
## my.cnf
4848

4949
The file name of the default MySQL configuration file.
5050

5151
## MyISAM
5252

53-
A [MySQL](#term-MySQL) [Storage Engine](#term-Storage-Engine) that was the default until MySQL 5.5.
53+
A [MySQL](#MySQL) [Storage Engine](#Storage-Engine) that was the default until MySQL 5.5.
5454

5555
## MySQL
5656

57-
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 [MariaDB](#term-MariaDB) and [Percona Server for MySQL](#term-Percona-Server).
57+
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 [MariaDB](#MariaDB) and [Percona Server for MySQL](#Percona-Server).
5858

5959
## NUMA
6060

61-
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.
61+
Non-Uniform Memory Access ([NUMA](https://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.
6262

6363
## Percona Server for MySQL
6464

@@ -67,9 +67,9 @@ Percona’s branch of [MySQL](#MySQL) with performance and management improvemen
6767

6868
## Storage Engine
6969

70-
A [Storage Engine](#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 [MySQL](#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. [MyISAM](#term-MyISAM), InnoDB).
70+
A [Storage Engine](#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 [MySQL](#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. [MyISAM](#MyISAM), InnoDB).
7171

7272
## XtraDB
7373

74-
Percona’s improved version of [InnoDB](#term-InnoDB) provides performance, features, and reliability above what is shipped by Oracle in InnoDB.
74+
Percona’s improved version of [InnoDB](#InnoDB) provides performance, features, and reliability above what is shipped by Oracle in InnoDB.
7575

0 commit comments

Comments
 (0)