Add more information to TABLE_STATISTICS and USER_STATISTICS

Bug #673622 reported by Olivier Doucet
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Percona Server moved to https://jira.percona.com/projects/PS
Triaged
Wishlist
Unassigned

Bug Description

Hello,

The MySQL Server Facebook Edition offers many useful fields in table_statistics :
- `TABLE_ENGINE` varchar(192) NOT NULL DEFAULT '',
- `ROWS_INSERTED` bigint(21) NOT NULL DEFAULT '0',
- `ROWS_UPDATED` bigint(21) NOT NULL DEFAULT '0',
- `ROWS_DELETED` bigint(21) NOT NULL DEFAULT '0',
- `ROWS_READ` bigint(21) NOT NULL DEFAULT '0',
- `ROWS_REQUESTED` bigint(21) NOT NULL DEFAULT '0',
- `IO_READ_BYTES` bigint(21) NOT NULL DEFAULT '0',
- `IO_READ_REQUESTS` bigint(21) NOT NULL DEFAULT '0',
- `IO_READ_SVC_USECS` bigint(21) NOT NULL DEFAULT '0',
- `IO_READ_SVC_USECS_MAX` bigint(21) NOT NULL DEFAULT '0',
- `IO_READ_WAIT_USECS` bigint(21) NOT NULL DEFAULT '0',
- `IO_READ_WAIT_USECS_MAX` bigint(21) NOT NULL DEFAULT '0',
- `IO_READ_OLD_IOS` bigint(21) NOT NULL DEFAULT '0',
- `IO_WRITE_BYTES` bigint(21) NOT NULL DEFAULT '0',
- `IO_WRITE_REQUESTS` bigint(21) NOT NULL DEFAULT '0',
- `IO_WRITE_SVC_USECS` bigint(21) NOT NULL DEFAULT '0',
- `IO_WRITE_SVC_USECS_MAX` bigint(21) NOT NULL DEFAULT '0',
- `IO_WRITE_WAIT_USECS` bigint(21) NOT NULL DEFAULT '0',
- `IO_WRITE_WAIT_USECS_MAX` bigint(21) NOT NULL DEFAULT '0',
- `IO_WRITE_OLD_IOS` bigint(21) NOT NULL DEFAULT '0',
- `IO_INDEX_INSERTS` bigint(21) NOT NULL DEFAULT '0'

There are also new fields in user_statistics :
- `ROWS_DELETED` bigint(21) NOT NULL DEFAULT '0',
- `ROWS_INSERTED` bigint(21) NOT NULL DEFAULT '0',
- `ROWS_READ` bigint(21) NOT NULL DEFAULT '0',

This could be useful to add it in Percona Server.

Related commits in Facebook edition are : (may missed some, I'm not a mysql internals guru) :
http://bazaar.launchpad.net/~mysqlatfacebook/mysqlatfacebook/5.1/revision/3431

Other revisions you may take a look at :
3563 ; 3548 ; 3547 ; 3434 ; 3424 ;

Tags: userstat
Revision history for this message
Nikki Morton (nikki-morton) wrote : Hi Olivier

I saw your note about this bug that you sent to Vadim and wondered if you might be interested in having this bug fixed by paying for maintenance from Percona?

We recently launched a support and maintenance package whereby you gain access to a quantity of hours from Percona that can be used for both bug fixes and support- in any sized division. Check it out and let me know if you're interested in a discussion:

http://www.percona.com/support/overview/

Nikki Morton
Senior Account Manager, Percona Inc.
+1-888-316-9775 X 530
+1-778-327-9460
fax +1-888-401-3411
<email address hidden>
http://www.percona.com

Percona has new 24x7 support pricing! No per-server or per-CPU costs: sensible, easy to buy:

http://tinyurl.com/2fcmn34

Changed in percona-server:
status: New → Confirmed
importance: Undecided → Wishlist
Stewart Smith (stewart)
Changed in percona-server:
status: Confirmed → Triaged
tags: added: userstat
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-2331

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.