You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm not managing databases with puppet, however this module will always loop all databases and do a "show variables" on them.
This currently takes ~60 seconds for ~4.000 database.
Debug: Executing: '/usr/bin/mysql --defaults-extra-file=/root/.my.cnf -NBe show variables like '%_database' db_982'
Describe the Solution You Would Like
If I'm not managing databases via the module at all, maybe this information is not required for everything else to function, and the module could detect itself if it isn't managing databases.
Describe Alternatives You've Considered
An alternative could be a new parameter to just disable this behaviour on demand.
The text was updated successfully, but these errors were encountered:
mysql_caller(["show variables like '%_database'",name],'regular').split("\n").eachdo |line|
k,v=line.split(%r{\s})
attributes[k]=v
end
new(name: name,
ensure: :present,
charset: attributes['character_set_database'],
collate: attributes['collation_database'])
end
end
a single query of the information_schema database could do the job.
ie this single query should return everything required to create the mysql_database instances. select SCHEMA_NAME,DEFAULT_CHARACTER_SET_NAME,DEFAULT_COLLATION_NAME FROM information_schema.SCHEMATA;
It'd need testing on all the mysql variants the module supports though...
Use Case
I'm not managing databases with puppet, however this module will always loop all databases and do a "show variables" on them.
This currently takes ~60 seconds for ~4.000 database.
Describe the Solution You Would Like
If I'm not managing databases via the module at all, maybe this information is not required for everything else to function, and the module could detect itself if it isn't managing databases.
Describe Alternatives You've Considered
An alternative could be a new parameter to just disable this behaviour on demand.
The text was updated successfully, but these errors were encountered: