Bug #35994 Support for the table information_schema.SLAVE_STATUS.

Submitted: 11 Apr 2008 12:47 Modified: 29 Aug 2013 13:50
Reporter: Santo Leto Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server: Replication Severity:S4 (Feature request)
Version:5.1.x, 6.0.x OS:Any
Assigned to: Mats Kindahl CPU Architecture:Any
Tags: replication metadata, slave status

[11 Apr 2008 12:47] Santo Leto
Description:
It could be interesting if you add a 'SLAVE_STATUS' table in information_schema similar to the table 'GLOBAL_STATUS'.

This is very important for me and could be useful for other users, too.

It could bring the same advantages of using the SELECT statement over the table 'GLOBAL_STATUS' instead of using a less flexible SHOW syntax.

You could also add a [like_or_where] CLAUSE in the SHOW SLAVE STATUS syntax but having a table is even better.

Thanks.

How to repeat:
-

Suggested fix:
mysql> DESCRIBE `information_schema`.`SLAVE_STATUS`;
+----------------+----------------+------+-----+---------+-------+
| Field          | Type           | Null | Key | Default | Extra |
+----------------+----------------+------+-----+---------+-------+
| VARIABLE_NAME  | varchar(64)    | NO   |     |         |       |
| VARIABLE_VALUE | varchar(20480) | YES  |     | NULL    |       |
+----------------+----------------+------+-----+---------+-------+
2 rows in set (0.02 sec)
[16 Apr 2008 14:48] Susanne Ebrecht
Many thanks for writing a feature request. We will discuss if we will implement it or not.
[29 Aug 2013 13:50] Jon Stephens
Fixed in 5.7.2. Implemented as new PERFORMANCE_SCHEMA tables in WL#3656, q.v. for documentation information.

Closed.

Portions of this website are copyright © 2001, 2002 The PHP Group

Page generated in 0.053 sec. using MySQL 8.4.7-u6-cloud

Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.