175 reputation
4
bio website
location
age
visits member for 2 years, 8 months
seen Apr 24 '13 at 15:08

Apr
10
comment Is there a workaround for lack of support of cascade triggers with MySQL?
I need cascade update (for other reasons).
Apr
10
asked Is there a workaround for lack of support of cascade triggers with MySQL?
Nov
21
comment Need advises for a new MySQL architecture
I think I am going to go for a partial replication setup: the user tables won't be replicated (which means each website will have its own set of users) whereas the content tables will. Are there any issues to bear in mind while doing partial MySQL replication?
Nov
21
comment Need advises for a new MySQL architecture
Thanks for clusters terrify me (I've heard and read feedback from sysadmins on clustering issues that I definitely don't want to run into). I think I'm going to go with a basic replicated setup for now. If my website is successful and I make a lot of money I'll hire guys like you to setup clustering :)
Nov
20
comment Need advises for a new MySQL architecture
Thanks for your answer Rick. By "each server should have READ-WRITE access to these tables" I mean that the application can execute UPDATE, INSERT, and SELECT queries. In the case of content tables, the application only needs to execute SELECT queries. Thanks for the warnings with splitting techniques. I am thinking of using PHP MySQLnd_ms (php.net/manual/en/book.mysqlnd-ms.php) which allows me to force read queries to the master if needed.
Nov
18
asked Need advises for a new MySQL architecture
May
15
comment ERROR 1100 (HY000) at line 11084: Table 'search_index' was not locked with LOCK TABLES
Using --single-transaction did fix the issue :) Thanks for much. What's weird is that we never had this issue before, it only started occurring yesterday.
May
15
accepted ERROR 1100 (HY000) at line 11084: Table 'search_index' was not locked with LOCK TABLES
May
14
revised ERROR 1100 (HY000) at line 11084: Table 'search_index' was not locked with LOCK TABLES
added 4 characters in body
May
14
revised ERROR 1100 (HY000) at line 11084: Table 'search_index' was not locked with LOCK TABLES
added 1365 characters in body
May
14
asked ERROR 1100 (HY000) at line 11084: Table 'search_index' was not locked with LOCK TABLES
Apr
26
comment Investigate peak in MySQL throughput
Your post looks good. I'll dig into it deeper and try to have those tools ready for next time the issue happens. However last time the issue occurred, the load was so high that the box was practically unusable. We're afraid that if we wait for the issue to happen again, we won't be able to investigate anyway. I understand doing live investigation is better, but isn't there anything we can do using the binlogs at this point?
Apr
26
comment MySQL general query log performance effects
@Aaron Brown: we'currently using a UNIX socket (application and database are on the same server) hence why we can't use tcpdump. Do you think switching from a UNIX socket to a network connection on localhost to be able to run pt-query-digest on tcpdump is worth doing? (i.e. are there big performance differences between UNIX and network sockets)?
Apr
24
asked Investigate peak in MySQL throughput
Jan
26
awarded  Editor
Jan
26
revised Substantial difference between database size under MySQL and actual size on disk
corrected spelling mistake and observations from mysql optimize
Jan
25
awarded  Supporter
Jan
25
awarded  Scholar
Jan
25
accepted Substantial difference between database size under MySQL and actual size on disk
Jan
25
comment Substantial difference between database size under MySQL and actual size on disk
why doesn't the size of the ibdata files reduces if the size of the database does?