Quote:
Originally Posted by daemonfowl
Maybe there no point arguing that one is always better than the other ..
|
Correct.
Quote:
|
Are there any particular cases when postgresql is more advisable to opt for ?
|
Historically, MySQL focused more on performance at the expense of following standard, but it was still adopted in the marketplace more than PostgreSQL. As a result, more people are probably familiar with MySQL than PostgreSQL.
On the other hand, PostgreSQL focused more on implementing the SQL standard than MySQL, but lagged in performance until the late 8.0x series. The PostgreSQL team is also working on making high availability
(HA) features solid. Performance in the 9.x series is significantly better too.
Personally, I prefer PostgreSQL because of its adherence to standards, the compatibility of its license to the BSD license, & the PostgreSQL mailing lists. The PostgreSQL development team is very active, & very helpful.
Until very recently, Mediawiki claimed compatibility with MySQL, however they made available information on how to work with PostgreSQL, but they made no guarantees on stability. Nevertheless, they now claim to support PostgreSQL. I do not have experience using Mediawiki with PostgeSQL to know how solid this compatibility is yet. You do the math.
The patched version of Apache 1.3 in OpenBSD's base installation is only getting older. Discussion on
misc@ indicates that at some point it will be dropped.
nginx(8) is already integrated into OpenBSD's base installation, & by reputation sports better performance & agility. People can over-emphasize performance issues, but this helps when using older hardware with isn't cutting edge.
Quote:
|
Or is it all a matter of habitual first-used-app ?
|
This can be a factor.