A transaction reads one row and then remains open. Later, a deployment adds a column using ALTER TABLE ... ALGORITHM=INSTANT. The migration waits. A new request issues an ordinary SELECT against the same table, and that request waits too.
The original query has already finished. The schema change requires no table rebuild. The new query accesses a different row. Yet all three sessions participate in the same blocking sequence.
All database administrators have experienced something like this at one point. A query that was running well suddenly starts to create problems. No error, failure, or…
Google is testing query refinement bubbles at the top of the AI Overviews in Google Search. But clicking the refinement bubble does not change the query, instead, it…
I'm not naive enough to think that these companies don't already have some internal detection tools, but they clearly are not being used enough. Lately researching…
Discussion (0)
No comments yet. Start the conversation!