[pfx] Re: expected behavior of 3.11 *with* bdb and hash/btree support?

Hi Wietse,

Sorry for the delay following up..

>>>>> On April 2, 2026 Wietse Venema via Postfix-users <[email protected]> wrote:

> 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.

I think my confusion here was that the warning messages in the logs,
added by the Debian maintainer as you point out below, refer one to
NON_BERKELEYDB_README, but that README is written from the perspective
of Berkeley DB support having been removed.

As I was having db lookup failures, I glossed over the fact that these
were merely warnings, and pulled up the README and also
'non_bdb_migration_level' in postconf(5), and saw that all three
options describe *not* using hash/btree, and with the default being
'disable', incorrectly concluded that you could no longer use
hash/btree.

I now see that the 'Introduction' section does state:

| ... there is a rude awakening when you update the OS to a newer
| version that has deleted its support for Berkeley DB ...

But I think especially given that the Debian-added warning also
directs to that README, that it would be good to make more clear both
in the README and under 'non_bdb_migration_level' of the man page,
that all this only applies when BDB support is not included.

>> | 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.

OK, thank you for clarifying that.

>> 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.

Thank you, I understand now..

So, would this bug, fixed in 3.11.1:

|   * Bugfix (defect introduced: 20260219): alias_maps errors when
|     default_database_type was not set in main.cf. Fix by Michael
|     Tokarev.

have only impacted use of hash: tables?

Because after switching to cdb: my db lookup problems are fixed, still
using 3.11.0.  I had not dug deeply into those db lookup problems, but
I know that at least /etc/aliases expansions were broken with hash:.

thank you,
Greg
_______________________________________________
Postfix-users mailing list -- [email protected]
To unsubscribe send an email to [email protected]