Prepared statements are written to general query log after being executed

Bug #1182949 reported by Sergei Glushchenko on 2013-05-22
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MySQL Server
Unknown
Unknown
Percona Server moved to https://jira.percona.com/projects/PS
Fix Released
Medium
Unassigned
5.1
Won't Fix
Medium
Sergei Glushchenko
5.5
Fix Committed
Medium
Sergei Glushchenko
5.6
Fix Released
Medium
Unassigned

Bug Description

Prepared statements logged to general query log and audit plugin notified after statement being executed unlike most other log events which are written before query being executed.

Related branches

Sergei -

This is an upstream bug, isn't? Can you link one here?

It seems that, for prepared statements, not only executing, but preparing is affected too.

Alexey Kopytov (akopytov) wrote :

Preparing a client-side prepared statement is currently ignored by the scalability metrics plugin anyway (its current implementation only tracks COM_QUERY and COM_STMT_EXECUTE).

Also, as there's no audit plugin interface in 5.1, do we really want to fix this in 5.1?

Preparing the statement can easily be tracked by scalability metrics plugin and I am going to implements this.
I agree that we can mark it as won't fix for 5.1. Does somebody has an objections?

Upstream is fixed in 5.7, do we want to port the fix into 5.1/5.5/5.6 ?

Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-1372

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Related blueprints

Remote bug watches

Bug watches keep track of this bug in other bug trackers.