Wietse Venema:
> Stefan:
> > Hi list,
> >
> > I'm in the process of adding write support to postfix's mysql client (you
> > will
> > find a patch against postfix-2.7.1 in the appendix). But I have two
> > problems:
> > 1) the dict_cache_clean_event writes _LAST_CACHE_CLEANUP_COMPLETED_ to the
> > database. Is this the intended behaviour?
>
> This record is needed by the cache cleanup pseudo-thread. This code
> assumes that the verify(8) daemon is responsible for cleaning up
> the verify(8) cache.
>
> > 2) If I'm guessing right then the dict_cache_clean_event will iterate with
> > help of dict->sequence through the database and will look for keys to
> > expire.
> > But I don't know how to implement this iteration/traverse process with
> > mysql.
> > My first thought was to use "SELECT * FROM verify" and mysql_use_result()
> > but
> > I'm wondering if there is a better solution.
> > Has anyone an idea of how to do this?
>
> Does the database support a first/next operation?
>
Another desirable option may be to disable cache cleanup by the
verify(8) daemon. Supposedly, the cache is meant to be shared,
otherwise why incur the overhead?
Wietse
> > Thanks for your help and best regards
> > Stefan
> >
> > > > by Stefan Jakobs on 2010-06-13T19:43:00+00:00
> > > > Hello list,
> > > > I refer to my question of august 2008
> > > > (http://archives.neohapsis.com/archives/postfix/2008-08/0747.html, and
> > > > see
> > > > below).
> > > > What are the necessary steps to add update support to the mysql client
> > > > (Postfix 2.5.6 or newer)?
> > > > Has someone already done this and is willing to share the code?
> > > > Thanks for your help and kind regards
> > > > Stefan
> > > Wietse wrote on August 22nd 2008:
> > > Stefan Jakobs:
> > > I think this involves writing, testing, and documenting code. The
> > > design stage can pretty much be skipped for this fill-in-the-blanks
> > > exercise.
> > > Wietse
>
> [ Attachment, skipping... ]
>
>
>
