On Mittwoch, 25. Juli 2007 Anne wrote:
> SELECT count(id) FROM dbmail_physmessage WHERE id NOT IN (SELECT
> physmessage_id FROM dbmail_messages);
> result: 233753 records

In dbmail-2.2.6 or so, dbmail-util was extended, so a call to
dbmail-util -uy
should drop these, as I understood.

However, I tried it now:
# dbmail-util -u
Choosing dry-run mode. No changes will be made at this time.

Checking DBMAIL for NULL messages...
Ok. Found [0] NULL messages.

Checking DBMAIL for NULL physmessages...
Ok. Found [0] physmessages without messageblocks.

but there are some messages:
select count(*) from dbmail_physmessage WHERE id NOT IN (SELECT 
physmessage_id FROM dbmail_messages);
 count
-------
 31349
(1 Zeile)

And very strange is, that I created a rule which should prevent this:

CREATE RULE drop_messages_with_mailbox AS ON DELETE TO dbmail_messages 
DO DELETE FROM dbmail_physmessage WHERE id = OLD.physmessage_id AND id 
NOT IN (SELECT physmessage_id from dbmail_messages);

The rule is active, still I see again 31.349 physmessages hanging 
around. What could be the problem?

mfg zmi
-- 
// Michael Monnerie, Ing.BSc    -----      http://it-management.at
// Tel: 0676/846 914 666                      .network.your.ideas.
// PGP Key:         "curl -s http://zmi.at/zmi.asc | gpg --import"
// Fingerprint: EA39 8918 EDFF 0A68 ACFB  11B7 BA2D 060F 1C6F E6B0
// Keyserver: www.keyserver.net                   Key-ID: 1C6FE6B0

Attachment: signature.asc
Description: This is a digitally signed message part.

_______________________________________________
DBmail mailing list
[email protected]
https://mailman.fastxs.nl/mailman/listinfo/dbmail

Reply via email to