On Wed, Jul 02, 2014 at 10:00:52AM +0200, Marco wrote:
> Hello,
> I have a slow performance on my dspam-mysql conf. The purge nightly
> script take 7-12 hours to complete. During this time I see a lot of
> locks
>
> [07/02/2014 09:28:35] 32082: Lock wait timeout exceeded; try
> restarting
> First and most obvious question: Are your tables InnoDB or MyISAM?
> MyISAM should not be used in any production DB unless you absolutely
> require MyISAM features not supported by InnoDB.
Ops, yes: all tables are InnoDB.
Thanks
Marco
---
On 07/02/14 04:00, Marco wrote:
> Hello,
> I have a slow performance on my dspam-mysql conf. The purge nightly
> script take 7-12 hours to complete. During this time I see a lot of
> locks
First and most obvious question: Are your tables InnoDB or MyISAM?
MyISAM should not be used in any pr
> Hello,
>
> I need to install an antispam on a multiple mx mail system.
We use a single mysql db, and a nfs for /var/lib/dspam (dspam Home).
No problem.
But we don't use quarantine or web interface for end users, only IMAP
spam folders.
Regards
Marco
-
Am 02.07.2014 10:00, schrieb Marco:
> I have a slow performance on my dspam-mysql conf. The purge nightly
> script take 7-12 hours to complete. During this time I see a lot of
> locks
>
> [07/02/2014 09:28:35] 32082: Lock wait timeout exceeded; try
> restarting transaction: UPDATE dspam_to
Hello,
I have a slow performance on my dspam-mysql conf. The purge nightly
script take 7-12 hours to complete. During this time I see a lot of
locks
[07/02/2014 09:28:35] 32082: Lock wait timeout exceeded; try
restarting transaction: UPDATE dspam_token_data SET
last_hit=CURRENT_DATE(),in