> "Kevin Baker" <[EMAIL PROTECTED]> writes: <snip>
> has to do. However, about two years ago, experiments > conducted by the > people at Slashdot showed that the two systems were > comparable even > for simple tasks, while PostgreSQL totally whipped MySQL > once the > going got tough -- it's built to handle complex queries, > and it's also > built to withstand the pressure of many simultaneous > users. MySQL is > not, and takes a really bad performance hit when loaded > down. The > main reason for this is very primitive locking algorithms > in MySQL. > Do you have a reference for this slashdot article? I'd be interested to read it. As you say mysql has made many improvements recently, but I am still intersted in reviewing PgSQL in a production env, especially for DBMail. <snip: oracle comparison> > However, this data is not very new, and from what I've > been told, the > people at MySQL have been reimplementing their locking to > work the way > PostgreSQL does, and they're starting to catch up. MySQL > is still > much more primitive, and has severe limitations compared > to proper > database systems. > > The thing is, you see, MySQL was ready at the right time, > and became > the default "database system" for Linux applications. > This mirrors > the very fact that Linux is the default Open Source UNIX: > if AT&T > hadn't sued the University of California at Berkeley when > they did, > people would be running BSD instead of Linux. As it was, > Linux was > there when the time was right, and is now the de facto > standard, even > though it still has some catching up to do, quality-wise. > > -tih > -- > Tom Ivar Helbekkmo, Senior System Administrator, EUnet > Norway Hosting > www.eunet.no T +47-22092958 M +47-93013940 F +47-22092901 > FWD 484145 >
