One way to do it (maybe the only way for selects) is to use the general log. The Id number, 30399, is the thread id. You can look up the thread id in the general log and see the entire command. But you have to have the general log running.
If the command changes data (update, delete, insert) then it'll be in the bin log with the thread id. If you know what time the command was executed, you can use the --start-datetime option of mysqlbinlog. But only the general log keeps selects. On Mon, Oct 6, 2008 at 10:38 AM, MaBa.listas <[EMAIL PROTECTED]>wrote: > Hello, > reading the MySQL documentation I've run into the " show full > processlist\G" command. In my case I've got an output similar to this: > > > ----------------------------------------------------------------------------------------------------------------------------- > mysql> show full processlist\G > *************************** 1. row *************************** > Id: 30127 > User: root > Host: localhost > db: NULL > Command: Query > Time: 0 > State: NULL > Info: show full processlist > *************************** 2. row *************************** > Id: 30399 > User: root > Host: localhost > db: this would be my DB > Command: Sleep > Time: 0 > State: > Info: NULL > > ----------------------------------------------------------------------------------------------------------------------------- > > What I'd like to know is how to get more info about the query > identified with 30399 (in this example). I mean, the exact query, like > "SELECT pr1, pr2 FROM someDB". > > Thanks > > Matias > > -- > MySQL General Mailing List > For list archives: http://lists.mysql.com/mysql > To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED] > > -- Jim Lyons Web developer / Database administrator http://www.weblyons.com
