[MDEV-7382] Query log per database or table Created: 2014-12-26 Updated: 2015-01-23 |
|
| Status: | Open |
| Project: | MariaDB Server |
| Component/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major |
| Reporter: | Michael Mussulis | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 1 |
| Labels: | logging | ||
| Description |
|
Hi, It would be extremely useful to have query logs per database or table, especially when debugging projects on servers with multiple projects. For example, our development server has over 50 databases and it is nearly impossible to debug the general log file when so many queries from so many databases are being written to the same log file. We would like each database to have it's own query log, or even better each table to have it's own log file. Cheers, |
| Comments |
| Comment by Sergei Golubchik [ 2015-01-06 ] |
|
Also, it'd make sense to have binary log per, say, per database. With multiple projects in the same MariaDB instance, one doing a huge LOAD DATA will effectively block replication for all other projects as no binlog events can be logged (or read by the slave) in the middle of the big load data event. |
| Comment by Sergei Golubchik [ 2015-01-23 ] |
|
This can be easily done with an audit plugin with no changes to the server |