QA: It may not break for you. PostConfigure uses a system call to 'pidof' to determine if mysqld is running. It streams the result of the call into a buffer as a string, then converts that string to a number. If > 0, then mysqld is already running. The problem is, the buffer was not zeroed out, so if mysqld is not running, what ever happens to be in that buffer is used for the pid. In many cases, that will be 0 and nothing breaks. But, sometimes it's other than zero and it falsely assumes mysqld is running and thus exits.

Build verified: 1.5.0-1 BB

engine commit:
f01185f

1.4.4 is not yet available in buildbot.

In release 1.4.3, when installing RPM packages, server mysqld actually starts automatically and postConfigure would not run. For testing this ticket, I need to stop mysqld first, then test.

I ran regression test only, by installing ColumnStore few time and make sure postConfigure does not report false positive.

Build verified: 1.4.4.-1 source

/root/ColumnStore/buildColumnstoreFromGithubSource/server
commit 86a634a0feaf7788c9bcf7cc763e500d2be97d75
Author: Sergei Golubchik <serg@mariadb.org>
Date: Fri Feb 28 21:55:32 2020 +0100

Revert "make columnstore maturity gamma"

This reverts commit e4a0372cd08a53f97a62d6b6ef32114b553cacb7.

/root/ColumnStore/buildColumnstoreFromGithubSource/server/engine
commit ca3e2d78d6e1d06fb6711befe7bb2d618e801929
Merge: ec3630d f437152
Author: Patrick LeBlanc <43503225+pleblanc1976@users.noreply.github.com>
Date: Thu Mar 19 11:43:55 2020 -0500

Merge pull request #1113 from pleblanc1976/develop-1.4

Bumped version num to 1.4.4-1