Own mysqld per database

Own mysqld per database

am 15.02.2003 01:56:18 von Mark Arnold

Hi,

I have an idea to reduce the interdependencies between my various databases as far as one database needing to be down for
maintenance is affecting other databases on the same server.
If I run one mysqld instance for all the databases on a server (the standard setup), all the databases become unavailable if I take
mysqld down, even though I might have to do maintenance for only one of the databases.
I have seen section 4.7.3 of the manual on mysqld_multi, however, this means defining different ports in all the connect statements
in all my scripts/programs I have.
Since I do have many scripts/db-connection configuration files, this means changing many files on many servers and i will definitely
overlook one or the other file. It also means having to change firewall settings every time I add/remove databases. Is there any way
to come in through the standard port for all the databases and then internally redirecting to the various engines/ports so that my
clients don't have to know about this?

Either as part of the standard MYSQL distribution or some additional add-on/plugin (hopefully a reliable one :) )...

Thanks,

MARK


------------------------------------------------------------ ---------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)

To request this thread, e-mail
To unsubscribe, e-mail
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php