Merge lp:~hrvojem/percona-server/doc-29 into lp:percona-server/5.6

Proposed by Hrvoje Matijakovic
Status: Merged
Approved by: Laurynas Biveinis
Approved revision: 376
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
Reviewer Review Type Date Requested Status
Laurynas Biveinis (community) Needs Fixing
Review via email: mp+167029@code.launchpad.net
To post a comment you must log in.
Revision history for this message
Laurynas Biveinis (laurynas-biveinis) wrote :

    - Replace ALL_O_DIRECT with O_DIRECT_NO_FSYNC in atomic_fio.rst
      (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-documented bugs should
      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.

review: Needs Fixing
Revision history for this message
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_log_arch_expire_sec needs describing at the top as
     well. "It is possible to remove the oldest archived logs
     automatically by ... ".

review: Needs Fixing
Revision history for this message
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://blueprints.launchpad.net/percona-server/+spec/document-log-archiving: "internals, limitations, new server variables, new entries in SHOW ENGINE INNODB STATUS and possible use cases for this feature."

Revision history for this message
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_table_struct:is_corrupt/whatever is the link to
      corrupt table action feature
    - Remove :bug:`1157037` from the "other bugs".

review: Needs Fixing
Revision history for this message
Laurynas Biveinis (laurynas-biveinis) wrote :

    - bug 714925: "Incorrect schema definitions for
      the :ref:`user_stats` tables in INFORMATION_SCHEMA
      (CLIENT_STATISTICS, INDEX_STATISTICS, TABLE_STATISTICS,
      THREAD_STATISTICS, and USER_STATISTICS) led to ... "
    - 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-suggested wording "that, in
      Percona Server, ... "

review: Needs Fixing
lp:~hrvojem/percona-server/doc-29 updated
376. By Hrvoje Matijakovic on 2013-06-03

- 5.6.11-60.3 - release notes
- log archiving docs (alpha)

Revision history for this message
Laurynas Biveinis (laurynas-biveinis) :
review: Approve
Revision history for this message
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>.

review: Needs Fixing

Preview Diff

[H/L] Next/Prev Comment, [J/K] Next/Prev File, [N/P] Next/Prev Hunk
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 * SHOW [GLOBAL] TEMPORARY TABLES functionality is now only available via the INFORMATION_SCHEMA tables :table:`TEMPORARY_TABLES` and :table:`GLOBAL_TEMPORARY_TABLES`.
6 * `InnoDB timer-based Concurrency Throttling <http://www.percona.com/doc/percona-server/5.5/performance/innodb_thread_concurrency_timer_based.html>`_
7 * `InnoDB Recovery Stats <http://www.percona.com/doc/percona-server/5.5/management/innodb_recovery_patches.html>`_
8+ * Rows_read counters in :ref:`slow_extended` and ``SHOW PROCESSLIST`` had a very fuzzy meaning so they were removed.
9
10 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
12@@ -30,3 +31,59 @@
13 * The |InnoDB| data dictionary INFORMATION_SCHEMA tables have been superseded by the |MySQL| implementations
14 * |XtraDB| SYS_STATS persistent table and index statistics has been replaced by the MySQL 5.6 implementation
15 * `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+
17+Following features were ported from |Percona Server| 5.5 to |Percona Server| 5.6:
18+
19+ * :ref:`threadpool`
20+
21+ * :ref:`atomic_fio` patch from |MariaDB|
22+
23+ * :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+
25+ * :ref:`innodb_io_page`
26+
27+ * :ref:`innodb_numa_support`
28+
29+ * :ref:`log_warning_suppress`
30+
31+ * :ref:`improved_memory_engine`
32+
33+ * :ref:`maximum_binlog_files`
34+
35+ * :ref:`log_connection_error`
36+
37+ * :ref:`error_pad`
38+
39+ * :ref:`show_slave_status_nolock`
40+
41+ * :ref:`udf_percona_toolkit`
42+
43+ * :ref:`innodb_fake_changes_page`
44+
45+ * :ref:`innodb_kill_idle_trx`
46+
47+ * :ref:`enforce_engine`
48+
49+ * :ref:`psaas_utility_user`
50+
51+ * :ref:`secure_file_priv_extended`
52+
53+ * :ref:`expanded_option_modifiers`
54+
55+ * :ref:`changed_page_tracking`
56+
57+ * :ref:`pam_plugin`
58+
59+ * :ref:`user_stats`
60+
61+ * :ref:`slow_extended`
62+
63+ * :ref:`innodb_show_status`
64+
65+ * :ref:`innodb_deadlocks_page`
66+
67+ * :ref:`mysql_syslog`
68+
69+ * :ref:`show_engines`
70+
71+ * :ref:`thread_based_profiling`
72
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 :vartype: Numeric
78 :scope: Global
79
80+.. variable:: innodb_descriptors_memory
81+
82+ :version 5.6.11-60.3: Introduced.
83+ :vartype: Numeric
84+ :scope: Global
85+
86+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+
88+.. variable:: innodb_read_views_memory
89+
90+ :version 5.6.11-60.3: Introduced.
91+ :vartype: Numeric
92+ :scope: Global
93+
94+This status variable shows the total amount of memory allocated for the |InnoDB| read view (in bytes).
95+
96 TRANSACTIONS
97 ------------
98
99
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 Percona Server 5.6 - Documentation
105 ===================================
106
107-.. warning::
108+.. note::
109
110- Please note: |Percona Server| 5.6 is ALPHA quality software. It should *NOT* be used in production environments.
111+ Please note: |Percona Server| 5.6 is RELEASE CANDIDATE quality software. It should *NOT* be used in production environments.
112
113 |Percona Server| is an enhanced drop-in replacement for |MySQL|. With |Percona Server|,
114
115@@ -67,6 +67,7 @@
116 :maxdepth: 1
117 :glob:
118
119+ performance/atomic_fio
120 performance/query_cache_enhance
121 performance/innodb_numa_support
122 performance/threadpool
123@@ -112,6 +113,7 @@
124 management/changed_page_tracking
125 management/pam_plugin
126 management/innodb_expanded_fast_index_creation
127+ management/log_archiving
128
129 Diagnostics Improvements
130 ========================
131
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 Debian
137 ------
138
139- * 5.0 (lenny)
140 * 6.0 (squeeze)
141+ * 7.0 (wheezy)
142
143 Ubuntu
144 ------
145
146 * 10.04LTS (lucid)
147- * 11.10 (oneiric)
148 * 12.04LTS (precise)
149+ * 12.10 (quantal)
150+ * 13.04 (raring)
151
152
153 Release Candidate Repository
154
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+.. _log_archiving:
160+
161+==========================
162+ Log Archiving for XtraDB
163+==========================
164+
165+.. note::
166+
167+ This feature implementation is considered ALPHA quality.
168+
169+|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+
171+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+
173+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+
175+ ib_log_archive_00000000010145937920
176+ ib_log_archive_00000000010196267520
177+
178+The oldest archived logs can be removed automatically by setting up the :variable:`innodb_log_arch_expire_sec` variable.
179+
180+
181+User statements for handling the XtraDB log archiving
182+======================================================
183+
184+New statements have been introduced in |Percona Server| for handling the |XtraDB| log archiving. Both of these statements require ``SUPER`` privilege.
185+
186+ * ``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+
188+ * ``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+
190+
191+Version Specific Information
192+============================
193+
194+ * :rn:`5.6.11-60.3`:
195+ Feature implemented
196+
197+System Variables
198+================
199+
200+.. variable:: innodb_log_archive
201+
202+ :version 5.6.11-60.3: Introduced.
203+ :cli: Yes
204+ :conf: Yes
205+ :scope: Global
206+ :dyn: Yes
207+ :vartype: Boolean
208+ :values: ON/OFF
209+ :default: OFF
210+
211+This variable is used to enable or disable log archiving.
212+
213+.. variable:: innodb_log_arch_dir
214+
215+ :version 5.6.11-60.3: Introduced.
216+ :cli: Yes
217+ :conf: Yes
218+ :scope: Global
219+ :dyn: No
220+ :type: Text
221+ :default: ./
222+
223+This variable is used to specify the log archiving directory.
224+
225+.. variable:: innodb_log_arch_expire_sec
226+
227+ :version 5.6.11-60.3: Introduced.
228+ :cli: Yes
229+ :conf: Yes
230+ :scope: Global
231+ :dyn: Yes
232+ :type: Numeric
233+ :default: 0
234+
235+Number of seconds since last modification after which archived log should be deleted.
236
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+.. _atomic_fio:
242+
243+============================================
244+ Atomic write support for Fusion-io devices
245+============================================
246+
247+.. note::
248+
249+ This feature implementation is considered BETA quality.
250+
251+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+
253+
254+Version Specific Information
255+============================
256+
257+ * :rn:`5.6.11-60.3`
258+ ``Atomic write support for Fusion-io`` feature implemented. This feature was ported from |MariaDB|.
259+
260+System Variables
261+================
262+
263+.. variable:: innodb_use_atomic_writes
264+
265+ :cli: Yes
266+ :conf: Yes
267+ :scope: Global
268+ :dyn: No
269+ :vartype: Boolean
270+ :default: 0 (OFF)
271+
272+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+
274+.. warning::
275+
276+ :variable:`innodb_use_atomic_writes` should only be enabled on supporting devices, otherwise |InnoDB| will fail to start.
277+
278+Other Reading
279+=============
280+
281+ * For general |InnoDB| tuning :ref:`innodb_io_page` documentation is available.
282+
283+ * `FusionIO DirectFS atomic write support in *MariaDB* <https://kb.askmonty.org/en/fusionio-directfs-atomic-write-support/>`_
284+
285+ * `Atomic Writes Accelerate MySQL Performance <http://www.fusionio.com/blog/atomic-writes-accelerate-mysql-performance/>`_
286+
287
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+.. rn:: 5.6.11-60.3
293+
294+==============================
295+ |Percona Server| 5.6.11-60.3
296+==============================
297+
298+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+
300+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+
302+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+
304+New Features
305+============
306+
307+ |Percona Server| has implemented :ref:`log_archiving`. Currently this feature implementation is considered *ALPHA*.
308+
309+
310+Ported Features
311+===============
312+
313+ |Percona Server| has ported priority connection scheduling for the :ref:`threadpool` from |Percona Server| 5.5.
314+
315+ |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+
317+ |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+
319+ :ref:`innodb_io_page` has been ported from |Percona Server| 5.5
320+
321+ :ref:`innodb_numa_support` has been ported from |Percona Server| 5.5
322+
323+ :ref:`log_warning_suppress` has been ported from |Percona Server| 5.5
324+
325+ :ref:`improved_memory_engine` has been ported from |Percona Server| 5.5
326+
327+ :ref:`maximum_binlog_files` has been ported from |Percona Server| 5.5
328+
329+ :ref:`log_connection_error` has been ported from |Percona Server| 5.5
330+
331+ :ref:`error_pad` has been ported from |Percona Server| 5.5
332+
333+ :ref:`show_slave_status_nolock` has been ported from |Percona Server| 5.5
334+
335+ :ref:`udf_percona_toolkit` has been ported from |Percona Server| 5.5
336+
337+ :ref:`innodb_fake_changes_page` has been ported from |Percona Server| 5.5
338+
339+ :ref:`innodb_kill_idle_trx` has been ported from |Percona Server| 5.5
340+
341+ :ref:`enforce_engine` has been ported from |Percona Server| 5.5
342+
343+ :ref:`psaas_utility_user` has been ported from |Percona Server| 5.5
344+
345+ :ref:`secure_file_priv_extended` has been ported from |Percona Server| 5.5
346+
347+ :ref:`expanded_option_modifiers` has been ported from |Percona Server| 5.5
348+
349+ :ref:`changed_page_tracking` has been ported from |Percona Server| 5.5
350+
351+ :ref:`pam_plugin` has been ported from |Percona Server| 5.5
352+
353+ :ref:`user_stats` has been ported from |Percona Server| 5.5
354+
355+ :ref:`slow_extended` has been ported from |Percona Server| 5.5
356+
357+ :ref:`innodb_show_status` has been ported from |Percona Server| 5.5
358+
359+ :ref:`innodb_deadlocks_page` has been ported from |Percona Server| 5.5
360+
361+ :ref:`mysql_syslog` has been ported from |Percona Server| 5.5
362+
363+ :ref:`show_engines` has been ported from |Percona Server| 5.5
364+
365+ :ref:`thread_based_profiling` has been ported from |Percona Server| 5.5
366+
367+
368+Bug Fixes
369+==========
370+
371+ 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+
373+ 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+
375+ 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+
377+ 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+
379+ 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+
381+ 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+
383+ 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+
385+ 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+
387+ The :table:`INNODB_CHANGED_PAGES` table couldn't be queried if the log tracker wasn't running. Bug fixed :bug:`1185304`.
388+
389+ 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+
391+ Fixed the ``RPM`` package dependencies issues. Bug fixed :bug:`1186831`.
392+
393+ Reduced the overhead from :ref:`innodb_corrupt_table_action_page` check as it was missing branch predictor annotations. Bug fixed :bug:`1176864`.
394+
395+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+
397
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 :maxdepth: 1
403 :glob:
404
405+ Percona-Server-5.6.11-60.3
406 Percona-Server-5.6.10-60.2
407 Percona-Server-5.6.6-60.1
408 Percona-Server-5.6.5-60.0
409
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 Version-Specific Information
415 ============================
416
417- * :rn:`5.6.11-30.3`:
418+ * :rn:`5.6.11-60.3`:
419 Feature ported from |Percona Server| 5.5.

Subscribers

People subscribed via source and target branches