My guess is at the time, mysql offered replication and postgresql did not. This is no longer the case, replication is now part of postgresql and as typical for postgresql vs mysql it is much more advanced than what mysql offers.
http://wiki.postgresql.org/wiki/Replication,_Clustering,_and_Connection_Pooling On Wed, Apr 4, 2012 at 8:37 AM, Apexi 200sx <[email protected]> wrote: > YouTube do apparently... :) > > > On Wed, Apr 4, 2012 at 1:36 PM, Lex Berezhny <[email protected]> wrote: >> >> On Wed, Apr 4, 2012 at 8:19 AM, Jeffrey Van Voorst >> <[email protected]> wrote: >> > Sad part is mysql doesn't have an async C API. Probably a good reason >> > to >> > use postgres. Although one could fake it using pthreads like libeio >> > does >> > for files. >> > >> > If you run python instead on your server, it will be slower, but you can >> > use >> > twisted, gevent, stackless, etc., and don't need to care that mysql >> > blocks. >> > However, that doesn't solve your clientside issues. >> >> I think you have to be masochistic to use MySQL in this day and age :-) >> >> Does anyone even voluntarily decide to use it anymore? > >
