Bug #67525 profiling, have_profiling etc. in MySQL 5.6.8+
Submitted: 8 Nov 2012 18:46 Modified: 19 Jun 2013 19:35
Reporter: Peter Laursen (Basic Quality Contributor) Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server: Documentation Severity:S3 (Non-critical)
Version:5.6.8+ OS:Any
Assigned to: Paul Dubois CPU Architecture:Any
Triage: Needs Triage: D3 (Medium)

[8 Nov 2012 18:46] Peter Laursen
Description:
http://dev.mysql.com/doc/refman/5.6/en/server-system-variables.html#sysvar_profiling: "..This variable is deprecated in MySQL 5.6.8 and will be removed in a future MySQL release."

http://dev.mysql.com/doc/refman/5.6/en/news-5-6-8.html: "Important Change: The server system variables profiling, have_profiling, and profiling_history_size are now deprecated, and are subject to removal in a future release of the MySQL Server. (Bug #14658683)"

http://dev.mysql.com/doc/refman/5.6/en/show-profile.html: "Note: These statements are deprecated as of MySQL 5.6.7 and will be removed in a future MySQL release. Use the Performance Schema instead; see Chapter 20, MySQL Performance Schema."

But http://dev.mysql.com/doc/refman/5.6/en/profiling-table.html has no information about same. It just tells that the table is available.

How to repeat:
See above. I suspcect that the sentence "use Performance_schema instead" in 2nd link/quote should rather be "Use Information_schema_instead".  There is nothing in P_S that matches I_S.profiling or SHOW PROFILes as far as I can understand.

Suggested fix:
If I am right we need a clarification whether the server will *always* or *never* populate I_S.profiling as before.

If I am wrong, we need a clarification how P_S can be used the way I_S.profiling could from MySQL 5.0.37.

(but I tend to think it is a plain 'miswrite'/misunderstanding between developers and docs team. P_S should probably be I_S)
[10 Nov 2012 13:56] Sveta Smirnova
Thank you for the report.

5.6.7 and 5.6.8 version mismatch verified as described. But I am not sure information_schema.profiling will be deprecated.
[10 Nov 2012 14:03] Peter Laursen
OK .. but I didn't even notice that version mismatch. THis was not the important point!

The important thing (for me) is to get a statement whether I_S.profiling table is also deprecated. 

If it is then http://dev.mysql.com/doc/refman/5.6/en/profiling-table.html should have a note that this table is deprecated and will he removed in a future version.  And then please explain how Performance_Schema can be used to get the same level of info.

If it is just a typo (P_S printed instead of I_S) then please correct in docs.
[10 Nov 2012 14:09] Sveta Smirnova
See this: http://dev.mysql.com/doc/refman/5.6/en/performance-schema-stages-tables.html and Mark Leith's presentation at MySQL Connect starting from slide 56: https://oracleus.activeevents.com/connect/sessionDetail.ww?SESSION_ID=9309
[15 Nov 2012 1:50] Paul Dubois
"5.6.7 and 5.6.8 version mismatch verified as described."

No, it's not verified. There is no mismatch. The SHOW statements were deprecated in 5.6.7:
http://dev.mysql.com/doc/refman/5.6/en/news-5-6-7.html
The system variables were deprecated in 5.6.8:
http://dev.mysql.com/doc/refman/5.6/en/news-5-6-8.html
[5 Apr 2013 18:43] Paul Dubois
"The important thing (for me) is to get a statement whether I_S.profiling table is also deprecated."

Yes, consider it deprecated.
[19 Jun 2013 16:44] Paul Dubois
I_S.PROFILING is deprecated as of 5.7.2.
[19 Jun 2013 19:35] Peter Laursen
Deprecated only or will the I_S table be removed in 5.7.2 release?

In any case, could you please advise (a docs link for instance) how similar detailed information can be retrieved from P_S *for a single specific query*.
[20 Jun 2013 1:14] Paul Dubois
Deprecated in 5.7, to be removed later. This is what will appear at
http://dev.mysql.com/doc/refman/5.6/en/profiling-table.html:

    <note>
      <para>
        This table is deprecated as of MySQL 5.7.2 and will be removed
        in a future MySQL release. Use the Performance Schema instead;
        see <xref linkend="performance-schema"/>.
      </para>
    </note>

re: "In any case, could you please advise (a docs link for instance) how similar detailed information can be retrieved from P_S *for a single specific query*."

No, that'll depend on what you want to know.