Merge lp:~hrvojem/percona-server/bug997469-5.1 into lp:percona-server/5.1

Proposed by Hrvoje Matijakovic
Status: Merged
Approved by: Alexey Kopytov
Approved revision: no longer in the source branch.
Merged at revision: 447
Proposed branch: lp:~hrvojem/percona-server/bug997469-5.1
Merge into: lp:percona-server/5.1
Diff against target: 126 lines (+19/-29)
6 files modified
doc/source/diagnostics/innodb_stats.rst (+2/-3)
doc/source/diagnostics/mysql_syslog.rst (+1/-1)
doc/source/diagnostics/slow_extended.rst (+2/-2)
doc/source/installation/apt_repo.rst (+12/-0)
doc/source/reliability/innodb_corrupt_table_action.rst (+0/-23)
doc/source/scalability/innodb_extra_rseg.rst (+2/-0)
To merge this branch: bzr merge lp:~hrvojem/percona-server/bug997469-5.1
Reviewer Review Type Date Requested Status
Alexey Kopytov (community) Approve
Review via email: mp+107845@code.launchpad.net
To post a comment you must log in.
Revision history for this message
Alexey Kopytov (akopytov) :
review: Approve

Preview Diff

[H/L] Next/Prev Comment, [J/K] Next/Prev File, [N/P] Next/Prev Hunk
1=== modified file 'doc/source/diagnostics/innodb_stats.rst'
2--- doc/source/diagnostics/innodb_stats.rst 2012-01-31 13:43:08 +0000
3+++ doc/source/diagnostics/innodb_stats.rst 2012-05-29 20:17:23 +0000
4@@ -54,13 +54,12 @@
5
6 .. variable:: innodb_use_sys_stats_table
7
8+ :version: 5.1.49-11.3 Variable introduced
9 :type: BOOLEAN
10 :default: 0
11
12
13-If this option is enabled, |XtraDB| uses the ``SYS_STATS`` system table to store statistics of table indexes. Also, when |InnoDB| opens a table for the first time, it loads the statistics from ``SYS_STATS`` instead of sampling index pages. If you use a high ``stats_sample_pages`` value, the first open of a table is expensive. In such a case, this option will help. Note: This option may cause less frequent updating of statistics. So, you should intentionally use the ``ANALYZE TABLE`` command more often.
14-
15-(This variable was introduced in release 5.1.49-rel11.3)
16+If this option is enabled, |XtraDB| uses the ``SYS_STATS`` system table to store statistics of table indexes. Also, when |InnoDB| opens a table for the first time, it loads the statistics from ``SYS_STATS`` instead of sampling index pages. If you use a high ``stats_sample_pages`` value, the first open of a table is expensive. In such a case, this option will help. Intended behavior is to never update statistics unless an explicit ``ANALYZE TABLE`` is issued.
17
18
19 INFORMATION_SCHEMA Tables
20
21=== modified file 'doc/source/diagnostics/mysql_syslog.rst'
22--- doc/source/diagnostics/mysql_syslog.rst 2011-10-07 00:55:06 +0000
23+++ doc/source/diagnostics/mysql_syslog.rst 2012-05-29 20:17:23 +0000
24@@ -4,7 +4,7 @@
25 Log All Client Commands (``syslog``)
26 ======================================
27
28-When enabled, this feature causes all commands run on the client to be logged to ``syslog``.
29+When enabled, this feature causes all commands run by the command line client to be logged to ``syslog``. If you want to enable this option permanently, add it to the [mysql] group in my.cnf.
30
31
32 Version Specific Information
33
34=== modified file 'doc/source/diagnostics/slow_extended.rst'
35--- doc/source/diagnostics/slow_extended.rst 2011-10-07 00:55:06 +0000
36+++ doc/source/diagnostics/slow_extended.rst 2012-05-29 20:17:23 +0000
37@@ -179,10 +179,10 @@
38 Specifies the time threshold for filtering queries out of the slow query log. The unit of time is seconds. This option has the same meaning as in a standard |MySQL| server, with the following changes:
39
40 The option accepts fractional values. If set to 0.5, for example, queries longer than 1/2 second will be logged.
41-
42-If the value is set to 0, then all queries are logged. This is different from the standard |MySQL| build, where a value of 0 disables logging.
43 Before version 1.01 of this feature, the value was an integer, and the unit of time was microseconds, not seconds.
44
45+If the value is set to 0, then all queries are logged. This is different from the standard |MySQL| build, prior to version 5.1.21, where a value of 0 disables logging. After |MySQL| 5.1.21 this has been changed to minimum value and you can disable/enable slow query log with ``slow_query_log`` variable.
46+
47 .. variable:: profiling_server
48
49 :cli: Yes
50
51=== modified file 'doc/source/installation/apt_repo.rst'
52--- doc/source/installation/apt_repo.rst 2012-05-17 11:21:21 +0000
53+++ doc/source/installation/apt_repo.rst 2012-05-29 20:17:23 +0000
54@@ -50,3 +50,15 @@
55
56 deb http://repo.percona.com/apt-rc VERSION main
57 deb-src http://repo.percona.com/apt-rc VERSION main
58+
59+
60+Apt-Pinning the packages
61+========================
62+
63+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: ::
64+
65+ Package: *
66+ Pin: release o=Percona Development Team
67+ Pin-Priority: 1001
68+
69+For more information about the pinning you can check the official `debian wiki <http://wiki.debian.org/AptPreferences>`_.
70
71=== modified file 'doc/source/reliability/innodb_corrupt_table_action.rst'
72--- doc/source/reliability/innodb_corrupt_table_action.rst 2011-10-07 00:55:06 +0000
73+++ doc/source/reliability/innodb_corrupt_table_action.rst 2012-05-29 20:17:23 +0000
74@@ -8,18 +8,12 @@
75
76 This feature adds a new system variable.
77
78-Version Specific Information
79-============================
80-
81- * 5.5.10-20.1:
82- Renamed variable :variable:`innodb_pass_corrupt_table` to :variable:`innodb_corrupt_table_action`.
83
84 System Variables
85 ================
86
87 .. variable:: innodb_pass_corrupt_table
88
89- :version 5.5.10-20.1: Renamed.
90 :cli: Yes
91 :conf: Yes
92 :scope: Global
93@@ -31,20 +25,3 @@
94
95 Pass corruptions of user tables as ``corrupt table`` instead of crashing itself, when used with innodb_file_per_table. All file I/O for the datafile after detected as corrupt is disabled, except for the deletion.
96
97- This variable was renamed to innodb_corrupt_table_action, beginning in release 5.5.10-20.1. It still exists as :variable:`innodb_pass_corrupt_table` in versions prior to that.
98-
99-
100-.. variable:: innodb_corrupt_table_action
101-
102- :version 5.5.10-20.1: Introduced.
103- :cli: Yes
104- :conf: Yes
105- :scope: Global
106- :dyn: Yes
107- :vartype: ULONG
108- :default: ``assert``
109- :range: ``assert``, ``warn``
110-
111-Pass corruptions of user tables as ``corrupt table`` instead of not crashing itself, when used with file_per_table. All file I/O for the datafile after detected as corrupt is disabled, except for the deletion.
112-
113- This variable was added in release 5.5.10-20.1. Prior to that, it was named :variable:`innodb_pass_corrupt_table`, which still exists in earlier versions.
114
115=== modified file 'doc/source/scalability/innodb_extra_rseg.rst'
116--- doc/source/scalability/innodb_extra_rseg.rst 2011-10-07 00:55:06 +0000
117+++ doc/source/scalability/innodb_extra_rseg.rst 2012-05-29 20:17:23 +0000
118@@ -32,6 +32,8 @@
119
120 When you modify this variable, you must restart the |MySQL| server for the change to take effect. Please note that you must perform a slow shutdown (ie with ``innodb_fast_shutdown = 0``). If you just perform a fast shutdown, the |MySQL| server will then restart without error but the additional segments will not be created.
121
122+If there is already any existing data stored in |XtraDB| or |InnoDB| it will need to be dumped and re-imported once this option has been enabled. This is needed so |XtraDB| can re-create the new data files with additional rollback segments.
123+
124 To check that the extra segments have been created, you can run the following query: ::
125
126 SELECT COUNT(*) FROM information_schema.INNODB_RSEG;

Subscribers

People subscribed via source and target branches