11.5.30 Update #24 -- remove the skip-bdb option from my.cnf ???

[Linulex]

Parallels Plesk Panel 11.5.30 Update #24

says

1 * Plesk will remove the skip-bdb option from my.cnf if MySQL version is 5.1 or later.

http://dev.mysql.com/doc/refman/5.0/en/bdb-start.html

says

If you use the --skip-bdb option, MySQL does not initialize the Berkeley DB library and this saves a lot of memory.

I have never used it, never allowed it, so my clients have never used any DBD tables. None of my clients ever asked for it so up till now it was some other exotic engine type no one uses and i didn't gave any attention to.

Why does plesk needs it?
what will happen if i re-add skip-bdb to my.cnf?

regards
Jan

 

[Faris Raouf]

I think you may have misunderstood the purpose of this MU.

Plesk does not need it and never has. If I remember correctly, it was simply found in my.cnf either because it was there by default in some MySQL installations, or at some point in the past it was commonly added by sysadmins (for the reason given in the MySQL docs).

The real problem is that more recent versions of MySQL (5.1 onwards?) will not start if you have the skip-bdb option in my.cnf. That's why the MU checks for an removes it, as it will solve a lot of update/upgrade problems.