Trade-off options available significantly. The official release of the MySQL Falcon engine in the future is one likelyĪsynchronous Commit feature in PostgreSQLĨ.3 is another upcoming event that will shift the reliability/performance ![]() Version that it's believed the general guidelines here would be invalidated. This time that offer incremental improvements to some areas this documentĪddresses, but there are no fundamental differences so large in either new Operating systems vendors bundle and support it than the relatively new 8.2.īoth systems have newer versions in testing (PostgreSQL 8.3 and MySQL 5.1) at Moderately faster (perhaps as much as 30% so on some workloads), but deployingĨ.1 is still a completely viable option right now, particularly because more Performance, some comments here may refer to them collectively. Sinceīoth PostgreSQL 8.1 and 8.2 are currently supported versions with good PostgreSQL 8.2 and MySQL 5.0, and those are what's being compared here. The current production-ready versions as this is written in August of 2007 are Similar portions of the MySQL implementation have some seams resulting from how features like transactional support and strict mode were added onto the software well into its design lifecycle rather than being integral from the start.Ĭompared Versions, Feature Sets, and Focus It is also hoped that by exploring the differences between the two systems, you might come to appreciate how the fundamental approach of the PostgreSQL design team pervasively prioritizes reliable and predictable behavior. The position of this paper is that when the two are compared using the high level of data integrity demanded by a serious transactional database application, the current generation PostgreSQL performs similarly or better than MySQL (particularly under heavy user loads and with complex queries), while retaining its lead in the areas of SQL standards compliance and a rich feature set. Together in order to get an accurate view of the landscape. Performance against reliability, both these topics need to be considered Since it's often the case that you can trade-off Main areas covered here are the fundamental data integrity and speed issues of Production versions of each and discuss their strengths and weaknesses. More appropriate for than MySQL, attempting to fairly compare the current This document aims to clarify what situations PostgreSQL would be The result that it has gotten more difficult to objectivelyĭetermine which database is likely to be better suited for a givenĪpplication. Has actively made changes to address their respective sets of perceivedĭisadvantages. Focusing on improving performance has been central to all the 8.X releases up to the current 8.2.Īs innovation on these databases has progressed, each development community ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |