Skip to main content
Database Administrators
Katafalkas's user avatar
Katafalkas's user avatar
Katafalkas's user avatar
Katafalkas
  • Member for 12 years, 10 months
  • Last seen more than 1 year ago
Profile Activity

77 Actions

All Accepts Posts Badges Comments Revisions Reviews Suggestions
accepted
Redirecting MySQL errors and slow logs into another database
comment
Redirecting MySQL errors and slow logs into another database
hmz ... and then I can use replication to replicate logs to a central log database. Sounds good. Cheers.
asked
Redirecting MySQL errors and slow logs into another database
accepted
mysql read slave to fetch entire database on start
asked
mysql read slave to fetch entire database on start
awarded
 Tumbleweed
accepted
MySQL flush logs, unknown error
asked
mysqlslap number in sql statement to change with iteration
comment
MySQL flush logs, unknown error
It was MySQL 5.5.21 from the first day of installation, and the FLUSH LOGS; used to work fine. For some reason it stopped working now, when I tried using scripts.
comment
MySQL flush logs, unknown error
MySQL version - 5.5.21. I did not upgrade recently. OS: CentOS - 6 . Kernel 2.6.32-220.7.1.el6.x86_64
comment
MySQL slow log configuration
I tried both this script and logrotate, and non of them seem to work. It turned out that flush logs did not work. I started new question on that:dba.stackexchange.com/questions/16339/…
asked
MySQL flush logs, unknown error
awarded
 Commentator
comment
MySQL slow log configuration
Cheers for useful and quick reply, as always. My only concern is about FLUSH LOGS on servers with replication slave or master. Will that influence bin-logs or relay-logs ?
comment
MySQL slow log configuration
But if you have replication happening, will the FLUSH LOGS do influence it some way ?
asked
MySQL slow log configuration
comment
MySQL replication: "Houston, We've Got a Problem"
Cheers for a reply, I'll check out the query logging.
accepted
can't remove "GRANT USAGE"
comment
MySQL replication: "Houston, We've Got a Problem"
totally agree. After this incident, I ll try making all the programers to show me, and test all their "awesome" queries before putting the production. Cheer for info! much appreciated.
accepted
MySQL replication: "Houston, We've Got a Problem"