[rt-users] is SELECT GET_LOCK normal?

[Bryan McLellan]

I'm having issues with large tickets taking a while to load. FF3, IE7
and Links all show the symptoms where there will be long pauses
between tickets being displayed

RT 3.8.1 (source build) on Ubuntu intrepid amd64, with fast-cgi
mysql-server 5.0.32-7etch5 on Debian etch x86, with huge.cnf

on the mysql server in the "show process-list" shows:
| Id  | User     | Host                             | db       |
Command | Time | State     | Info
                               |
| 220 | rtuser   | client:60233 | rtdb     | Query   |   28 | User
lock | SELECT GET_LOCK('Apache-Session-a085f3079e948dbcff5c416644dce981',
3600) |
| 221 | rtuser   | client:60260 | rtdb     | Query   |   28 | User
lock | SELECT GET_LOCK('Apache-Session-a085f3079e948dbcff5c416644dce981',
3600) |
| 223 | rtuser   | client:60281 | rtdb     | Query   |   28 | User
lock | SELECT GET_LOCK('Apache-Session-a085f3079e948dbcff5c416644dce981',
3600) |

About 20 comments on this ticket. One merge.

The time column continues growing until the page is loaded:  Time to
display: 87.689462

The database has been through a number of upgrades from about 3.6.1.
Perhaps there's something that went wrong in a db upgrade? Maybe I
should try to dump and import the data to a fresh database?

Bryan