Perman: Pom999: there is no conflict between these features
Youngquist: Bdn: that’s not a random number
Kretzschmar: Ok then let’s call it pseudorandom
Whaler: SuperQ: so I i use innodb_max_dirty_pages_pct to flush my data to a disk, does the data still stays in the memory and innodb_buffer_pool_dump_at_shutdown will save the metadata?
Delore: Bdn: not sure how to ensure uniqueness
Blatchford: Jonfatin-: you can use “USING id” if you are joining transactions.id to log_items.target_id.
Genna: Pom999: Yea, when you flush dirty pages, they stay in ram, but are now “clean”
Moscardelli: Oh, cool,. thanks SuperQ!
Clagg: Snoyes: why can’t he?
Fucci: Jonfatin-: change the “USING id” to transactions.id = log_items.target_id
Bownds: Pom999: the pct just determines how many pages are “dirty”, as in the transactions are written to binlogs, and written to innodb in ram, but haven’t been stored on disk
Colesar: Dbolser: because the field names are different.
Fequiere: Pom999: In the event of a crash, pages that are dirty have to be restored from disk, have the binlog applied to them, and then you can start serving
Caughell: Jonfatin-: and then change SELECT id to SELECT transactions.id AS transactionId, log_items.id AS logItemId
Kretzschmar: Thanks for the help so far, any other ideas?
Detzel: SuperQ; we need to restart mysql servers, so my goals is to restart fast and yet use content caching, so plan to use innodb_max_dirty_pages_pct and innodb_buffer_pool_dump_at_shutdown
Umholtz: Bdn: does your posts table have a primary key?
Sinrich: Pom999: Yea, that’s what I do
Kretzschmar: Yes it has a primary key
Colon: Pom999: I personally find the innodb_max_dirty_pages_pct default to be wayyyyyyyyyyy too big
Manwarren: Pom999: for a modern server with 10s of GB of innodb ram
Arbuckle: Snoyes: what did I do wrong? ERROR 1066 42000: Not unique table/alias: ‘transactions’
Folkman: Mysql SELECT transactions.id AS transactionId, log_items.id AS logItemId,identifier,transactions.created_at,action,log_output FROM transactions LEFT JOIN log_items transactions.id = log_items.target_id WHERE status=’running’ AND transactions.created_at current_timestamp – INTERVAL 1 HOUR;
Kolkmann: Pom999: for servers with say, 128GB of ram, I target innodb_max_dirty_pages_pct to 5%
Frerich: Jonfatin-: missed the ON
Wyman: Hi guys, when setting a default for a column that is of type TINYINT1 should I set the default as 1 or ‘1’ and what the heck is the difference?
Jordon: LEFT JOIN log_items ON.
Zambarano: Bear: 1 is a number. ‘1’ is a string.
Banis: Snoyes: I know it’s a string, but does MySQL evaluate as best as it can as a value?
Demar: Snoyes: thanks that worked :- Your amazing
Demeritte: Snoyes: even mysql worbench says the default value is ‘0’ if I use 0
Woolums: Agree SuperQ. do you normally change the parameter from default?
Carvey: Bear: MySQL quietly does terrible things with implicit casting
Watsky: Pom999: Yes, I leave it at a much lower value all the time
Tur: Pom999: So that there isn’t more than a few GB of oustanding writes needed for any server
Feasel: SuperQ make sense, I will consider it
Pol: Bear: workbench really says ‘0’, not b’0′?
Marrujo: I’ve re-worked how we do most maintence work, so we never need to do fast restarts
Malsom: But it’s still annoying to have them take forever to shutdown when doing OOB work :
Larrieu: I’m having trouble authenticating to the mail accounts database in the mailadmin page
Shackleton: I’m setting a mail server
Kirschbaum: How do i check for errors?
Flemming: Asterismo: what has that to do with mysql?