maria-discuss team mailing list archive

[Sergei Golubchik <serg@xxxxxxxxxxx>]

Hi, Reindl!

On May 07, Reindl Harald wrote:
> Am 07.05.2015 um 22:29 schrieb Sergei Golubchik:
> > On May 07, Reindl Harald wrote:
> >>
> >> Am 07.05.2015 um 21:02 schrieb Reindl Harald:
> >>> Don't build on Fedora 21 / gcc-4.9.2-6.fc21.x86_64 but on Fedora 20 /
> >>> gcc-4.8.3-7.fc20.x86_64 which is not a good sign since 10.0.17 with
> >>> identical environment builds on both
> >>
> >> and the Fedora 20 build is completly broken and crashs due "mysql_upgrade"
> >
> > Yes, I've just fixed it. But too late for 10.0.18 :(
> >
> > Your most simple workaround would be not to run mysql_upgrade. It
> > wouldn't do anything noticeable when upgrading from 10.0.17 to 10.0.18
> > anyway
> 
> does that *really* only affect mysql_upgrade since a crash of mysqld 
> itself and not mysql_upgrade is bad and i am not sure if some other 
> query in production would not trigger the same problem?

No, it affects the server, not mysql_upgrade. But it's a new statement,
that mysql_upgrade is using,  no existing query can possibly trigger
that bug.

Regards,
Sergei