Bug #45812 DTrace: no InnoDB read row probes
Submitted: 28 Jun 2009 18:39 Modified: 11 Apr 2017 21:54
Reporter: Alexey Kopytov Email Updates:
Status: Verified Impact on me:
None 
Category:MySQL Server: InnoDB storage engine Severity:S3 (Non-critical)
Version:5.4.2-beta OS:Solaris
Assigned to: Sunny Bains CPU Architecture:Any
Tags: DTrace
Triage: Triaged: D3 (Medium)

[28 Jun 2009 18:39] Alexey Kopytov
Description:
The 'read-row' and 'index-read-row' probes are missing in the InnoDB storage engine.

How to repeat:
$ sudo dtrace -l -n 'mysql*:::read-row-start'
   ID   PROVIDER            MODULE                          FUNCTION NAME
58328 mysql27089            mysqld    __1cJha_myisamHrnd_pos6MpC1_i_ read-row-start
58329 mysql27089            mysqld    __1cJha_myisamIrnd_next6MpC_i_ read-row-start
58330 mysql27089            mysqld __1cMha_myisammrgHrnd_pos6MpC1_i_ read-row-start
58331 mysql27089            mysqld __1cMha_myisammrgIrnd_next6MpC_i_ read-row-start
58332 mysql27089            mysqld      __1cHha_heapHrnd_pos6MpC1_i_ read-row-start
58333 mysql27089            mysqld      __1cHha_heapIrnd_next6MpC_i_ read-row-start
58334 mysql27089            mysqld __1cMha_federatedHrnd_pos6MpC1_i_ read-row-start
58335 mysql27089            mysqld __1cMha_federatedIrnd_next6MpC_i_ read-row-start
58336 mysql27089            mysqld      __1cHha_tinaHrnd_pos6MpC1_i_ read-row-start
58337 mysql27089            mysqld      __1cHha_tinaIrnd_next6MpC_i_ read-row-start
58338 mysql27089            mysqld __1cMha_blackholeHrnd_pos6MpC1_i_ read-row-start
58339 mysql27089            mysqld __1cMha_blackholeIrnd_next6MpC_i_ read-row-start
58340 mysql27089            mysqld   __1cKha_archiveHrnd_pos6MpC1_i_ read-row-start
58341 mysql27089            mysqld   __1cKha_archiveIrnd_next6MpC_i_ read-row-start
58342 mysql27089            mysqld __1cNha_ndbclusterHrnd_pos6MpC1_i_ read-row-start
58343 mysql27089            mysqld __1cNha_ndbclusterIrnd_next6MpC_i_ read-row-start

Suggested fix:
Add missing probes to InnoDB code.
[6 Jul 2009 12:10] Sveta Smirnova
Thank you for the report.

Verified as described.
[11 Apr 2017 21:54] Alexey Kopytov
I guess this can be closed now that DTrace support has been removed in MySQL 8.0.1.