Gary Richardson wrote:
There are a bunch of queries that happen on the master for statistical
purposes that don't use temp tables and generate large amounts of
data. These queries don't need to run on the slaves and in fact slow
it down quite a bit.
If the queries modify tables that are being
So I gather you are creating a table, and doing some work in it, but
even though it isn't declared 'temporary' it really is and you don't
want it replicated?
If this is the case you can create the table in a separate database, and
in your mysql configuration tell the binary logging to exclude
Try SET SQL_LOG_BIN=0 before you run your queires on master. This will be valid for
that connection only.
-Original Message-
From: Gary Richardson [mailto:[EMAIL PROTECTED]
Sent: Thu 10/21/2004 11:24 AM
To: Mysql General (E-mail)
Subject: Ignore a single query in replication
Hey,
Is
If the queries modify tables that are being replicated, then how would
the slave remain
in sync with the master if it didn't replicate them?
These are essentially temporary tables that aren't defined as such --
they typically take a long time to derive (30 minutes to an hour) and
are used for
If this is the case you can create the table in a separate database, and
in your mysql configuration tell the binary logging to exclude that
database. Then anything in that specific database won't get replicated,
I believe you can only do this exclusion on the database level, not per
table.
This was exactly what I was looking for :) Too bad you need to be
SUPER to do it :(
Thanks.
On Thu, 21 Oct 2004 12:44:11 -0700, Sanjeev Sagar
[EMAIL PROTECTED] wrote:
Try SET SQL_LOG_BIN=0 before you run your queires on master. This will be valid for
that connection only.
Gary Richardson wrote:
These are essentially temporary tables that aren't defined as such --
they typically take a long time to derive (30 minutes to an hour) and
are used for multiple queries afterwards before being dropped.
In that case, why not just ignore those tables for replication? I
