Tag Info

New answers tagged

1

It's the file size that's the problem. Essentially there's a timeout expiring somewhere, the server logs will tell you where. When the timeout expires, no more data is produced, and after a while with no data the connection gets closed as per normal. The last time I had to tackle something like this (Which is a long time ago now), I wrote a small program ...


1

Since you control my.cnf on EC2, you have two options, neither of which require restarting mysql OPTION #1 : Change old_password Protocol for EC2 Stop replication to the RDS Slave As root@localhost run this on EC2 : SET GLOBAL old_passwords = 0; Start replication to the RDS Slave OPTION #2 : Lower the Security for EC2 Stop replication to the RDS Slave ...


0

I had discussed this in earlier posts Sep 05, 2012 : Is the overhead of frequent query cache invalidation ever worth it? Sep 26, 2013 : query cache hit value is not changing in my database InnoDB internals has a very hands-on approach to the query cache since it micromanages query cache entry invalidation. In the MySQL 4.x days, the query cache was ...


0

You can deploy JIRA on a existing RDS instance itself you just need to create a DB called "jiradb". I guess you might have to change few DB parameters in RDS instance as JURA needs to be run in "STRICT" type for "SQL_mode" You can refer this documentation link on how to Configure your JIRA server to connect to your MySQL database. ...


1

In this specific case (a failed grant statement) stopping the slave, skipping the event, and restarting the slave is likely a safe operation... you just have to do it the RDS way. mysql> CALL mysql.rds_skip_repl_error; This is one of several stored procedures installed on every RDS instance that partially make up for the lack of SUPER privilege. ...


3

You want ALTER DEFAULT PRIVILEGES. Give the rds_superuser default access rights to all new tables. This only affects tables created after the ALTER. For existing tables you must GRANT rights.


0

The public schema is supposed to be visible by all users. You should not restrict rights of public schema to just one group. So, if you do not use: GRANT ALL ON SCHEMA public TO GROUP rds_superuser WITH GRANT OPTION; You may safely work with the public schema with all accounts. If you do not want specific accounts to mess up your public schema tables, ...


1

You are mistaken in your assertion that "the binary log retrieves fine." The output you are seeing is boilerplate output from mysqlbinlog... there's no evidence here that you are actually fetching the binlog. There's no such log file on the server. That's the meaning of this error. SHOW BINARY LOGS; ...to find the available logs on the server. You can ...


1

In your attempt: SELECT id FROM "players" where "players".born_on < "1950-01-01"; Then DELETE FROM "players" WHERE "players".id = 5; DELETE FROM "stats" WHERE "stats".player_id = 5; DELETE FROM "photos" WHERE "photos".player_id = 5; ... repeat First, I don't understand the "...= 5;" one each the subsequent deletes. What is the 5? But....what if ...



Top 50 recent answers are included