On Jan 18, 2018, at 14:56, Rob Landry <41001...@interpring.com> wrote:
> When you run rdadmin after an upgrade, it compares the database version with
> the desired one and then upgrades if necessary. Why not have it check the
> database engine and modify rd.conf accordingly?
So what would be co
On Wed, 17 Jan 2018, Fred Gleason wrote:
That was indeed the default when the feature was first implemented. It was
changed in the course of pre-release testing because of a similar
interaction that broke compatibility with the Aman Rivendell server manager,
which requires MyISAM tables. The rea
On Wednesday 17 January 2018 06:14:53 pm Fred Gleason wrote:
> So, unfortunately, whatever we do it appears that *someone* is going to be
> ‘astonished’ after an upgrade to 2.18.x. Not ideal, but I don’t see any way
> around it.
Re-invent the Slackware practice of moving the old file to
filena
> On Jan 17, 2018, at 17:31, Thomas Golding wrote:
>
> OVERRIDES the my.cnf default-storage-engine setting, even if it's not present
> in your rd.conf file. Because all tables must be InnoDB for Galera to work,
> if you don't add Engine=InnoDB to your rd.conf, Rivendell will start creating
>
A word of CAUTION for anyone using Galera database cluster:
The new feature in the MYSQL section of rd.conf
Engine=[DEFAULT: MyISAM]
OVERRIDES the my.cnf default-storage-engine setting, even if it's not
present in your rd.conf file. Because all tables must be InnoDB for
Galera to work, if
