Philippe Chal�at wrote: > > 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 ? >
One single task can never cause a deadlock. Deadlock always needs at least two transactions reading/writing the same tables/rows. Of course the share lock is held for the whole select/up to the transaction end (we do not know the isolation level you are working with). How do you know that it is a deadlock? You checked LOCKSTATISTICS or is it just a guess? Please check who is working with your database, too. Elke SAP Labs Berlin > 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]
