- developers - lists.mariadb.org

Re: [Maria-developers] [GSoC] Kerberize MariaDB -- some unclear point about the project
by QIU Shuang 19 Jun '13

19 Jun '13

Hi serg, Thank you for your comment. I will clean my repo at some later time follow your advice. :) Sincerely, Shuang On Jun 18, 2013, at 4:51 PM, Sergei Golubchik <serg(a)mariadb.org> wrote: > Hi, QIU Shuang! > > Just to answer the bzr part: > > On Jun 16, QIU Shuang wrote: >> The first one is about the private repo and bazaar (I'm a git guy and >> have little experience working with bazaar). In order to make some >> demonstrated progress, I push my local update to the private repo each >> time I create a new commit. It seems the commit number is global (see >> the screen shot of my private repo history below). >> >> Recent revisions >> 3796. By Shuang Qiu 20 hours ago >> prototype with GSSAPI enabled >> 3795. By Shuang Qiu on 2013-06-15 >> Kerberos plugin prototype with raw krb5 API >> 3794. By Shuang Qiu on 2013-06-13 >> doodle >> 3793. By Michael Widenius on 2013-06-11 >> Fixed tests that failed on 32 bit because of my earlier fixes of 32 bit limits. >> 3792. By Sergei on 2013-06-07 >> MDEV-4468 Assertion `error != 0' fails or timeout occurs on select from a FEDERATED table which points at a non-existent table >> >> I'm afraid that my commits may pollute the code base. So the question >> is that will others (e.g. Sergei since commit 3792) see my changes >> next time he gets local branch updated. Is it the best practice to >> use bazaar like this (push after each commit)? > > Don't worry about it. Revision numbers in bzr aren't stable, during a > merge they might be renumbered (*). Revision ids are stable and unique, > but they look like > > sergii(a)pisem.net-20130607133513-p27s1bg8gt0amkiw > > (this is for my commit with revno 3792 above). > Think of revision numbers as of convenient shortcuts that help to avoid > typing and that are easy to remember. But don't use them for long-term > references or something. > > And no, I won't see your changes when I pull from 5.5. > Not unless I pull from your repository. > > Regards, > Sergei > > [1]. Details. Example. Say you have a repo with only one changeset. It > has revno 1. You've branched. And you've made changes and committed > something in both branches, independently. Every branch has now two > changesets. Changeset 1 (it's the same in both, save revid), and > Changeset 2 (revno is the same, revid is different). Now if you merge > the second branch into the first, the changeset 2 of the second branch > will be renumbered, it'll get revno 1.1 (but its revid won't change). > The history will look like (Changeset 3 is the merge changeset): > > 1 > | \ > 2 1.1 > | / > 3 > >

1 0

[Maria-developers] mysql 5.6, 5.7
by Roberto Spadim 18 Jun '13

18 Jun '13

