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).
More information may be found at
https://www.postfix.org/NON_BERKELEYDB_README.html
What does this mean for the rest of Postfix? Small changes to the
build instructions. Some LINUX maintainers will have to explicitly
specify default_database_type and default_cache_type, as covered in
https://www.postfix.org/NON_BERKELEYDB_README.html#build-conf
Otherwise, no change in Postfix behavior. Berkeley DB migration
support is disabled by default, and that code will likely be deleted
in 4-5 years.
The plan is to let the code bake for a few days and then release
postfix-3.11.0 after no show-stopper problems are found.
Wietse
_______________________________________________
Postfix-users mailing list -- [email protected]
To unsubscribe send an email to [email protected]
