On Fri, Nov 26, 2004, Martin Schneider wrote: > I wonder which combo (OpenPKG 2.2 + MySQL 4.1.5 or Current + MySQL > 4.1.7) is better suited for production use. > > I need to test the MySQL Cluster features. The servers are running SUSE > Linux 9.0 and 9.1 and maybe in the future 9.2. These come with MySQL > 4.0.x. So my options are OpenPKG or the binaries of MySQL AB. (The > clients are running SUSE and Debian and use the cli-mysql-client and our > own C-programs with client functionality.) > > MySQL 4.1.7 should have fewer bugs. But is it safe to use OpenPKG > Current? > > I'd like to hear your suggestions. > I think you have two questions which are 'should I use MySQL 4.1.5 or MySQL 4.1.7' and 'should I use OpenPKG release or current packages on production machines'.
Unfortunately, the first question can best be answered on the mysql mailing list and not here. With limited experience of MySQL database replication (what I believe you mean by 'cluster features') I can say that the biggest difference is between MySQL 3.* and MySQL 4.* versions. Try reading the release notes of 4.1.7 to see if those features have changed since 4.1.5. The second question is somewhat easier to answer. Although subjective, OpenPKG targets the most stable versions for release packages. Because most admins prefer better stability over more features, they stick to release packages. If you know you need a feature not present in 4.1.5 and if you are brave, then try out the current version 4.1.7 package. Regards, Michael -- Michael Schloh von Bennewitz <[EMAIL PROTECTED]> Development Team, Operations Northern Europe Cable & Wireless Telecommunications Services Tel +49-89-92699-227, Fax +49-89-92699-808
pgpcBorrkteCp.pgp
Description: PGP signature
