> In short, what happens is that if you create a large number of tables, like 10000, the mysql daemon will crash at restart.

Feels like this would be unlikely to get triggered in practice. What am I missing?

What I’ve read is that some multi-tenant apps run into this. I’m not sure if it’s 10k per database, or per server. The multi-tenant comments make it sound like a per server issue. I’ve worked on apps that create a database per tenant. (I’d advise against this, but it did have its advantages.) I could see 10k tables happening pretty easily in that kind of architecture.

> unfortunately, the bug is now private

Are there security implications of this bug? If not, then could turning it private have been anything but an abuse of power?

10k tables is not a lot, I've seen instances with more than 1M tables

Not saying it is a good practices just saying it is big QA oversight :(