|
Jason Saunders wrote:
>
>
> Regarding corruption, what if the client ensures that table locking is
> used around each write?
since i don't know how they wrote the code I'm not going to be surprised
at anything here. We'll just have to test it. I would expect that the
locks are in memory and the other mysqld won't know about them.
> In any case, is it certain that the one mysqld will see the other one's
> write, with the memory caches etc. As an example, "INSERT DELAYED" might
> cause problems, as server A may do an "INSERT DELAYED" on a table in the
> database, then server B may try to read from the same table before
> server A decides to sync the on-disk database with the in-memory
> database. Also, the in-memory indices may also be out of sync. Please
> correct me if I'm wrong!
we'll have to find out what is required to write out the changes to disk.
I'm hoping it's either disconnecting from the table, or closing the connection
with the mysqld.
Joe
--
Joseph Mack PhD, Senior Systems Engineer, Lockheed Martin
contractor to the National Environmental Supercomputer Center,
mailto:mack.joseph@xxxxxxx ph# 919-541-0007, RTP, NC, USA
|
