[pfx] Re: expected behavior of 3.11 *with* bdb and hash/btree support?
Wietse Venema via Postfix-users <[email protected]>
| Newsgroups | gmane.mail.postfix.user |
|---|---|
| Message-ID | <[email protected]> |
Greg Klanderman via Postfix-users: > > > >>>>> On April 1, 2026 Greg Klanderman via Postfix-users <[email protected]> wrote: > > >>>>> On April 1, 2026 Wietse Venema <[email protected]> wrote: > >> Greg Klanderman via Postfix-users: > >>> Further, it seems there is not even the option to use hash/btree > >>> when postfix is compiled with bdb in this release. > > >> That is not true. I run postfix with real Berkeley DB. Just don't > >> build with -DNO_DB on Fedora and FreeBSD. > > > OK, so it's just a Debian packaging issue then? > > > But postfix has been built with BDB support, as postfix -m does > > include hash and btree. I assume if it had been built with -DNO_DB > > that would not be the case, right? > > Hmm, I see my log messages are only warnings: > > | warning: /etc/postfix/discard_ehlo_keywords: hash/btree support is deprecated. Please switch to cdb or lmdb. That's added by the Debian maintainer, in an attempt to encourage people to convert before Berkeley DB support becomes unavailable. > and not the error message shown in NON_BERKELEYDB_README: > > | Berkeley DB support for 'hash:/etc/postfix/virtual' is not available That's when Postfix 3.11 is compiled with -DNO_DB, in an attempt to get people started with a 'late' conversion when Berkeley DB support is already no longer available. Wietse _______________________________________________ Postfix-users mailing list -- [email protected] To unsubscribe send an email to [email protected]