[bind10-dev] MySQL vs PosgreSQL data source flamewar - FIGHT!

[Adam Tkac]

On Thu, Jan 10, 2013 at 04:52:51PM +0100, Jelte Jansen wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> On 01/10/2013 02:24 PM, Shane Kerr wrote:
> > 
> > Arguments for MySQL:
> > 
> > * We use it for the first DHCP lease database store. * Developers
> > tend to like it.
> > 
> > Arguments against MySQL:
> > 
> > * GPL license
> > 
> > Arguments for PostgreSQL:
> > 
> > * DBA tend to like it. * BSD license.
> > 
> 
> the license will not be an issue for us unless we want to bundle it;
> but it could be for people making a 'full solution' kind of thing; but
> if we are planning on supporting both this isn't a big deal.
> 
> I personally would have a slight preference for postgres because I
> find it easier to setup and maintain as an admin. But that, too, is
> not too relevant.
> 
> So I really don't have a strong opinion :) If dhcp is already using it
> I guess it'd make sense to go for mysql first.
> 
> Jelte

Just my two cents against MySQL. It's upstream (Oracle) tends to be quite
closed and Oracle is usually slow with releasing critical fixes for MySQL.
As you probably know this lead to MySQL fork (MariaDB). There are many articles
and blogposts about this on the Internet.

On the other hand PostgreSQL community is more opened and there are no such
problems.

However if MySQL data source will be carefully designed, it shouldn't be too
hard to port it to PostgreSQL and vice versa.

Regards, Adam

-- 
Adam Tkac, Red Hat, Inc.