Help us understand the problem. What is going on with this article?

RDSでgeneral_logとslow_logテーブルをクリアする方法

More than 1 year has passed since last update.

general_log や slow_log の保存先がTABLEにしておくと mysql.general_log とかにレコードが増えていくが、RDSだとこれらのテーブルを直接TRUNCATEとかは出来ない。その代わりにRDSではそれらのログをローテーションするプロシージャが用意されているのでそれを読んでやることで削除が出来ます。
このプロシージャは1回実行すると *_backup というテーブルにリネームするだけなのでまだ削除はされません。ただし1世代しか保存されない作りなので2回実行してやることで完全にレコードを削除することが出来ます。

call rds_rotate_general_log;
call rds_rotate_general_log;
call rds_rotate_slow_log;
call rds_rotate_slow_log;
Why do not you register as a user and use Qiita more conveniently?
  1. We will deliver articles that match you
    By following users and tags, you can catch up information on technical fields that you are interested in as a whole
  2. you can read useful information later efficiently
    By "stocking" the articles you like, you can search right away
Comments
Sign up for free and join this conversation.
If you already have a Qiita account
Why do not you register as a user and use Qiita more conveniently?
You need to log in to use this function. Qiita can be used more conveniently after logging in.
You seem to be reading articles frequently this month. Qiita can be used more conveniently after logging in.
  1. We will deliver articles that match you
    By following users and tags, you can catch up information on technical fields that you are interested in as a whole
  2. you can read useful information later efficiently
    By "stocking" the articles you like, you can search right away