Christian Pfeiffer via Postfix-users:
>
> I had already posted on here a couple of days ago on the matter
> but it got missed or so. Anyway, the problem is a singular change
> to mdb_drop(), commit d0fcfd3d02321d04b56a23e6c86c80309f4ecef5 in
> mdb. It was made to fix bug ITS#8174 in LMDB. The consequence is
> that now you cannot reuse a transaction handle that was used to
> drop MAIN_DBI. Postfix does this in slmdb_prepare(), dropping ALL
> databases, including MAIN_DBI. This handle then causes MXN_BAD_TXN
> on its next usage, breaking newaliases and co. The transaction
> handle would need to be aborted and then the transaction reopened.
> The patch I made for Arch downstream patch that has been in this
> thread already does precisely that. It only changes slmdb_prepare()
I have a question.
When used with the postmap command, the "old" Postfix code tries
to drop AND 'bulk update' a database in one transaction, so that
the drop will not happen when the update cannot be completed.
Do I get that assurance with the new code?
Wietse
_______________________________________________
Postfix-users mailing list -- [email protected]
To unsubscribe send an email to [email protected]
