Thomas, I can prepare a small change to amavisd which would use (partition_tag,mail_id) as a unique key instead of just the (mail_id).
That would make mail_id not necessarily unique (causing touble to releasing from a quarantine, needing to provide partition_tag in addition to mail_id in order to uniquely identify a message to be released), but would satisfy the constraint you quoted: "...every unique key on the table must use every column in the table's partitioning expression." (this also includes the table's primary key, since it is by definition a unique key...) Do you think it would help? > Is there someone doing the same job with PostgreSQL? If so: Can > you provide me some farther details? Good and bad experiences, > replication etc? PostgreSQL is 'half-way' to supporting partitions - it bends its optimizer to make it behave like you have partitions. Because of this and because PostgreSQL is an order of magnitude faster in purging amavisd database, I doubt anybody has ventured into that territory yet. Mark ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ AMaViS-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/amavis-user AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3 AMaViS-HowTos:http://www.amavis.org/howto/
