Yahoo Groups archive

Milter-greylist

Index last updated: 2026-04-28 23:32 UTC

Message

Re: [milter-greylist] milter-greylist 3.1.x branch and OpenBSD performance loading greylist.db

2007-01-07 by Fabien Tassin

According to Emmanuel Dreyfus:
> On Sun, Jan 07, 2007 at 06:53:30PM +0100, Fabien Tassin wrote:
> > > I droped it because we had no garantee of not loosing data when the
> > > milter would be killed. How are you going to address that problem? 
> > 
> > What about SQLite ? I'd love to have that. No need to maintain a local DNSRBL
> > then. Any tool could update a table very easily from the outside.
> 
> How does it resist to a kill -9?

theory:

Transactions are atomic, consistent, isolated, and durable (ACID) even after
system crashes and power failures.

(...)

If a process is writing to the database file but exits abruptly without
finishing its write (perhaps because of a power failure or an OS crash) it
leaves behind a "hot journal". Subsequent processes which try to read the
database will see this hot journal and use it to restore the database to a
consistent state.

read this for more on database corruption past issues:
http://www.sqlite.org/cvstrac/wiki?p=DatabaseCorruption

/Fabien

Attachments

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.