* Wietse Venema :
> Systems that run close to the capacity limit probably should not
> expire caches but simply rotate them. I already have a version of
> Postfix that allows you to turn off cache cleanup.
I deployed 20091230-nonprod before I went to town this evening and
until now, there is not
As a side note:
* Stefan F??rster :
I took care of that problem - permanently. I understand that an UTF-8
encoded realname might pose serious problems to some MUAs and I don't
want to cause any, erm, "inconveniences".
Stefan
* Victor Duchovni :
> On Wed, Dec 30, 2009 at 05:08:23PM +0100, Stefan F??rster wrote:
>
> > > What database type are you using?
> >
> > Berkeley DB 4.6.21-11 from libdb4.6_4.6.21-11_amd64.deb.
>
> That's software package not database type. Is it "hash" or "btree"?
$ postconf postscreen_cache_m
On Wed, Dec 30, 2009 at 05:08:23PM +0100, Stefan F??rster wrote:
> > What database type are you using?
>
> Berkeley DB 4.6.21-11 from libdb4.6_4.6.21-11_amd64.deb.
That's software package not database type. Is it "hash" or "btree"?
--
Viktor.
Disclaimer: off-list followups get on-list
* Victor Duchovni :
> On Wed, Dec 30, 2009 at 08:26:45AM +0100, Stefan F??rster wrote:
> > I've noticed a vast deterioration of the databases's performance,
> > though. 20091209 only emitted some timing warnings for updates from
> > time to time (database rotated every Saturday as per your
> > reco
Stefan F?rster:
> * Ralf Hildebrandt :
> > * Wietse Venema :
> > > Dec 29 04:20:17 spike postfix/postscreen[44900]: cache
> > > /var/lib/postfix/ps_cache.db full cleanup: retained=134 dropped=19 entries
> > > Dec 29 06:19:33 spike postfix/verify[46072]: cache
> > > /var/lib/postfix/verify.db full
On Wed, Dec 30, 2009 at 08:26:45AM +0100, Stefan F??rster wrote:
> I've noticed a vast deterioration of the databases's performance,
> though. 20091209 only emitted some timing warnings for updates from
> time to time (database rotated every Saturday as per your
> recommendation). With the new cod
* Ralf Hildebrandt :
> * Wietse Venema :
> > Dec 29 04:20:17 spike postfix/postscreen[44900]: cache
> > /var/lib/postfix/ps_cache.db full cleanup: retained=134 dropped=19 entries
> > Dec 29 06:19:33 spike postfix/verify[46072]: cache
> > /var/lib/postfix/verify.db full cleanup: retained=1726 drop
Ralf Hildebrandt:
> * Wietse Venema :
>
> > You may want to give a heads-up to the maintainer as I am just
> > about to release this code as a regular experimental release.
> > Cache cleanup will definitely be part of the Postfix 2.7 stable
> > release, so they will have to deal with it in a month
* Wietse Venema :
> You may want to give a heads-up to the maintainer as I am just
> about to release this code as a regular experimental release.
> Cache cleanup will definitely be part of the Postfix 2.7 stable
> release, so they will have to deal with it in a month or so anyway.
I'm running th
Stefan F?rster:
> * Wietse Venema :
> > I'm burning in some new code that I wrote over the past week to
> > periodically remove old entries from postscreen(8) and verify(8)
> > caches. This is not a sexy topic, but it helps to keep database
> > sizes in check, it speeds up database access, and it w
* Wietse Venema :
> I'm burning in some new code that I wrote over the past week to
> periodically remove old entries from postscreen(8) and verify(8)
> caches. This is not a sexy topic, but it helps to keep database
> sizes in check, it speeds up database access, and it was time.
>
> If you're co
I'm burning in some new code that I wrote over the past week to
periodically remove old entries from postscreen(8) and verify(8)
caches. This is not a sexy topic, but it helps to keep database
sizes in check, it speeds up database access, and it was time.
If you're courageous you can try postfix-2
13 matches
Mail list logo
