>> The thing is policyd's behaviour when the database is unavailable is more >> configurable (either tempfail or bypass) than Postfix' behaviour when >> policyd is unavailable (always tempfail). That's why we run policyd >> locally on each Postfix server, with a central SQL database server. >> >> > > Tha's a very good point. It's always a tradeoff. OTOH when we had > multiple policyd instances talking to mysql, we were seeing frequent > corruption of the policyd myisam tables whenever there was a network > glitch. Since moving to a single policyd on the same host as the mysql > database, we haven't had any table corruption. > There should be no corruption in v2, please, if you're having problems like this either log a bug report or drop an email here for us to investigate.
v2 also by default uses InnoDB to ensure entire transactions are carried out properly to prevent incomplete data. Regards Nigel _______________________________________________ Users mailing list [email protected] http://lists.policyd.org/mailman/listinfo/users
