With WL36 and WL40 we have:
mysqlbinlog options:
--database=db
--rewrite-db=db_from->db_to
--do-table=db.tbl
--ignore-table=db.tbl
--wild-do-table=pattern.pattern
--wild-ignore-table=pattern.pattern
replication options:
--replicate-rewrite-db=db_from->db_to
--replic
Alexi1952 writes:
Hi Alexi! Sorry for the delay in answering, things have been quite busy...
> With WL36 and WL40 we have:
> mysqlbinlog options:
> --database=db
> --rewrite-db=db_from->db_to
> --do-table=db.tbl
> --ignore-table=db.tbl
> --wild-do-table=pattern.pattern
>
Hi Kristian, Alexi
The current replication filters are borked. I wouldn't put work into
it, but rather leave them (they are used) and add something that works.
Current
- the binlog options prevent things from getting logged locally,
which is bad for point-in-time recovery.
- the replicate
Arjen Lentz writes:
> Current
> - the binlog options prevent things from getting logged locally,
> which is bad for point-in-time recovery.
> - the replicate options work on the slave end, so they still get
> transmitted which is a) slow and b) potential security issue.
Yes. So we filter eithe
Hi Kristian
On 02/10/2009, at 5:22 PM, Kristian Nielsen wrote:
Arjen Lentz writes:
Current
- the binlog options prevent things from getting logged locally,
which is bad for point-in-time recovery.
- the replicate options work on the slave end, so they still get
transmitted which is a) slow and
Hi!
> "Arjen" == Arjen Lentz writes:
>> Filtering on current database (or on whatever for row-based) might
>> be more
>> feasible, though there would still be the additional overhead of
>> decoding each
>> event before sending to each slave.
Arjen> Kristian, your comment, while sound
6 matches
Mail list logo
