Bug #104704 A stored proc used to refresh a table became unusable with upgrade to 8.0.25
Submitted: 23 Aug 2021 19:56 Modified: 27 Sep 2021 12:27
Reporter: Aji Adeniji Email Updates:
Status: Can't repeat Impact on me:
Category:MySQL Server: Stored Routines Severity:S3 (Non-critical)
Version:8.0.25 OS:Ubuntu
Assigned to: CPU Architecture:Any

[23 Aug 2021 19:56] Aji Adeniji
Created an API (stored proc) that we used to refresh a table that's about 5 million records. We do a total reload of the table which contains aggregations of data with the possibility of the aggregate data changing with each new data sets received. On 8.0.21 of MySQL, the stored proc completed in about 30 mins. We upgraded MySQL to 8.0.25 (and then 8.0.26) and the same stored proc was now running for over 7 hours to complete. The stored proc builds the aggregations using common table expressions and then a final insert/select.

How to repeat:
The stored proc takes over 7hrs in 8.0.25/26 environments and 30 mins in 8.0.21
[24 Aug 2021 12:15] MySQL Verification Team
Hi Mr. Adeniji,

Thank you for your bug report.

However, we can not help you with the information that you have supplied.

In order to proceed, we need the entire source of your stored routine that makes you problems. Beside that, we need you to profile all DML statements in that stored routine. We need profiling for both 8.0.21 and 8.0.25.  Then we can proceed further.

Waiting on your feedback.
[25 Sep 2021 1:00] Bugs System
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".