On 07/30/17 05:31, Kern Sibbald wrote: > Phil, > > By the way, if you can definitively tell me how to distinguish Solaris > 10 from any newer Solaris I will attempt to fix the conio.c problem. > This is an old "bug" of Solaris 10 where I have never had the > information I needed to fix it. In fact, if I am not mistaken, the move > the line up one fix is documented in the source code.
Indeed it is, and anyone installing on Solaris is almost certainly building from source anyway. Which is why I didn't make a big deal of it, just mentioned applying the usual fix. I'm not sure how to best autodetect Solaris 11 vs. 10 at the code level either. One does presume that there must be a way, though. It ought to be possible to set a flag based upon the output of 'uname -r', which will return either 5.10 or 5.11. > PS: I am seriously considering deprecating MySQL and MariaDB, because > both are constantly changing their code and cause Bacula to break. In > other words, they and the C++ programmers don't seem to mind introducing > serious incompatibilities with previous version. This is still an open > subject. Oracle has been doing a lot of work to clean up MySQL, fix old legacy cruft, improve performance, and make it comply better with the formal SQL spec. The other major fork of community MySQL, Percona Server, tracks 100% interchangeably with MySQL to the extent that I have run MySQL and Percona Server interchangeably as members of the same cluster with no issues, and Percona Software has actually contributed a lot of their own bug fixes and enhancements back to the MySQL community (and Oracle has happily adopted them). MariaDB, particularly 10.1 and later, not so much. MariaDB is *INTENTIONALLY* diverging from community MySQL. MariaDB 10.2 and MySQL 5.7 are not really fully interoperable any more. I actually recommend against MariaDB to clients at my day job for this reason, and in particular I have established a policy that we *will not* support MariaDB Galera clustering in customer environments because it is just not sufficiently well integrated to be considered production-stable for mission-critical applications. In fact, when I first evaluated it at work we couldn't even get it to successfully form a cluster. The only reason I'm currently running MariaDB instead of Percona XtraDB Cluster (which is Percona Server plus Galera) is that there is no Gentoo ebuild for XtraDB Cluster, and my efforts to create my own have so far been unsuccessful. If a Gentoo ebuild for XtraDB Cluster were released today, I would convert to XtraDB Cluster today. > With PostgreSQL, we not only get 30% better performance (in my tests), > but the incompatibilities that have been regularly hitting Bacula in > MySQL/MariaDB just don't exist. Honestly, I think a lot of the performance issues reported with MySQL is that most people who are not professional MySQL DBAs don't understand how to properly tune MySQL. It can be a lot of work. The typical Linux distribution's default MySQL configuration files are generally not helpful in this regard. Until a couple of years ago, Red Hat Enterprise Linux not only shipped an old end-of-life MySQL release, but shipped it with a default configuration file in which only one directive actually *did* anything - and that one directive was *actively harmful*. The usual response to tuning discussions from PostgreSQL advocates is that PostgreSQL is "self-tuning" and very little tuning is required. I tend to think what that really translates to is that very little tuning is *possible*. There are technical choices made in some of PostgreSQL's low-level implementation that frankly make me shudder. > Of course, if we suddenly find that no > one uses MySQL and we only have MariaDB that would be a different > consideration. To be clear about what I mean by deprecation is I will > no longer maintain the code, but will not remove it. If it breaks then > I will wait for a patch from the community. This is essentially the > current case with bat. -- Phil Stracchino Babylon Communications ph...@caerllewys.net p...@co.ordinate.org Landline: +1.603.293.8485 Mobile: +1.603.998.6958 ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Bacula-devel mailing list Bacula-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-devel
