The following issue has been RESOLVED. 
====================================================================== 
http://www.dbmail.org/mantis/view.php?id=384 
====================================================================== 
Reported By:                mavetju
Assigned To:                aaron
====================================================================== 
Project:                    DBMail
Issue ID:                   384
Category:                   general delivery
Reproducibility:            random
Severity:                   major
Priority:                   normal
Status:                     resolved
target:                      
Resolution:                 won't fix
Fixed in Version:           
====================================================================== 
Date Submitted:             26-Jul-06 03:52 CEST
Last Modified:              30-Jul-06 13:22 CEST
====================================================================== 
Summary:                    database failure leads to message rejection
Description: 
Sometimes, four, five times per day, we get a deadlock in postgresql:

Error executing query [UPDATE dbmail_users SET curmail_size = curmail_size
+ '2930503' WHERE user_idnr = '39361'] : [ERROR:  deadlock detected DETAIL:
 Process 53401 waits for RowExclusiveLock on relation 19270441 of database
8435668; blocked by process 53654. Process 53654 waits for ExclusiveLock
on relation 19588978 of database 8435668; blocked by process 53401. 

As a result, a lot of other things fail behind it (See additional
information). But the worst is... dbmail-smtp returns EX_NOUSER, and the
email is bounced. In my belief, this should be a temporary failure and be
retried later.
====================================================================== 

---------------------------------------------------------------------- 
 aaron - 30-Jul-06 13:22  
---------------------------------------------------------------------- 
I know it would be good to fix this in the 2.0 series, but you're better
off upgrading to the 2.1 series at this point. The work required to fix
this is potentially invasive; not something we're looking to do along the
2.0's now. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
26-Jul-06 03:52 mavetju        New Issue                                    
30-Jul-06 13:22 aaron          Status                   new => resolved     
30-Jul-06 13:22 aaron          Resolution               open => won't fix   
30-Jul-06 13:22 aaron          Assigned To               => aaron           
30-Jul-06 13:22 aaron          Note Added: 0001324                          
======================================================================

Reply via email to