|
SA Bugzilla – Full Text Bug Listing |
Summary: | concurrency problem in the PostgreSQL specific Bayes-module | ||
---|---|---|---|
Product: | Spamassassin | Reporter: | Stefan Kaltenbrunner <stefan> |
Component: | Learner | Assignee: | SpamAssassin Developer Mailing List <dev> |
Status: | NEW --- | ||
Severity: | normal | CC: | dluke, parkerm |
Priority: | P5 | ||
Version: | 3.1.0 | ||
Target Milestone: | Undefined | ||
Hardware: | Other | ||
OS: | other | ||
Whiteboard: |
Description
Stefan Kaltenbrunner
2005-10-20 19:42:55 UTC
> However the approach used is subject to a racecondition in the case of multiple
> clients learning mails with similiar tokens (multiple spamds or sa-learns),
> because it might happen that a new token gets inserted(and commited) after the
> function got called but before it tries the insert resulting in the following
> error message in the postgresql log:
Btw, the same problem occurs in SQL-based AWL backend: process A does a SELECT
and does not find any entries, meanwhile process B does the same and INSERTs
its record, and when later process A tries to do its own INSERT (instead of
UPDATE), the SQL operation fails due to a key constraint.
|