e76b6a9048
Destroy the AnyDBM-tied hash after untying Google's wisdom seems to indicate that leaving the AnyDBM-tied hash around after untying it was causing data to not flush to the DBM file... or something. At any rate the regression test added here confirms inconsistency when using multiple instances which is fixed by destroying the AnyDBM-tied hash after untying. |
||
---|---|---|
.. | ||
DB | ||
Postfix | ||
SMTP | ||
TcpServer | ||
Address.pm | ||
Auth.pm | ||
Base.pm | ||
Command.pm | ||
Config.pm | ||
ConfigServer.pm | ||
Connection.pm | ||
Constants.pm | ||
DB.pm | ||
DSN.pm | ||
Plugin.pm | ||
Postfix.pm | ||
SMTP.pm | ||
TcpServer.pm | ||
Transaction.pm |