Making MySQL Better at GitHub

Re:Making MySQL Better at GitHub by erkkie on Wednesday September 03, 2014 @03:05AM (#8261821)

After Postgres got replication out of the box I'm pretty sure it's just inertia and the fact that it's installed everywhere keeping mysql usage up. Postgres is so much nicer when dealing with day-to-day things.

Eg disabling connections per database using sql and having built-in query stats (http://www.postgresql.org/docs/9.4/static/pgstatstatements.h...) just made me smile.

[ Parent | on HN ]

Re:Making MySQL Better at GitHub by morgo on Wednesday September 03, 2014 @08:38AM (#8262652)

The built in query stats is similar to Performance Schema in MySQL. The statistics are quite fine grained, and with a set of views on top (https://github.com/MarkLeith/mysql-sys) are very useful for observability.

[ Parent | on HN ]

Re:Making MySQL Better at GitHub by erkkie on Wednesday September 03, 2014 @04:05PM (#8265136)

Thanks, wasn't aware of that, quit mysql habits pre 5.6 :)

[ Parent | on HN ]

Re:Making MySQL Better at GitHub by morgo on Wednesday September 03, 2014 @11:17PM (#8266602)

Technically, it was introduced in 5.5, but off by default :)

5.7 is going to be amazing for observability. Memory, transactions, stored procedures, replication, meta data locking and prepared statements are all instrumented in P_S.

[ Parent | on HN ]