On 8/7/21 12:02 AM, Quanah Gibson-Mount wrote: > --On Friday, August 6, 2021 11:49 PM +0100 Howard Chu <[email protected]> > wrote: >> Just to be clear, the current upgrade doc is a bit paranoid. A 2.4 DB is >> forward compatible with 2.5. But 2.5 allows you to configure new DB >> parameters >> that would make it incompatible with 2.4. > > Or another way to put it: > > Unless sortvals, multival, or idlexp is being newly configured as a > configuration change during the upgrade process, there is no requirement > to reload a back-mdb database on reload with OpenLDAP 2.5.6 and prior.
Ah, this is good to know. Thank you both for clarification. > However it will not be possible to export this database via slapcat > until after an OpenLDAP 2.5 slapd has been executed with the database in > place. Ok, noted. Easy with Æ-DIR because slapd will be restarted after upgrade during ansible play. > With OpenLDAP 2.5.7 and later it is possible to export a 2.4 > database with slapcat in all circumstances. This will be very helpful because downstream packagers won't have to provide two different versions of slapcat (as currently discussed on opensuse-factory list). Ciao, Michael.
