Sagewire Logo

mysql internals RSS Feed

Recent Posts View Recent Posts | View Archived Posts

Message from stewart
Most recent post: 6/25/2007
2 authors and 2 replies.

(sent to @xxxxxxxxxxx instead of @xxxxxxxxxxx by mistake, reposting for benefit
of all)

Hi all,

I have updated the Master_Bind patches based on feedback.

New things here:
- Master_Bind in SHOW SLAVE STATUS moved to the end
Mark, Chip, Guilhem, Sinisa: you guys have more real world
experinece with these changes and the resulting potential chaos.
Is this a much better solution? If anyone can test some of the
random scripts around,'d be great. Do you forsee any other
problems?

- All the test results updated due to the creation/move of the
Master_Bind column

- mysql-test-run.pl is passing with stmt and row based rpl. Possibly
some other test will "fail" because of the new column that is not
run in my build... hoping pushbuild will pick this up (is trivial
fixes).

- Fixed a (at least potential) bug when sending the Master_Bind column
out for SHOW SLAVE STATUS.. turns out previously I was sending twice.

My primary concerns:
- Client side bind: does this break any binary compatibility?
I'm not familiar enough with the client library to judge this.

- Kay's patch for replication delay will need some merging love with this.
Hopefully the test suite will help in picking up if this is merged wrongly..

- behaviour when you set Master_Bind to something silly (e.g. '42').

Where this is heading:
- Currently only to the mysql-5.1-telco tree (MySQL Cluster Carrier Grade
Edition).

- Do not know of any plans for it to hit the read more about [patch 0/6] Bind patches for telco tree (take 2)


Message from yogesh
Most recent post: 1/5/2007
3 authors and 3 replies.

what are the compatable issues occurs , both are different version
level , can any one tell how to

neglate the error or how to over come the compatable issues ........ read more about what are the changes from mysql4.1.7 to mysql5.0.27


Message from binary-nomad
Most recent post: 11/2/2005
7 authors and 9 replies.

How do I make a table with fields again, say, name, age, address, wife
etc. that I want people to be able to look at (with any client like
MysqlCC etc), but only be able to modify certain fields, eg. wife (this
includes deleting the field from the database, maybe) - the name, age
etc. must be left intact, ie. not changeable by anyone.Thanks. read more about Privileges on specific fields in a DB


Message from jonas
Most recent post: 10/5/2005
2 authors and 2 replies.

Below is the list of changes that have just been committed into a local
5.1 repository of jonas. When jonas does a push these changes will
be propagated to the main repository and, within 24 hours after the
push, to the public repository.
For information on how to access the public repository
see http://dev.mysql.com/doc/mysql/en/installing-source-tree.html

ChangeSet
1.2031 05/10/04 20:54:17 jonas@xxxxxxxxxxx(none) +2 -0
ndb diskdata
expand mysql-test-case

mysql-test/t/ndb_basic_disk.test
1.7 05/10/04 20:54:09 jonas@xxxxxxxxxxx(none) +8 -0
add usage of alter tablespace/logfile group

mysql-test/r/ndb_basic_disk.result
1.4 05/10/04 20:54:09 jonas@xxxxxxxxxxx(none) +6 -0
add usage of alter tablespace/logfile group

# This is a BitKeeper patch. What follows are the unified diffs for the
# set of deltas contained in the patch. The rest of the patch, the part
# that BitKeeper cares about, is below these diffs.
# User: jonas
# Host: eel.(none)
# Root: /home/jonas/src/mysql-5.1-ndb-dd

--- 1.3/mysql-test/r/ndb_basic_disk.result 2005-09-28 11:27:28 +02:00
+++ 1.4/mysql-test/r/ndb_basic_disk.result 2005-10-04 20:54:09 +02:00
@xxxxxxxxxxx@xxxxxxxxxxx -4,11 +4,17 @xxxxxxxxxxx@xxxxxxxxxxx
INITIAL_SIZE 16M
UNDO_BUFFER_SIZE = 1M
ENGINE=NDB;
+alter logfile group lg1
+add undofile 'undofile02.dat'
+initial_size 4M engine=ndb;
CREATE TABLESPACE ts1
ADD DATAFILE 'datafile.dat'
USE LOGFILE GROUP lg1
INITIAL_SIZE 12M
ENGINE NDB;
+alter tablespace ts1
+add datafile 'datafile02.da read more about bk commit into 5.1 tree (jonas:1.2031)


Message from jonas
Most recent post: 10/5/2005
2 authors and 2 replies.

Below is the list of changes that have just been committed into a local
5.1 repository of jonas. When jonas does a push these changes will
be propagated to the main repository and, within 24 hours after the
push, to the public repository.
For information on how to access the public repository
see http://dev.mysql.com/doc/mysql/en/installing-source-tree.html

ChangeSet
1.2031 05/10/03 10:41:34 jonas@xxxxxxxxxxx +1 -0
ndb diskdata
fix various testBasic w/ atleast 2 fragments (nodes)
bug was invalid alignement of disk part in case of chained row commit

storage/ndb/src/kernel/blocks/dbtup/DbtupCommit.cpp
1.60 05/10/03 10:41:17 jonas@xxxxxxxxxxx +1 -1
Fix alignment of disk part in case of while committing chained row

# This is a BitKeeper patch. What follows are the unified diffs for the
# set of deltas contained in the patch. The rest of the patch, the part
# that BitKeeper cares about, is below these diffs.
# User: jonas
# Host: perch.ndb.mysql.com
# Root: /home/jonas/src/mysql-5.1-ndb-dd

--- 1.59/storage/ndb/src/kernel/blocks/dbtup/DbtupCommit.cpp 2005-09-28 10:25:22 +02:00
+++ 1.60/storage/ndb/src/kernel/blocks/dbtup/DbtupCommit.cpp 2005-10-03 10:41:17 +02:00
@xxxxxxxxxxx@xxxxxxxxxxx -243,7 +243,7 @xxxxxxxxxxx@xxxxxxxxxxx
}
if(0) ndbout_c("");
disk_ptr = (Tuple_header*)
- (((Uint32*)copy)+Tuple_header::HeaderSize+fix_size+sz);
+ (((Uint32*)copy)+Tuple_header::HeaderSize+fix_size+((sz + 3) 2));
}
else
{ read more about bk commit into 5.1 tree (jonas:1.2031)




7/24/2008 10:55:21 PM

Programming | Sports | Autos

copyright 2006
Valid XHTML 1.0 Transitional