Menu
▾
▴
#344 pgsql locking deadlock
Hi,
I've encountered a deadlock problem when using
Phpwiki-1.3.9 with Postgrsql. Maybe this is not only
our problem - try looking for
phpwiki error deadlock
on google - there are some pages that returned this
error to google.
I've tried to solve this problem in our modified
version of your phpwiki. I suggest to change the
queries working with the phpwiki database. The problem
is maybe in the fact that tables are locked in one
order by the locking function (using the LOCK command)
and in another order automatically by postgres when
accessing multiple tables at once - probably in the
order they are written in the query.
I'm not sure this problem is in you new versions of
phpwiki - i saw the removed locking code
somewhere..this is just to inform you of the possible
cause of the problem. Our problem disappeared after
changing
the order of tables in queries.
With best regards,
Peter Hoffmann (kappa@centrum.cz)
Logged In: YES
user_id=13755
We are aware of the locking problems in better databases,
and work on changing locking to transactions.
Latest CVS has no pgsql locking anymore, only transactions,
but I would appreciate detailed reports and suggestions on this.
Logged In: YES
user_id=13755
In CVS table-level locking is now disabled.
Putting it into transactions (not auto-transactions per
statement) needs to be verified.