John Roddy wrote:
I know that successful, data changing queries get logged in the binary log. But
is there any
> way to see the actual queries that fail (i.e. timeouts, deadlocks)?
I'm hoping there's a
> way other than using the general query log, which takes up too much
space just to catch
>
I know that successful, data changing queries get logged in the binary log. But
is there any way to see the actual queries that fail (i.e. timeouts,
deadlocks)? I'm hoping there's a way other than using the general query log,
which takes up too much space just to catch that occasional failed upd
