[mythtv] [mythtv-commits] Ticket #10391: Slow MythTV startup if DB has many tables
Nigel Pearson
nigel at ind.tansu.com.au
Wed Feb 29 01:10:09 UTC 2012
On 29/02/2012, at 11:36 AM, Gavin Hurlbut wrote:
> Maybe I'm dense here, but how did a user get hundreds or thousands of
> tables in a database that we designed?
Sadly, INFORMATION_SCHEMA.TABLES lists info on all
the databases in MySQL, not just our mythconverg:
mysql> SELECT table_schema,table_name FROM INFORMATION_SCHEMA.TABLES;
+--------------------+---------------------------------------+
| table_schema | table_name |
+--------------------+---------------------------------------+
| information_schema | CHARACTER_SETS |
...
| information_schema | USER_PRIVILEGES |
| information_schema | VIEWS |
| mysql | columns_priv |
| mysql | db |
...
| mysql | user |
| mythconverg | callsignnetworkmap |
| mythconverg | capturecard |
...
| mythconverg3 | websites |
| test | callsignnetworkmap |
^C
1) Our current SELECT in DBUtil::GetTables() does anchor it to the current database name, so it should always return just mythconverg's hundred tables.
2) In my slight, random testing, sometimes the query takes a long time.
But yes, it does seem unlikely.
I haven't had time to follow up with the reporters,
and haven't created a huge database for full testing yet.
Low priority.
--
Nigel Pearson |"I haven't tested it yet, |
nigel at ind.tansu.com.au | but it should be perfectly safe." |
Telstra, Sydney, Australia |"Just a bit of harmless brain |
9202 3900, fax 9212 6348 | manipulation, that's all" - Wallace|
More information about the mythtv-dev
mailing list