Przemyslaw Popielarski wrote:
>>I'm executing on master a long and complicated query such:
>>UPDATE (lots of tables, lots of LEFT JOIN) SET ... WHERE .
>
>
> Okey, I simplified the query to:
> -----
> UPDATE
> tKsidata,
> tKsiabeksiazki
> SET
> tKsidata.STAN_REALNY=tKsiabeksiazki.STAN
> WHERE
> tKsidata.ksi='0815120877' and
> tKsidata.KSI=tKsiabeksiazki.KSI
> -----
>
> This query shows up in both master's and slave's log, but it DOES NOT
> execute on slave. Table tKsidata on slave remains unmodified.
>
> Executing the query manually works perfectly on slave.
>
> Is seems that multi-table update badly replicates in MySQL 4.1.
>
Przemyslaw:
Check if you have any replication restricting rules on the slave. There might be
a bug that incorrectly flags a query to be excluded. If that is the case, then
try to re-write the rules to see if you can get around the bug.
Also, try building 4.1.7 from source - there was another user that was reporting
a really strange crash that went away after he complied the binary himself. So
there is some strong evidence that the standard MySQL 4.1.7 binary was not built
properly, in which case, odd behaviour is to be expected.
--
Sasha Pachev
Create online surveys at http://www.surveyz.com/
