Is there a halfway house between a single database and a full master-slave setup?
I have a database with one "piggish" table, and I'd like to direct queries that search the
pig to a duplicate database, where it won't affect all the routine traffic.
I could definitely do this by setting up a slave server, but for my purposes it would be
just as effective, and lots easier, if mysql could automatically maintain a duplicate of
the database. Presumably this would work internally like an internal auto-slave, with a
binary log of changes to the master database self-consumed to maintain the duplicate.
As a bonus, I could backup the duplicate instead of the master, so that won't affect the
routine traffic either.
