Merge lp:~hrvojem/percona-server/doc-29 into lp:percona-server/5.6
- doc-29
- Merge into 5.6
Status: | Merged |
---|---|
Approved by: | Laurynas Biveinis |
Approved revision: | no longer in the source branch. |
Merged at revision: | 376 |
Proposed branch: | lp:~hrvojem/percona-server/doc-29 |
Merge into: | lp:percona-server/5.6 |
Diff against target: |
419 lines (+310/-5) 9 files modified
doc/source/changed_in_56.rst (+57/-0) doc/source/diagnostics/innodb_show_status.rst (+16/-0) doc/source/index.rst (+4/-2) doc/source/installation/apt_repo.rst (+3/-2) doc/source/management/log_archiving.rst (+77/-0) doc/source/performance/atomic_fio.rst (+46/-0) doc/source/release-notes/Percona-Server-5.6.11-60.3.rst (+105/-0) doc/source/release-notes/release-notes_index.rst (+1/-0) doc/source/reliability/log_connection_error.rst (+1/-1) |
To merge this branch: | bzr merge lp:~hrvojem/percona-server/doc-29 |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Laurynas Biveinis (community) | Needs Fixing | ||
Review via email: mp+167029@code.launchpad.net |
Commit message
Description of the change
Laurynas Biveinis (laurynas-biveinis) wrote : | # |
Laurynas Biveinis (laurynas-biveinis) wrote : | # |
- Need different introduction because the feature is not in XB
yet:
- "Main goal for archiving the |XtraDB| logs is ability to later
use them for incremental backups." - move to the end.
- "These logs can be replayed since the last backup was taken
with |Percona XtraBackup|." - not actually true right now.
- And I miss a sentence(s) what does log archiving actually
do. I.e. "InnoDB writes to the redo log files in a cyclic
manner, so that the oldest log data is overwritten with the
newest one. This feature makes copies of the old log files
before they are overwritten, thus saving all the redo log for a
write workload".
- innodb_
well. "It is possible to remove the oldest archived logs
automatically by ... ".
Laurynas Biveinis (laurynas-biveinis) wrote : | # |
That's for the current docs, but before the archived log GA it will be needed to document all the points in https:/
Laurynas Biveinis (laurynas-biveinis) wrote : | # |
- Diff line 169: maybe "XtraDB and InnoDB write ... ",
- Diff line 171: maybe let's remove the purpose / XB sentences
for now and re-add at a later point. Likewise in the RNs.
- Diff line 173: "Archived log file name format", "The start LSN
marks ... ", "when the archive", "An example of archived log
files"
- Diff line 178: "The oldest archived logs".
- bug 1185686: transaction objects are now allocated calling
calloc() directly instead of using InnoDB heap allocation.
This may improve write performance for high levels of
concurrency.
- bug 1184517: "Under very rare circumstances, deleting a
zero-size bitmap file at the right moment would make server
stop with an I/O error if changed page tracking is enabled"
- bug 1171699: "Changed page tracking used to hold the log system
mutex for the log reads needlessly, potentially limiting
performance on write-intensive workloads"
- 714925: "Incorrect schema definition for the (all the userstat
tables) led to the maximum counter values being limited to
32-bit signed integers. Fixed so that these values can be
64-bit unsigned integers now."
- 1184427: "Server would crash if an I_C_P query is issued that
has an empty LSN range and thus does not need to read any bitmap
files"
- 1179974 is the one that gets to keep the current 3-bug
description. "in the middle of requested LSN range".
- 1185040: "A warning is now returned if a bitmap file I/O error
occurs after an I_C_P query started returning data to indicate
an incomplete result set".
- 1157037: sorry, this should have been an "other bugfix"
- 1169494: "Fixed an upstream bug ... that, in Percona Server,
would cause small tablespaces to expand too fast around 500KB
tablespace size"
- 1176864: s/dict_
corrupt table action feature
- Remove :bug:`1157037` from the "other bugs".
Laurynas Biveinis (laurynas-biveinis) wrote : | # |
- bug 714925: "Incorrect schema definitions for
the :ref:`user_stats` tables in INFORMATION_SCHEMA
(
THREAD_
- bug 1179974: "with an I/O error", missing.<space>Bug
- bug 1169494: Percona Server-only user impact (even if the bug is
upstream), thus use the previously-
Percona Server, ... "
Laurynas Biveinis (laurynas-biveinis) : | # |
Laurynas Biveinis (laurynas-biveinis) wrote : | # |
PURGE ARCHIVED LOGS BEFORE <log_filename>
PURGE ARCHIVED LOGS TO <datetime>
are swapped. They are actually BEFORE <date> and TO <filename>.
Preview Diff
1 | === modified file 'doc/source/changed_in_56.rst' | |||
2 | --- doc/source/changed_in_56.rst 2013-06-03 10:01:08 +0000 | |||
3 | +++ doc/source/changed_in_56.rst 2013-06-03 17:46:27 +0000 | |||
4 | @@ -13,6 +13,7 @@ | |||
5 | 13 | * SHOW [GLOBAL] TEMPORARY TABLES functionality is now only available via the INFORMATION_SCHEMA tables :table:`TEMPORARY_TABLES` and :table:`GLOBAL_TEMPORARY_TABLES`. | 13 | * SHOW [GLOBAL] TEMPORARY TABLES functionality is now only available via the INFORMATION_SCHEMA tables :table:`TEMPORARY_TABLES` and :table:`GLOBAL_TEMPORARY_TABLES`. |
6 | 14 | * `InnoDB timer-based Concurrency Throttling <http://www.percona.com/doc/percona-server/5.5/performance/innodb_thread_concurrency_timer_based.html>`_ | 14 | * `InnoDB timer-based Concurrency Throttling <http://www.percona.com/doc/percona-server/5.5/performance/innodb_thread_concurrency_timer_based.html>`_ |
7 | 15 | * `InnoDB Recovery Stats <http://www.percona.com/doc/percona-server/5.5/management/innodb_recovery_patches.html>`_ | 15 | * `InnoDB Recovery Stats <http://www.percona.com/doc/percona-server/5.5/management/innodb_recovery_patches.html>`_ |
8 | 16 | * Rows_read counters in :ref:`slow_extended` and ``SHOW PROCESSLIST`` had a very fuzzy meaning so they were removed. | ||
9 | 16 | 17 | ||
10 | 17 | Some features that were present in |Percona Server| 5.5 have been replaced by a different implementation of the same/similar functionality in |Percona Server| 5.6. These are: | 18 | Some features that were present in |Percona Server| 5.5 have been replaced by a different implementation of the same/similar functionality in |Percona Server| 5.6. These are: |
11 | 18 | 19 | ||
12 | @@ -30,3 +31,59 @@ | |||
13 | 30 | * The |InnoDB| data dictionary INFORMATION_SCHEMA tables have been superseded by the |MySQL| implementations | 31 | * The |InnoDB| data dictionary INFORMATION_SCHEMA tables have been superseded by the |MySQL| implementations |
14 | 31 | * |XtraDB| SYS_STATS persistent table and index statistics has been replaced by the MySQL 5.6 implementation | 32 | * |XtraDB| SYS_STATS persistent table and index statistics has been replaced by the MySQL 5.6 implementation |
15 | 32 | * `Dump/Restore of the Buffer Pool <http://www.percona.com/doc/percona-server/5.5/management/innodb_lru_dump_restore.html>`_ is now available in |MySQL| 5.6, so we have replaced the |Percona Server| implementation with the MySQL one. | 33 | * `Dump/Restore of the Buffer Pool <http://www.percona.com/doc/percona-server/5.5/management/innodb_lru_dump_restore.html>`_ is now available in |MySQL| 5.6, so we have replaced the |Percona Server| implementation with the MySQL one. |
16 | 34 | |||
17 | 35 | Following features were ported from |Percona Server| 5.5 to |Percona Server| 5.6: | ||
18 | 36 | |||
19 | 37 | * :ref:`threadpool` | ||
20 | 38 | |||
21 | 39 | * :ref:`atomic_fio` patch from |MariaDB| | ||
22 | 40 | |||
23 | 41 | * :variable:`innodb_read_views_memory` and :variable:`innodb_descriptors_memory` status variables in the :ref:`innodb_show_status` to improve |InnoDB| memory usage diagnostics. | ||
24 | 42 | |||
25 | 43 | * :ref:`innodb_io_page` | ||
26 | 44 | |||
27 | 45 | * :ref:`innodb_numa_support` | ||
28 | 46 | |||
29 | 47 | * :ref:`log_warning_suppress` | ||
30 | 48 | |||
31 | 49 | * :ref:`improved_memory_engine` | ||
32 | 50 | |||
33 | 51 | * :ref:`maximum_binlog_files` | ||
34 | 52 | |||
35 | 53 | * :ref:`log_connection_error` | ||
36 | 54 | |||
37 | 55 | * :ref:`error_pad` | ||
38 | 56 | |||
39 | 57 | * :ref:`show_slave_status_nolock` | ||
40 | 58 | |||
41 | 59 | * :ref:`udf_percona_toolkit` | ||
42 | 60 | |||
43 | 61 | * :ref:`innodb_fake_changes_page` | ||
44 | 62 | |||
45 | 63 | * :ref:`innodb_kill_idle_trx` | ||
46 | 64 | |||
47 | 65 | * :ref:`enforce_engine` | ||
48 | 66 | |||
49 | 67 | * :ref:`psaas_utility_user` | ||
50 | 68 | |||
51 | 69 | * :ref:`secure_file_priv_extended` | ||
52 | 70 | |||
53 | 71 | * :ref:`expanded_option_modifiers` | ||
54 | 72 | |||
55 | 73 | * :ref:`changed_page_tracking` | ||
56 | 74 | |||
57 | 75 | * :ref:`pam_plugin` | ||
58 | 76 | |||
59 | 77 | * :ref:`user_stats` | ||
60 | 78 | |||
61 | 79 | * :ref:`slow_extended` | ||
62 | 80 | |||
63 | 81 | * :ref:`innodb_show_status` | ||
64 | 82 | |||
65 | 83 | * :ref:`innodb_deadlocks_page` | ||
66 | 84 | |||
67 | 85 | * :ref:`mysql_syslog` | ||
68 | 86 | |||
69 | 87 | * :ref:`show_engines` | ||
70 | 88 | |||
71 | 89 | * :ref:`thread_based_profiling` | ||
72 | 33 | 90 | ||
73 | === modified file 'doc/source/diagnostics/innodb_show_status.rst' | |||
74 | --- doc/source/diagnostics/innodb_show_status.rst 2013-06-03 10:01:08 +0000 | |||
75 | +++ doc/source/diagnostics/innodb_show_status.rst 2013-06-03 17:46:27 +0000 | |||
76 | @@ -361,6 +361,22 @@ | |||
77 | 361 | :vartype: Numeric | 361 | :vartype: Numeric |
78 | 362 | :scope: Global | 362 | :scope: Global |
79 | 363 | 363 | ||
80 | 364 | .. variable:: innodb_descriptors_memory | ||
81 | 365 | |||
82 | 366 | :version 5.6.11-60.3: Introduced. | ||
83 | 367 | :vartype: Numeric | ||
84 | 368 | :scope: Global | ||
85 | 369 | |||
86 | 370 | This status variable shows the current size of the descriptors array (in bytes). The descriptor array is an |XtraDB| data structure that contains the information on currently running transactions. | ||
87 | 371 | |||
88 | 372 | .. variable:: innodb_read_views_memory | ||
89 | 373 | |||
90 | 374 | :version 5.6.11-60.3: Introduced. | ||
91 | 375 | :vartype: Numeric | ||
92 | 376 | :scope: Global | ||
93 | 377 | |||
94 | 378 | This status variable shows the total amount of memory allocated for the |InnoDB| read view (in bytes). | ||
95 | 379 | |||
96 | 364 | TRANSACTIONS | 380 | TRANSACTIONS |
97 | 365 | ------------ | 381 | ------------ |
98 | 366 | 382 | ||
99 | 367 | 383 | ||
100 | === modified file 'doc/source/index.rst' | |||
101 | --- doc/source/index.rst 2013-06-03 10:01:08 +0000 | |||
102 | +++ doc/source/index.rst 2013-06-03 17:46:27 +0000 | |||
103 | @@ -9,9 +9,9 @@ | |||
104 | 9 | Percona Server 5.6 - Documentation | 9 | Percona Server 5.6 - Documentation |
105 | 10 | =================================== | 10 | =================================== |
106 | 11 | 11 | ||
108 | 12 | .. warning:: | 12 | .. note:: |
109 | 13 | 13 | ||
111 | 14 | Please note: |Percona Server| 5.6 is ALPHA quality software. It should *NOT* be used in production environments. | 14 | Please note: |Percona Server| 5.6 is RELEASE CANDIDATE quality software. It should *NOT* be used in production environments. |
112 | 15 | 15 | ||
113 | 16 | |Percona Server| is an enhanced drop-in replacement for |MySQL|. With |Percona Server|, | 16 | |Percona Server| is an enhanced drop-in replacement for |MySQL|. With |Percona Server|, |
114 | 17 | 17 | ||
115 | @@ -67,6 +67,7 @@ | |||
116 | 67 | :maxdepth: 1 | 67 | :maxdepth: 1 |
117 | 68 | :glob: | 68 | :glob: |
118 | 69 | 69 | ||
119 | 70 | performance/atomic_fio | ||
120 | 70 | performance/query_cache_enhance | 71 | performance/query_cache_enhance |
121 | 71 | performance/innodb_numa_support | 72 | performance/innodb_numa_support |
122 | 72 | performance/threadpool | 73 | performance/threadpool |
123 | @@ -112,6 +113,7 @@ | |||
124 | 112 | management/changed_page_tracking | 113 | management/changed_page_tracking |
125 | 113 | management/pam_plugin | 114 | management/pam_plugin |
126 | 114 | management/innodb_expanded_fast_index_creation | 115 | management/innodb_expanded_fast_index_creation |
127 | 116 | management/log_archiving | ||
128 | 115 | 117 | ||
129 | 116 | Diagnostics Improvements | 118 | Diagnostics Improvements |
130 | 117 | ======================== | 119 | ======================== |
131 | 118 | 120 | ||
132 | === modified file 'doc/source/installation/apt_repo.rst' | |||
133 | --- doc/source/installation/apt_repo.rst 2013-05-06 15:43:51 +0000 | |||
134 | +++ doc/source/installation/apt_repo.rst 2013-06-03 17:46:27 +0000 | |||
135 | @@ -33,15 +33,16 @@ | |||
136 | 33 | Debian | 33 | Debian |
137 | 34 | ------ | 34 | ------ |
138 | 35 | 35 | ||
139 | 36 | * 5.0 (lenny) | ||
140 | 37 | * 6.0 (squeeze) | 36 | * 6.0 (squeeze) |
141 | 37 | * 7.0 (wheezy) | ||
142 | 38 | 38 | ||
143 | 39 | Ubuntu | 39 | Ubuntu |
144 | 40 | ------ | 40 | ------ |
145 | 41 | 41 | ||
146 | 42 | * 10.04LTS (lucid) | 42 | * 10.04LTS (lucid) |
147 | 43 | * 11.10 (oneiric) | ||
148 | 44 | * 12.04LTS (precise) | 43 | * 12.04LTS (precise) |
149 | 44 | * 12.10 (quantal) | ||
150 | 45 | * 13.04 (raring) | ||
151 | 45 | 46 | ||
152 | 46 | 47 | ||
153 | 47 | Release Candidate Repository | 48 | Release Candidate Repository |
154 | 48 | 49 | ||
155 | === added file 'doc/source/management/log_archiving.rst' | |||
156 | --- doc/source/management/log_archiving.rst 1970-01-01 00:00:00 +0000 | |||
157 | +++ doc/source/management/log_archiving.rst 2013-06-03 17:46:27 +0000 | |||
158 | @@ -0,0 +1,77 @@ | |||
159 | 1 | .. _log_archiving: | ||
160 | 2 | |||
161 | 3 | ========================== | ||
162 | 4 | Log Archiving for XtraDB | ||
163 | 5 | ========================== | ||
164 | 6 | |||
165 | 7 | .. note:: | ||
166 | 8 | |||
167 | 9 | This feature implementation is considered ALPHA quality. | ||
168 | 10 | |||
169 | 11 | |XtraDB| and |InnoDB| write to the redo log files in a cyclic manner, so that the oldest log data is overwritten with the newest one. This feature makes copies of the old log files before they are overwritten, thus saving all the redo log for a write workload. | ||
170 | 12 | |||
171 | 13 | When log archiving is enabled, instead of rotating through log files, |XtraDB| will create a new one. There will always be one spare log file so that transactions are never stalled at log file rotation. | ||
172 | 14 | |||
173 | 15 | Archived log file name format is ``ib_log_archive_<startlsn>``. The start LSN marks the log sequence number when the archive was started. An example of the archived log files should look like this: :: | ||
174 | 16 | |||
175 | 17 | ib_log_archive_00000000010145937920 | ||
176 | 18 | ib_log_archive_00000000010196267520 | ||
177 | 19 | |||
178 | 20 | The oldest archived logs can be removed automatically by setting up the :variable:`innodb_log_arch_expire_sec` variable. | ||
179 | 21 | |||
180 | 22 | |||
181 | 23 | User statements for handling the XtraDB log archiving | ||
182 | 24 | ====================================================== | ||
183 | 25 | |||
184 | 26 | New statements have been introduced in |Percona Server| for handling the |XtraDB| log archiving. Both of these statements require ``SUPER`` privilege. | ||
185 | 27 | |||
186 | 28 | * ``PURGE ARCHIVED LOGS BEFORE <log_filename>`` - this will delete all archived logs up to 'filename' (and 'filename' too). Archive which is currently in progress will not be deleted. | ||
187 | 29 | |||
188 | 30 | * ``PURGE ARCHIVED LOGS TO <datetime>`` - this will all archived logs modified before date time. Archive which is currently in progress will not be deleted. | ||
189 | 31 | |||
190 | 32 | |||
191 | 33 | Version Specific Information | ||
192 | 34 | ============================ | ||
193 | 35 | |||
194 | 36 | * :rn:`5.6.11-60.3`: | ||
195 | 37 | Feature implemented | ||
196 | 38 | |||
197 | 39 | System Variables | ||
198 | 40 | ================ | ||
199 | 41 | |||
200 | 42 | .. variable:: innodb_log_archive | ||
201 | 43 | |||
202 | 44 | :version 5.6.11-60.3: Introduced. | ||
203 | 45 | :cli: Yes | ||
204 | 46 | :conf: Yes | ||
205 | 47 | :scope: Global | ||
206 | 48 | :dyn: Yes | ||
207 | 49 | :vartype: Boolean | ||
208 | 50 | :values: ON/OFF | ||
209 | 51 | :default: OFF | ||
210 | 52 | |||
211 | 53 | This variable is used to enable or disable log archiving. | ||
212 | 54 | |||
213 | 55 | .. variable:: innodb_log_arch_dir | ||
214 | 56 | |||
215 | 57 | :version 5.6.11-60.3: Introduced. | ||
216 | 58 | :cli: Yes | ||
217 | 59 | :conf: Yes | ||
218 | 60 | :scope: Global | ||
219 | 61 | :dyn: No | ||
220 | 62 | :type: Text | ||
221 | 63 | :default: ./ | ||
222 | 64 | |||
223 | 65 | This variable is used to specify the log archiving directory. | ||
224 | 66 | |||
225 | 67 | .. variable:: innodb_log_arch_expire_sec | ||
226 | 68 | |||
227 | 69 | :version 5.6.11-60.3: Introduced. | ||
228 | 70 | :cli: Yes | ||
229 | 71 | :conf: Yes | ||
230 | 72 | :scope: Global | ||
231 | 73 | :dyn: Yes | ||
232 | 74 | :type: Numeric | ||
233 | 75 | :default: 0 | ||
234 | 76 | |||
235 | 77 | Number of seconds since last modification after which archived log should be deleted. | ||
236 | 0 | 78 | ||
237 | === added file 'doc/source/performance/atomic_fio.rst' | |||
238 | --- doc/source/performance/atomic_fio.rst 1970-01-01 00:00:00 +0000 | |||
239 | +++ doc/source/performance/atomic_fio.rst 2013-06-03 17:46:27 +0000 | |||
240 | @@ -0,0 +1,46 @@ | |||
241 | 1 | .. _atomic_fio: | ||
242 | 2 | |||
243 | 3 | ============================================ | ||
244 | 4 | Atomic write support for Fusion-io devices | ||
245 | 5 | ============================================ | ||
246 | 6 | |||
247 | 7 | .. note:: | ||
248 | 8 | |||
249 | 9 | This feature implementation is considered BETA quality. | ||
250 | 10 | |||
251 | 11 | DirectFS filesystem on `Fusion-io <http://www.fusionio.com/>`_ devices supports atomic writes. Atomic writes can be used instead of |InnoDB| doublewrite buffer to guarantee that the |InnoDB| data pages will be written to disk entirely or not at all. When atomic writes are enabled the device will take care of protecting the data against partial writes. In case the doublewrite buffer is enabled it will be disabled automatically. This will improve the write performance, because data doesn't need to be written twice anymore, and make the recovery simpler. | ||
252 | 12 | |||
253 | 13 | |||
254 | 14 | Version Specific Information | ||
255 | 15 | ============================ | ||
256 | 16 | |||
257 | 17 | * :rn:`5.6.11-60.3` | ||
258 | 18 | ``Atomic write support for Fusion-io`` feature implemented. This feature was ported from |MariaDB|. | ||
259 | 19 | |||
260 | 20 | System Variables | ||
261 | 21 | ================ | ||
262 | 22 | |||
263 | 23 | .. variable:: innodb_use_atomic_writes | ||
264 | 24 | |||
265 | 25 | :cli: Yes | ||
266 | 26 | :conf: Yes | ||
267 | 27 | :scope: Global | ||
268 | 28 | :dyn: No | ||
269 | 29 | :vartype: Boolean | ||
270 | 30 | :default: 0 (OFF) | ||
271 | 31 | |||
272 | 32 | This variable can be used to enable or disable atomic writes instead of the doublewrite buffer. When this option is enabled (set to ``1``), doublewrite buffer will be disabled on |InnoDB| initialization and the file flush method will be set to ``O_DIRECT`` if it's not ``O_DIRECT`` or ``O_DIRECT_NO_FSYNC`` already. | ||
273 | 33 | |||
274 | 34 | .. warning:: | ||
275 | 35 | |||
276 | 36 | :variable:`innodb_use_atomic_writes` should only be enabled on supporting devices, otherwise |InnoDB| will fail to start. | ||
277 | 37 | |||
278 | 38 | Other Reading | ||
279 | 39 | ============= | ||
280 | 40 | |||
281 | 41 | * For general |InnoDB| tuning :ref:`innodb_io_page` documentation is available. | ||
282 | 42 | |||
283 | 43 | * `FusionIO DirectFS atomic write support in *MariaDB* <https://kb.askmonty.org/en/fusionio-directfs-atomic-write-support/>`_ | ||
284 | 44 | |||
285 | 45 | * `Atomic Writes Accelerate MySQL Performance <http://www.fusionio.com/blog/atomic-writes-accelerate-mysql-performance/>`_ | ||
286 | 46 | |||
287 | 0 | 47 | ||
288 | === added file 'doc/source/release-notes/Percona-Server-5.6.11-60.3.rst' | |||
289 | --- doc/source/release-notes/Percona-Server-5.6.11-60.3.rst 1970-01-01 00:00:00 +0000 | |||
290 | +++ doc/source/release-notes/Percona-Server-5.6.11-60.3.rst 2013-06-03 17:46:27 +0000 | |||
291 | @@ -0,0 +1,105 @@ | |||
292 | 1 | .. rn:: 5.6.11-60.3 | ||
293 | 2 | |||
294 | 3 | ============================== | ||
295 | 4 | |Percona Server| 5.6.11-60.3 | ||
296 | 5 | ============================== | ||
297 | 6 | |||
298 | 7 | Percona is glad to announce the first Release Candidate release of |Percona Server| 5.6.11-60.3 on June 3rd, 2013 (Downloads are available `here <http://www.percona.com/downloads/Percona-Server-5.6/Percona-Server-5.6.11-60.3/>`_ and from the `Percona Software Repositories <http://www.percona.com/docs/wiki/repositories:start>`_). | ||
299 | 8 | |||
300 | 9 | Based on `MySQL 5.6.11 <http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-11.html>`_, including all the bug fixes in it, |Percona Server| 5.6.11-60.3 is the first RC release in the |Percona Server| 5.6 series. All of |Percona|'s software is open-source and free, all the details of the release can be found in the `5.6.11-60.3 milestone at Launchpad <https://launchpad.net/percona-server/+milestone/5.6.11-60.3>`_. | ||
301 | 10 | |||
302 | 11 | This release contains all the bug fixes from latest |Percona Server| 5.5 release (currently |Percona Server| `5.5.31-30.3 <http://www.percona.com/doc/percona-server/5.5/release-notes/Percona-Server-5.5.31-30.3.html>`_). | ||
303 | 12 | |||
304 | 13 | New Features | ||
305 | 14 | ============ | ||
306 | 15 | |||
307 | 16 | |Percona Server| has implemented :ref:`log_archiving`. Currently this feature implementation is considered *ALPHA*. | ||
308 | 17 | |||
309 | 18 | |||
310 | 19 | Ported Features | ||
311 | 20 | =============== | ||
312 | 21 | |||
313 | 22 | |Percona Server| has ported priority connection scheduling for the :ref:`threadpool` from |Percona Server| 5.5. | ||
314 | 23 | |||
315 | 24 | |Percona Server| has ported the :ref:`atomic_fio` patch from |MariaDB|. This feature adds atomic write support for ``directFS`` filesystem on ``Fusion-io`` devices. This feature implementation is considered BETA quality. | ||
316 | 25 | |||
317 | 26 | |Percona Server| has ported :variable:`innodb_read_views_memory` and :variable:`innodb_descriptors_memory` status variables in the :ref:`innodb_show_status` to improve |InnoDB| memory usage diagnostics. | ||
318 | 27 | |||
319 | 28 | :ref:`innodb_io_page` has been ported from |Percona Server| 5.5 | ||
320 | 29 | |||
321 | 30 | :ref:`innodb_numa_support` has been ported from |Percona Server| 5.5 | ||
322 | 31 | |||
323 | 32 | :ref:`log_warning_suppress` has been ported from |Percona Server| 5.5 | ||
324 | 33 | |||
325 | 34 | :ref:`improved_memory_engine` has been ported from |Percona Server| 5.5 | ||
326 | 35 | |||
327 | 36 | :ref:`maximum_binlog_files` has been ported from |Percona Server| 5.5 | ||
328 | 37 | |||
329 | 38 | :ref:`log_connection_error` has been ported from |Percona Server| 5.5 | ||
330 | 39 | |||
331 | 40 | :ref:`error_pad` has been ported from |Percona Server| 5.5 | ||
332 | 41 | |||
333 | 42 | :ref:`show_slave_status_nolock` has been ported from |Percona Server| 5.5 | ||
334 | 43 | |||
335 | 44 | :ref:`udf_percona_toolkit` has been ported from |Percona Server| 5.5 | ||
336 | 45 | |||
337 | 46 | :ref:`innodb_fake_changes_page` has been ported from |Percona Server| 5.5 | ||
338 | 47 | |||
339 | 48 | :ref:`innodb_kill_idle_trx` has been ported from |Percona Server| 5.5 | ||
340 | 49 | |||
341 | 50 | :ref:`enforce_engine` has been ported from |Percona Server| 5.5 | ||
342 | 51 | |||
343 | 52 | :ref:`psaas_utility_user` has been ported from |Percona Server| 5.5 | ||
344 | 53 | |||
345 | 54 | :ref:`secure_file_priv_extended` has been ported from |Percona Server| 5.5 | ||
346 | 55 | |||
347 | 56 | :ref:`expanded_option_modifiers` has been ported from |Percona Server| 5.5 | ||
348 | 57 | |||
349 | 58 | :ref:`changed_page_tracking` has been ported from |Percona Server| 5.5 | ||
350 | 59 | |||
351 | 60 | :ref:`pam_plugin` has been ported from |Percona Server| 5.5 | ||
352 | 61 | |||
353 | 62 | :ref:`user_stats` has been ported from |Percona Server| 5.5 | ||
354 | 63 | |||
355 | 64 | :ref:`slow_extended` has been ported from |Percona Server| 5.5 | ||
356 | 65 | |||
357 | 66 | :ref:`innodb_show_status` has been ported from |Percona Server| 5.5 | ||
358 | 67 | |||
359 | 68 | :ref:`innodb_deadlocks_page` has been ported from |Percona Server| 5.5 | ||
360 | 69 | |||
361 | 70 | :ref:`mysql_syslog` has been ported from |Percona Server| 5.5 | ||
362 | 71 | |||
363 | 72 | :ref:`show_engines` has been ported from |Percona Server| 5.5 | ||
364 | 73 | |||
365 | 74 | :ref:`thread_based_profiling` has been ported from |Percona Server| 5.5 | ||
366 | 75 | |||
367 | 76 | |||
368 | 77 | Bug Fixes | ||
369 | 78 | ========== | ||
370 | 79 | |||
371 | 80 | Transaction objects are now allocated calling ``calloc()`` directly instead of using |InnoDB| heap allocation. This may improve write performance for high levels of concurrency. Bug fixed :bug:`1185686`. | ||
372 | 81 | |||
373 | 82 | Under very rare circumstances, deleting a zero-size bitmap file at the right moment would make server stop with an I/O error if changed page tracking is enabled. Bug fixed :bug:`1184517`. | ||
374 | 83 | |||
375 | 84 | Missing path separator between the directory and file name components in a bitmap file name could stop the server starting if the :variable:`innodb_data_home_dir` variable didn't have the path separator at the end. Bug fixed :bug:`1181887`. | ||
376 | 85 | |||
377 | 86 | Changed page tracking used to hold the log system mutex for the log reads needlessly, potentially limiting performance on write-intensive workloads. Bug fixed :bug:`1171699`. | ||
378 | 87 | |||
379 | 88 | Incorrect schema definition for the :ref:`user_stats` tables in ``INFORMATION_SCHEMA`` (:table:`CLIENT_STATISTICS`, :table:`INDEX_STATISTICS`, :table:`TABLE_STATISTICS`, :table:`THREAD_STATISTICS`, and :table:`USER_STATISTICS`) led to the maximum counter values being limited to 32-bit signed integers. Fixed so that these values can be 64-bit unsigned integers now. Bug fixed :bug:`714925`. | ||
380 | 89 | |||
381 | 90 | Server would crash if an :table:`INNODB_CHANGED_PAGES` query is issued that has an empty LSN range and thus does not need to read any bitmap files. Bug fixed :bug:`1184427`. | ||
382 | 91 | |||
383 | 92 | Query to the :table:`INNODB_CHANGED_PAGES` table would cause server to stop with an I/O error if a bitmap file in the middle of requested LSN range was missing. Bug fixed :bug:`1179974`. | ||
384 | 93 | |||
385 | 94 | A warning is now returned if a bitmap file I/O error occurs after an :table:`INNODB_CHANGED_PAGES` query started returning data to indicate an incomplete result set. Bug fixed :bug:`1185040`. | ||
386 | 95 | |||
387 | 96 | The :table:`INNODB_CHANGED_PAGES` table couldn't be queried if the log tracker wasn't running. Bug fixed :bug:`1185304`. | ||
388 | 97 | |||
389 | 98 | Fixed the upstream bug :mysqlbug:`68970` that, in |Percona Server|, would cause small tablespaces to expand too fast around 500KB tablespace size. Bug fixed :bug:`1169494`. | ||
390 | 99 | |||
391 | 100 | Fixed the ``RPM`` package dependencies issues. Bug fixed :bug:`1186831`. | ||
392 | 101 | |||
393 | 102 | Reduced the overhead from :ref:`innodb_corrupt_table_action_page` check as it was missing branch predictor annotations. Bug fixed :bug:`1176864`. | ||
394 | 103 | |||
395 | 104 | Other bugs fixed: bug fixed :bug:`1184695`, bug fixed :bug:`1184512`, bug fixed :bug:`1183585`, bug fixed :bug:`1178606`, bug fixed :bug:`1177356`, bug fixed :bug:`1160895`, bug fixed :bug:`1182876`, bug fixed :bug:`1180481`, bug fixed :bug:`1163135`, bug fixed :bug:`1157078`, bug fixed :bug:`1182889`, bug fixed :bug:`1133926`, bug fixed :bug:`1165098`, bug fixed :bug:`1182793`, bug fixed :bug:`1157075`, bug fixed :bug:`1183625`, bug fixed :bug:`1155475`, bug fixed :bug:`1157037`, bug fixed :bug:`1182065`, bug fixed :bug:`1182837`, bug fixed :bug:`1177780`, bug fixed :bug:`1154954`. | ||
396 | 105 | |||
397 | 0 | 106 | ||
398 | === modified file 'doc/source/release-notes/release-notes_index.rst' | |||
399 | --- doc/source/release-notes/release-notes_index.rst 2013-05-27 03:01:29 +0000 | |||
400 | +++ doc/source/release-notes/release-notes_index.rst 2013-06-03 17:46:27 +0000 | |||
401 | @@ -6,6 +6,7 @@ | |||
402 | 6 | :maxdepth: 1 | 6 | :maxdepth: 1 |
403 | 7 | :glob: | 7 | :glob: |
404 | 8 | 8 | ||
405 | 9 | Percona-Server-5.6.11-60.3 | ||
406 | 9 | Percona-Server-5.6.10-60.2 | 10 | Percona-Server-5.6.10-60.2 |
407 | 10 | Percona-Server-5.6.6-60.1 | 11 | Percona-Server-5.6.6-60.1 |
408 | 11 | Percona-Server-5.6.5-60.0 | 12 | Percona-Server-5.6.5-60.0 |
409 | 12 | 13 | ||
410 | === modified file 'doc/source/reliability/log_connection_error.rst' | |||
411 | --- doc/source/reliability/log_connection_error.rst 2013-06-03 10:14:58 +0000 | |||
412 | +++ doc/source/reliability/log_connection_error.rst 2013-06-03 17:46:27 +0000 | |||
413 | @@ -10,5 +10,5 @@ | |||
414 | 10 | Version-Specific Information | 10 | Version-Specific Information |
415 | 11 | ============================ | 11 | ============================ |
416 | 12 | 12 | ||
418 | 13 | * :rn:`5.6.11-30.3`: | 13 | * :rn:`5.6.11-60.3`: |
419 | 14 | Feature ported from |Percona Server| 5.5. | 14 | Feature ported from |Percona Server| 5.5. |
- Replace ALL_O_DIRECT with O_DIRECT_NO_FSYNC in atomic_fio.rst documented bugs should
(note that this is _not_ a 5.6 replacement option value for PS
5.5 ALL_O_DIRECT, it just happens to fit in this context).
- <laurynas> as for the Ported Features, I'd just link to 5.5-5.6 changes page
and list them there, next to what's been dropped [16:07]
- Only 1186831 from the currently-
stay. The rest are "other bugfixes". Additional bugfixes to
document are: 1185686, 1185304, 1184517, 1176864, 1154954,
1181887, 1185040, 1171699, 714925, 1179974, 1182793, 1184427,
1157037, 1169494.