content_image/777166.jpg content_image/777174.jpg content_image/777167.jpg
audit_log_read() . Prior to MySQL 8.0.12, audit_log_read_buffer_size  has a default of 1MB, affects all clients, and can be changed only at server startup. 

• audit_log_rotate_on_size 

<img src='content_image/777166.jpg'>

If audit_log_rotate_on_size  is 0, the audit log plugin does not perform automatic size-based log file rotation. If rotation is to occur, you must perform it manually; see Manual Audit Log File Rotation. 

If audit_log_rotate_on_size  is greater than 0, automatic size-based log file rotation occurs. Whenever a write to the log file causes its size to exceed the audit_log_rotate_on_size  value, the audit log plugin renames the current log file and opens a new current log file using the original name. 

If you set audit_log_rotate_on_size  to a value that is not a multiple of 4096, it is truncated to the nearest multiple. In particular, setting it to a value less than 4096 sets it to 0 and no rotation occurs, except manually. 

<img src='content_image/777174.jpg'>

• audit_log_statement_policy 

## Note 

audit_log_rotate_on_size  controls whether audit log file rotation occurs. It can also be used in conjunction with audit_log_max_size  and audit_log_prune_seconds  to configure pruning of rotated JSON-format log files. For details, see Space Management of Audit Log Files. 

<img src='content_image/777167.jpg'>

