Scott Kitterman:
> Some Debian users aren't thrilled about a behavior change associated with the
> 20170611 Berkeley DB 2 DB_CONFIG fix. Apparently [1] something like:
>
> | root@playbox01:~# postmap test/in
>
> used to work, but now there is an error:
>
> | postmap: fatal: open database test/in.db: No such file or directory
>
> [1] in the bug report, I suggested this was a reasonable side effect of the
> change, but not everyone agreed, so I said I'd ask if that could be made to
> work again.
>
> Any feedback on this?
First test result:
dbenv->open(dbenv, db_home, path_to_db_file)
where db_home is set to the parent directory of path_to_db_file.
Surprisingly, dbenv->open() will APPEND path_to_db_file to db_home,
when path_to_db_file specifies a relative pathname.
I am not apologizing for this bug. The brain-damaged db_home feature
is under-documented, which is why there was this burst of db_home
workarounds a while ago.
Wietse
