On Mon, Jan 21, 2002 at 10:34:03PM -0500, Wendell Dingus wrote: > > I've tried this a bunch of times and different ways and can confirm > that in the 3-server setup I described an alter table does NOT > propogate. Can't see it in the binary log at all. No reference to > the table name, nothing.. Create table and drop table show up and > propogate just fine... Just adding a field to a table or similar do > not.
Hmm... That's odd. Are you replicating *everything*, or is the master (or a slave) set to filter any of the queries based on db or table? Jeremy > -----Original Message----- > From: Jeremy Zawodny [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, January 16, 2002 9:23 PM > To: Wendell Dingus > Cc: [EMAIL PROTECTED] > Subject: Re: Bug in replication 3.23.46-max > > > On Tue, Jan 15, 2002 at 10:59:07PM -0500, Wendell Dingus wrote: > > > > I'm fairly certain this is a bug. It's on 3.23.46-max and the > > changelog for .47 doesn't mention it. > > > > I have 2 servers using replication. Server1 is used by client > > machines and all updates are to it. Server2 stays in perfect sync > > with it and logs all updates to it's own binary log. I then use > > mysqlbinlog from server2 to parse out those database changes every > > half hour or so and send to another server via a (part-time) > > internet connection where it attempts to maintain a synced copy of > > the data as well. A "modify table" to add a new field on server1 > > propogates to server2 but NOT to the third server. I've not tracked > > down exactly where things are breaking down yet. Server1 and 2 are > > Linux and are using INNODB tables. Server3 is not Linux and is not > > able to use INNODB at the moment. Even a "create table > > ... type=INNODB" works on server3 making the table MyISAM > > instead. It's just the modify table statements with the addition of > > a new field that don't make it. > > > > I've not captured and analyzed one of the binary logs yet but will > > try to do so. Just wanted to let someone know of a probable > > bug. I'll also upgrade to .47 and report back if that resolves this. > > But you can see the query in the binary log? Is it just a case of > mysqlbinlog not extracting the query properly? > > Jeremy > > > --------------------------------------------------------------------- > Before posting, please check: > http://www.mysql.com/manual.php (the manual) > http://lists.mysql.com/ (the list archive) > > To request this thread, e-mail <[EMAIL PROTECTED]> > To unsubscribe, e-mail <[EMAIL PROTECTED]> > Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php > -- Jeremy D. Zawodny, <[EMAIL PROTECTED]> Technical Yahoo - Yahoo Finance Desk: (408) 349-7878 Fax: (408) 349-5454 Cell: (408) 685-5936 MySQL 3.23.41-max: up 19 days, processed 440,690,650 queries (264/sec. avg) --------------------------------------------------------------------- Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail <[EMAIL PROTECTED]> To unsubscribe, e-mail <[EMAIL PROTECTED]> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
