meta user
network profile
| bio | website | |
|---|---|---|
| location | Cincinnati, OH | |
| age | 42 | |
| visits | member for | 8 months |
| seen | 1 min ago | |
| stats | profile views | 101 |
If you question the superiority of the relational model... you're doing it wrong.
|
1d |
comment |
MySQL Master/Slave. Actual use of Slave Machine +1 very good point about "split brain" since MySQL replication will not detect this condition until one of the mismatched (or missing) (or extra) rows on the slave is referenced by, or causes a constraint violation in response to, an event replicated from the master. |
|
May 17 |
comment |
Mysql 5.6 and install php5-mysql , mysql-common Have you tried it? |
|
May 15 |
comment |
Why does copied MySQL database have different data than source? Are the source tables MyISAM or InnoDB? |
|
May 15 |
comment |
How do I use subquery on the same table in MySQL? Posting the output of SHOW CREATE TABLE table_name; might be helpful, as might the output of EXPLAIN SELECT * FROM table_name WHERE value_was IS NULL OR value_was <= value_now; Also, the (value_was,value_now) index should still improve performance of the first query, depending on what other indexes are already there... have you tried that? |
|
May 13 |
comment |
InnoDB Failure of some kind Try to make it 4 does not make sense. You need 0 (default) at all times unless you are in the middle of trying to recover from data corruption. You cannot do inserts with innodb_force_recovery set to any nonzero value. It is an emergency only setting. If it was already 6 you likely have an unstable installation and should not be deploying new databases on it. |
|
May 13 |
comment |
Repair with 1 thread Also, the question only mentions one index on the table ("1 primary key") so that would just be one thread in any case. |
|
May 12 |
comment |
mysql replication successful but slave not replicating If you SHOW PROCESSLIST on the master, do you see the incoming connection from the slave? You should. Also, I would try STOP SLAVE IO_THREAD; then START SLAVE IO_THREAD; on the slave and see how the output of SHOW SLAVE STATUS (on the slave) changes, if at all. |
|
May 12 |
comment |
mysql replication successful but slave not replicating Do not look at SHOW MASTER STATUS on the slave. This information is not relevant unless the slave is also serving as a master for other slaves further downstream. |
|
May 12 |
comment |
mysql replication successful but slave not replicating When Replicate_Do_DB is not set, all databases are replicated. |
|
May 12 |
comment |
'Offline' MySQL backup - server not starting The "partition" is too full? Meaning the hard drive partition? What's the exact error message? |
|
May 10 |
comment |
How to use and optimize subquery on 100 million rows The answer depends, in part, on whether domain_ID is the primary key or is at least a unique key in domain_setting. I'm resisting the temptation to assume that it is. |
|
May 9 |
comment |
Req: Typical location of mysql query cache CodeIgniter stores queries on disk and calls this the "query cache.“ This is unrelated to the MySQL query cache: ellislab.com/codeigniter/user-guide/database/caching.html... |
|
May 9 |
comment |
Master updates Slave but not Master itself Then, unless I failed to find the relevant place in the source for the documented trimming behavior, I would suggest it must have been the first alternative, the event was sent to the slave and never committed to the master binlog on disk ... you had a hardware crash and sync_binlog = 0 making this scenario very probable. |
|
May 9 |
comment |
how to avoid the maximum--execution time error This is a PHP configuration issue, not MySQL. |
|
May 8 |
comment |
Plugin 'FEDERATED' is disabled EasyPHP apparently (gasp) installs MySQL with an empty root password... so unless you have set that password, you should probably not specify the -p. |
|
May 6 |
comment |
Error “#1118 - row size too large” on the first row of the table only Ah, sorry, since there are some skipped numbers, I assumed you had omitted some columns. What is the major/minor/release version of your server? (e.g., 5.1.67) |
|
May 4 |
comment |
Error “#1118 - row size too large” on the first row of the table only Don't get distracted by the fact that you're using TEXT columns and the error message mentions TEXT columns... To identify this problem, you need to look at all of the other columns, the ones that aren't TEXT, which aren't currently shown in the output above. It's not likely these text columns that are causing the problem -- even if updating one of them triggers the error -- it's something in one of the other columns that's pushing the row size over the ~8000 byte limit for InnoDB. Post all of the columns, please. |
|
May 4 |
comment |
Insert data in current table and update another table MySQL That is explained in the answer -- but I'll rephrase it a bit to make it less situation-specific: you can reference the current value of a column on the right-hand side of an assignment "=" equals operator in an update query, so, for example, in a table called payroll with a column called salary you can simply UPDATE payroll SET salary = salary + 5000 WHERE employee = 'sqlbot' to give me a pay increase. |
|
May 4 |
comment |
Ubuntu / MySQL - How to choose from the various downloads? +1 for a very useful link. As a DBA, I trust the package manager for everything but MySQL, because I want to be the only one deciding whether there will be any monkeying about with the files associated with my MySQL instances (so my choice, for me, would be #1) but you're spot-on with your advice in this case... sudo apt-get install mysql-server -- it doesn't get much more straightforward than this. |
|
May 2 |
comment |
How to avoid lagging when enabling log-slave-updates? To clarify... you are saying that enabling log-slave-updates or not is the single factor in your environment that makes the difference between whether your slave can keep up or not.. correct? |
