Re: spamassassin deadlocks

2007-03-19 Thread SM 

Hi Sandeep,
At 05:28 19-03-2007, Sandeep Agarwal wrote:

i am using 3.1.7 with SQL based setup using Postgres 8.1.4 as the
RDBMS. postgresql server log is full of deadlock detected message

ERROR:  deadlock detected
DETAIL:  Process 18045 waits for ShareLock on transaction 2438579;
blocked by process 18049.


[snip]


CONTEXT:  SQL statement UPDATE bayes_token SET spam_count =
greatest_int(spam_count +  $1 , 0), ham_count = greatest_int(ham_count
+  $2 , 0), atime = greatest_int(atime,  $3 ) WHERE id =  $4  AND
token =  $5 
   PL/pgSQL function put_tokens line 9 at SQL statement


Another transaction may have updated the row.  The current UPDATE 
cannot get a ShareLock.


I suggest fine-tuning your Postgresql installation.

Regards,
-sm

Re: spamassassin deadlocks

2007-03-19 Thread Graham Murray 
Sandeep Agarwal [EMAIL PROTECTED] writes:

 above errors are just samples, the log is full of these messages. is
 there some bug is PGSQL implementaion

I am running SA with psql and the only log messages are autovacuum
ones, so it is not a general problem.