[debian-mysql] my.cnf problems

[Norvald H. Ryeng]

On Sat, 07 Dec 2013 00:58:43 +0100, Stewart Smith  
<stewart.smith at percona.com> wrote:

> Bjoern Boschman <bjoern at boschman.de> writes:
>> I've seen some blockers due to the fact that everybody (mysql, maria,
>> percona) includes my.cnf from mysql-common.
>>
>> my 2 cent:
>>
>> maria: /etc/mariadb/my.cnf
>> mysql: /etc/mysql/my.cnf
>> percona: /etc/percona/my.cnf
>>
>> From my point of view it's a dream that cannot be fullfilled that all
>> forks can share the same configuration file.

I agree. They are mostly similar, but some day someone will add an option  
that we want to use, but the other flavors don't support it.

>>
>> your comments?
>
> The idea of Percona Server is to be a complete drop-in replacement with
> zero or near-zero effort going to/from MySQL... so having a different
> configuration file would mean that switching to Percona Server would
> suddenly use a different configuration, potentially even preventing the
> server from starting (as the datadir is the same).
>
> I'm not sure what the best idea is here....

I see your point. The main problem with a common my.cnf is that it's  
impossible to separate between the servers. MySQL and Percona is probably  
similar enough that this won't be much of a problem in practice, but  
MariaDB doesn't follow MySQL that closely. With separate my.cnfs, we can  
add flavor specific options to those and add common options in a common  
file/directory (e.g., /etc/my.cnf.d/) that is included by all. Wouldn't  
that work?

Regards,

Norvald