Need documentation on innodb_rseg

Bug #592366 reported by Peter Zaitsev
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Percona Server moved to https://jira.percona.com/projects/PS
Fix Released
Medium
Fred Linhoss

Bug Description

Documentation need to be updated with explanation of what numbers with this table really are and how to read them

mysql> select * from innodb_rseg;
+---------+----------+----------+---------+------------+-----------+
| rseg_id | space_id | zip_size | page_no | max_size | curr_size |
+---------+----------+----------+---------+------------+-----------+
| 0 | 0 | 0 | 6 | 4294967294 | 6354 |
+---------+----------+----------+---------+------------+-----------+
1 row in set (0.01 sec)

Changed in percona-server:
status: New → Confirmed
importance: Undecided → Medium
assignee: nobody → Fred Linhoss (fred-linhoss)
milestone: none → 5.1.53-11.7
Revision history for this message
Vadim Tkachenko (vadim-tk) wrote :
Changed in percona-server:
status: Confirmed → Fix Committed
Changed in percona-server:
status: Fix Committed → Fix Released
Revision history for this message
Shahriyar Rzayev (rzayev-sehriyar) wrote :

Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-1142

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.