On 2015-06-23 17:29, Johan De Meersman wrote:
None that I'm aware of.
It's a pity!
This could ease debugging in many cases, without the need to change the
client (i.e. PHP/Perl/Python code which sends the queries, and we
suspect that some of them are bogus).
It would be a mild security risk; a malicious
(or just stupid, see Hanlon's razor) user could spam your server with
malformed requests until the logging disk runs full, at which point
the daemon would suspend operations until space is freed.
I don't think it's a valid argument - the same is true right now for
"general query log". Any stupid/malicious user can produce loads of
queries and fill the disk if one has "general query log" enabled.
In short, anyone enabling any logging should consider what limitations
it brings.
Maybe one of the proxies out there has support for such logging, I'm
not really familiar with any of them.
--
Tomasz Chmielewski
http://wpkg.org
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/mysql
