Ok, so nevermind... MySQL actually supports the selective replication I
want with the replicate-do-table=db_name.table_name syntax, which I
thought was only available after 4.x. Thanks for all the great
responses that helped me figure this out. :-)
=john
John Stanforth wrote:
Hi folks
Hi folks,
I'm looking for creative ways to setup a replication config that lets me
push all tables to some slaves and only a subset to other slaves. For
this scenario, let's say I have three db servers... One is a master and
gets all updates. One is an update slave, which gets all the master
Jeremy and Michael,
What compiler versions are you using? (just the gcc -v) I'm wondering
especially since MySQL has a warning posted about gcc 2.96 with 2.4 kernels.
Which reminds me, what specific kernel versions are you guys using?
(Jeremy, is yours a custom kernel from Redhat source or L
plain
stumped at this bizarre behavior...
=john
Michael Bacarella wrote:
> We experienced a similar problem with 3.23.51 which went away
> once we compiled from source. Assume this is Linux 2.4?
>
> -M
>
> On Sat, Aug 31, 2002 at 03:08:10AM -0700, John Stanforth wrot
Hi there,
Haven't been watching the list lately so forgive me if this has already been
discussed here recently. Have any of you seen an issue with MySQL 3.23.52
spiralling out of control after a minute or so of operation? We run a
fairly high-volume db, previously running 3.23.49a and upgradin
