The calculator shows 6906.

Antwi: Rathrock: wtf does line 55 do?

Lesley: Thanks Naktibalda got it with a more tricky thing, 1,

Lesley: Is that the typical way to get a substring from the left side to. rather than . right side?

Shepperd: Rathrock: apparently mariadb 5.5 optimizes that subquery and mysql 5.1 doesn’t

Mccort: Naktibalda: yeh i figured

Mirabelli: Rathrock: I guess that somebody tried to get the latest quotes using that subquery

Espinol: Rathrock:

Ancheta: Use GROUP BY and join

Bingham: Brittman, I think that was myisam only

Brittman: Bingham: but i did it with innodb in paste, i think

Brittman: Which i didn’t think was supposed to be possible

Warney: Right thx Naktibalda will look into that

Bingham: Brittman, why are you reading the old docs, seems to have changed later

Brittman: Bingham: says same thing, no? “As a result, the table would contain a single sequence, not a sequence per grp value.”

Bingham: Brittman, but which version are you using

Bingham: Myisam notes section exists in the later doc

Cheeseboro: Rathrock: check if you get correct result from maria, it is possible that mariadb optimized away the trick which made it work in mysql

Keiter: I would still shy away from using such sql, either way

Brittman: Bingham: oh it lets me do this with explict values for the autoinc without a duplicate but does not give me a seq per grp with null/generated value

Brittman: Myisam and innodb are the same when index id exists and innodb requires this index

Noga: Brittman: you’re saying you can get innodb to do groupwise autoinc?

Benno: It looks like your paste tried to change to innodb, failed, then you added the index but didn’t change to innodb again.

Raelson: Oh, wait, I should read better

Koble: I don’t see that you’re inserting NULL though, you’re inserting 1 explicitly

Brittman: Snoyes: yep, figured that out

Brittman: 12:01 Brittman Bingham: oh it lets me do this with explict values for the autoinc without a duplicate but does not give me a seq per grp with null/generated value

Economides: Ok. I’m all caught up now.

Santalucia: After running my newly upgraded mysql server over the weekend, im seeing larger memory usage and this is causing swap to be used. I did not have this issue with 5.1 is there a reason for this and some way to cope with it?

Keiter: Scott0_: larger default values, perhaps.

Lavergne: I only gave it 6.4GB of the server’s 8GB RAM

Keiter: Scott0_: what did you change in my.cnf ?

Huson: Not sure which default values to look at. no I imported the old my.conf then added binlog settings and boosted the RAM up to 6.4GB

Bunson: So I wouldn’t think that would hurt it

Swed: Scott0_: look at and check the variables mentioned in there

Kebe: I am now on 64bit server rather than the 32bit was on

Keiter: Scott0_: congratulations?

Keiter: That being said, you shouldn’t be using 32bit in 2015

Trocinski: Yeah was an old server

Grumet: But the reason I mentioned it is because I was under the impression that 64bit used more memory than 32bit

Keiter: Scott0_: all right – just show your my.cnf if you want constructive comments

Tsai: That calculator needs to be updated. key_buffer_size is deprecated 😛

Bolus: Evening all, when I make changes to /etc/my.cnf do I need to restart the dbserver after making those changes?

Mihatsch: The calculator shows 6906.2MB, which should be fine as I have 8GB of RAm