On 27.02.2026 23:37, Wietse Venema via Postfix-users wrote:
postfix-3.11.0-RC4 and postfix-3.12-20260227 come with support to ease the migration:
- Of Postfix configurations that use Berkeley DB hash: and btree: databases, - To OS distributions that have deleted Berkeley DB support. The support comes in three levels: - Manual conversion (edit configuration files, replace hash; with lmdb: or cdb:, run 'postmap' commands). This may be OK if you recently configured a Postfix system. Otherwise, consider using: - Automatic redirection (a request to read hash:/path/to/file is implicitly handled as a request to read lmdb:/path/to/file). Postfix will log requests to manually do 'postmap lmdb:/path/to/file' to create the missing indexed files before they can be read. - Automatic redirection and indexing (Postfix redirects a request to read hash:/path/to/file to lmdb:/path/to/file, and tries to 'postmap lmdb:/path/to/file' before it satisfies a read request).
This is excellent really. Simple and efficient. I think I missed one more state: warn. The idea is to have it enabled by default while bdb support is still here, - so that a warning is issued when hash/btree is in use, but it is used still? Actually this can be easily added as a patch for a distribution, so there's no need to carry it upstream, - for a temporary code. I'm not sure yet if the next debian stable release (14, forky) will have bdb support or not, - in my view it is not an easy task to fix before forky release to get rid of berkeley db. But if bdb will be there, a warning is the best we can do. I'll have a closer look at the result in a few days - unfortunately I didn't have a chance to do that earlier. Excellent news! Thanks, /mjt _______________________________________________ Postfix-users mailing list -- [email protected] To unsubscribe send an email to [email protected]
