I have got deadlocks too but postgresql knows how to resolve this so i don't need worry about it.
take a look here: https://www.postgresql.org/docs/9.1/static/explicit-locking.html /*-------------------excerpt------------------------------------------------------------------------------*/ 13.3.3. Deadlocks The use of explicit locking can increase the likelihood of *deadlocks*, wherein two (or more) transactions each hold locks that the other wants. For example, if transaction 1 acquires an exclusive lock on table A and then tries to acquire an exclusive lock on table B, while transaction 2 has already exclusive-locked table B and now wants an exclusive lock on table A, then neither one can proceed. *PostgreSQL automatically detects deadlock situations and resolves them by aborting one of the transactions involved, allowing the other(s) to complete*. (Exactly which transaction will be aborted is difficult to predict and should not be relied upon.) /*-----------------------------------------------------------------------------------------------------------*/ -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
