Hello Phillipe, for telling what's going on here, please take a look (with an additional session) on the system table LOCKSTATISTICS.
In that table you can see what locks are held, and what locks are requested, and how they possibly collide to a deadlock. Regards Alexander Schr�der SAP DB, SAP Labs Berlin > -----Original Message----- > From: Philippe Chal�at [mailto:[EMAIL PROTECTED] > Sent: Wednesday, April 28, 2004 1:02 PM > To: [EMAIL PROTECTED] > Subject: Multiple share lock one select > > > Hello, > > I've some deadlock problem due to select statement. A > read-only session > causes a deadlock with a simple select. I guess it's because > my select > has sub-select and the share lock put when reading the sub-select is > kept when putting the shared lock for the main select. Is > this possible > ? Any solution to avoid this ? > > Thanks > > Philippe > > -- > MaxDB Discussion Mailing List > For list archives: http://lists.mysql.com/maxdb > To unsubscribe: > http://lists.mysql.com/[EMAIL PROTECTED] > -- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
