2015-06-22 13:45 GMT+02:00 Ben RUBSON :
> 2015-06-19 12:08 GMT+02:00 Ben RUBSON :
>>
>> 2015-06-18 22:52 GMT+02:00 shawn l.green :
>>>
>>> On 6/18/2015 2:10 PM, Ben RUBSON wrote:
Hello,
In order for the slave to quickly show a communication issue between
the master and
Yep, as shown below:
root@audit-db.ec2:(none)> select fark from fark from fark fark fark from
frak;
ERROR 1064 (42000): You have an error in your SQL syntax; check the manual
that corresponds to your MySQL server version for the right syntax to use
near 'from fark fark fark from frak' at line 1
ro
Normal general log also logs everything including bad queries (i.e.
SLCECT BLAH BLAH;) - although does not say if it was an error (i.e.
syntax) or not.
Does the audit plugin log the actual error?
Tomasz
On 2015-06-25 00:32, Singer Wang wrote:
The performance hit of the Percona Audit is 15%
The performance hit of the Percona Audit is 15% for disk logging and for
remote syslog we found it is lower. It logs everything including bad
queries (eg. select fark from fark from fark fark fark from frak). You
should be able to write a JSON parser that extracts what you want based on
the log (eg
> From: "Singer X.J. Wang"
> Subject: Re: server-side logging of query errors?
> You could log all queries using the audit plugin, 15% hit..
Fair point, though: maybe one of the different audit plugins has the capability
to specifically log faulty requests. Have a look through the slides from
For immediate release:
http://www.upscene.com/news/item/20150624
Upscene releases Database Workbench 5.1.0
Upscene Productions is proud to announce a new release
of the popular multi-DBMS development tool:
“ Database Workbench 5.1 "
This version is the next big release after version