hi guys, i was reading mysql 5.6 and 5.7 manual i know that mariadb is very different (a bit) than mysql internally there's a mysql merge issue or something like that i can see what will be merged and what not? i like the partition lock prune, memcache and optimizer tracer of mysql 5.6, but today i'm not using it in mariadb (not a problem, but it's nice features) -- Roberto Spadim

3 6

Re: [Maria-developers] review / close MDEV-4581
by Roberto Spadim 18 Jun '13

18 Jun '13

nice! thanks sergei! i think it's now rich in features, maybe should be used by community to check if it's usefull (there's many columns) thanks again! 2013/6/18 Sergei Golubchik <serg(a)mariadb.org> > Hi, Roberto! > > On Jun 18, Roberto Spadim wrote: > > hi guys, could review / close > > MDEV-4581<https://mariadb.atlassian.net/browse/MDEV-4581> ? > > Roberto, as you can see in Jira, > MDEV-4581 is assigned to me, it's targeted for the 10.0.4 release. > So yes, I could and I will. > > Regards, > Sergei > -- Roberto Spadim SPAEmpresarial

1 0

Re: [Maria-developers] close some mdev
by Roberto Spadim 18 Jun '13

18 Jun '13

hi sergei! thanks about others mdev, and yes mdev 4583 shouldn't be closed, i will study a bit more to see what can be done to write a patch about it and test the speed of a procedure removing query cache queries 2013/6/18 Sergei Golubchik <serg(a)mariadb.org> > Hi, Roberto! > > On Jun 17, Roberto Spadim wrote: > > hi guys could anyone close some opened and fixed (won't fix) mdev's ? the > > comment explain why to close it > > > > MDEV-4571 <https://mariadb.atlassian.net/browse/MDEV-4571> > > MDEV-4589 <https://mariadb.atlassian.net/browse/MDEV-4589> > > MDEV-575 <https://mariadb.atlassian.net/browse/MDEV-575> > > Closed. > > > MDEV-4583 <https://mariadb.atlassian.net/browse/MDEV-4583> > > Not closed, it doesn't have a comment like the three above? > Should I still close it? > > Regards, > Sergei > -- Roberto Spadim SPAEmpresarial

1 0

[Maria-developers] a problem of Parallel replication
by nanyi607rao 18 Jun '13

18 Jun '13

hi, when i read patchs from http://bazaar.launchpad.net/~knielsen/maria/dingqi-parallel-replication/cha…, i found a problem (maybe would cause bug) :main SQL thread read a event from relay log, it make the log_event->thd point to the thd of main SQL thread. But when a log_event is disaptched to a sub SQL thread, the log_event->thd still point to the old value instead of the thd of sub SQL thread. this problem will lead check_stack_overrun() fails, then lead open_table() fails... maybe this will be helpful to you . 2013-06-18 nanyi607rao

1 0

[Maria-developers] review / close MDEV-4581
by Roberto Spadim 18 Jun '13

18 Jun '13

hi guys, could review / close MDEV-4581<https://mariadb.atlassian.net/browse/MDEV-4581> ? -- Roberto Spadim

1 0

[Maria-developers] Implementing implicit primary key in mysql server
by Lixun Peng 18 Jun '13

18 Jun '13

Hi, As we know, InnoDB has implicit primary key if a table hasn't defined a primary key. However MySQL server doesn't know this primary key, so this primary key will not apear in binlog. When we are using ROW format binlog for replication, if a table has no any indexes, that's a disaster. If a table without indexes do a DML (UPDATE/DELETE), of course it will run a long time in master, but in slave, it still need a long time. It will cause serious slave replication delay. For example: binlog_format=ROW; CREATE TABLE table1 ( col1 varchar(32), col2 int ); table1 hasn't any indexes, if table1 has 100 million rows, I do a query "UPDATE table1 SET col1='xxx' WHERE col2=100", and this query will effect 1 million rows. Then it has 1 million UPDATE events in binlog. After slave received these events, each events should scan all rows!!! It will cause serious replication delay! I saw:https://kb.askmonty.org/en/row-based-replication-with-no-primary-key/ But if no any indexes, it still a problem. I think mysql server can do the same thing as InnoDB do, if user doesn't define the primary key, mysql can add the primary key automatically. For example: If user create a table like "table1", we can do "ALTER TABLE table1 ADD __id bigint auto_increment, ADD PRIMARY KEY(__id)", so in fact, the "table1" structure is CREATE TABLE table1 ( col1 varchar(32), col2 int, __id bigint auto_increment primary key ); But when user do "SELECT * FROM table xxx" or "INSERT INTO table VALUES(xx)", we should ignore implicit primary key, "__id" will not apear in the result set. How do you think? Thanks, Lixun -- Senior Database Engineer @ Taobao.com Mobile Phone: +86 18658156856 (Hangzhou) Gtalk: penglixun(at)gmail.com Twitter: http://www.twitter.com/plinux Blog: http://www.penglixun.com

1 0

[Maria-developers] close some mdev
by Roberto Spadim 18 Jun '13

18 Jun '13

hi guys could anyone close some opened and fixed (won't fix) mdev's ? the comment explain why to close it 1. MDEV-4571 <https://mariadb.atlassian.net/browse/MDEV-4571> 1. MDEV-4583 <https://mariadb.atlassian.net/browse/MDEV-4583> 1. MDEV-4589 <https://mariadb.atlassian.net/browse/MDEV-4589> 1. MDEV-575 <https://mariadb.atlassian.net/browse/MDEV-575> -- Roberto Spadim SPAEmpresarial

1 0

Re: [Maria-developers] Jira new field
by Roberto Spadim 17 Jun '13

17 Jun '13

ok =) thanks 2013/6/17 Sergei Golubchik <serg(a)mariadb.org> > Hi, Roberto! > > On Jun 17, Roberto Spadim wrote: > > > > today i'm 'working around ' this, and putting the 'group information' in > > MDEV issue, example.. query cache things i put > > QUERY CACHE - some issue title > > processlist things i put > > PROCESSLIST - some issue title > > > > this works too, but well. mariadb team can change and when i lost my > memory > > (some times =) ) i need to read all issues again and find where i put the > > information > > You can certainly add labels like QUERY CACHE and PROCESSLIST. This > shouldn't be a problem. > > Regards, > Sergei > -- Roberto Spadim SPAEmpresarial

1 0

Re: [Maria-developers] Jira new field
by Roberto Spadim 17 Jun '13

17 Jun '13

heeh sometimes i just add a label that don't have interest to mariadb team, it's just to 'group' my issues if there's a interesting and nice way to do this could be nice it's just to organize my issues and when i have time see what changed and where, not changing the work of mariadb placing the right label in the right issue 2013/6/17 Sergei Golubchik <serg(a)mariadb.org> > Hi, Roberto! > > On Jun 17, Roberto Spadim wrote: > > hi guys, could we add a Reporter Label inside jira issue? instead of only > > Label (used by mariadb team) > > it's easier to filter issues, thinking about the reporter filter not for > > mariadb team filters > > But you can add your labels to the Label field, why would one need > another list of Labels? > > Regards, > Sergei > -- Roberto Spadim SPAEmpresarial

1 3