Michael Grimm via Postfix-users:
> Hi,
>
> tl;dr this is not a postfix issue.
>
> I do want to point out: http://www.lmdb.tech/doc/upgrading.html
>
> I got bitten by this on FreeBSD and had had to fall back to lmdb 0.93.5
>
> I have been in the naive assumption that this shouldn't be an issue at all by
> just rebuilding my lmdb databases with 'postmap lmdb:TEST'
>
> But there are other issues with lmdb 1.0:
>
> test> ldd /usr/local/lib/postfix/* | grep lmdb
> /usr/local/lib/postfix/postfix-lmdb.so:
> liblmdb.so.1 => /usr/local/lib/liblmdb.so.1 (0x90234ff3000)
>
> test> la /usr/local/lib/liblmdb*
> -rw-r--r-- 1 root wheel uarch 137992 Jul 5 08:51 /usr/local/lib/liblmdb.a
> lrwxr-xr-x 1 root wheel uarch 14 Jul 5 08:51 /usr/local/lib/liblmdb.so
> -> liblmdb.so.1.0
> lrwxr-xr-x 1 root wheel uarch 14 Jul 5 08:51
> /usr/local/lib/liblmdb.so.1 -> liblmdb.so.1.0
> -rw-r--r-- 1 root wheel uarch 114040 Jul 5 08:51
> /usr/local/lib/liblmdb.so.1.0
>
> test> postmap lmdb:TEST
> postmap: fatal: error updating lmdb:TEST: MDB_BAD_TXN: Transaction must
> abort, has a child, or is invalid
Apparently their API has changed too. If there is no compatibility
option, then that is a breaking change.
> Well, I will stick with lmdb 0.9.35 for the time being or migrate
> to other database formats, instead.
Way to go if you have that option.
Wietse
_______________________________________________
Postfix-users mailing list -- [email protected]
To unsubscribe send an email to [email protected]
