![]() ![]() I'd be surprised if hardware turned out to be a major component in a project this size.Īlso availability of skilled workforce would be a factor. Performance is also important as to keep costs low in hardware department. I'm not familiar with the policies of the various forks. That may change with Oracle being in charge. MySQL has had a somewhat more relaxed attitude to version numbers in the past. Always track the latest release of 9.1.x for the bugfixes. Release policy is strict, with bugfixes-only in the point releases. PostgreSQL has a strong developer team, with an extended community of contributors. Orders/day per account, couple of thousand accounts, eventually, eachĬan have several hundred to several thousand users.ĭoesn't sound that large - well within reach of a big box.īetter at: being future proof and flexible when it comes to growing Size of the project: Say an ordering system with roughly 10-100 Some of PostgreSQL's more recent SQL features (windowing functions, recursive WITH queries etc) are very powerful but if you have a dumb ORM they might not be usable. PostgreSQL's is less stupid in most cases. Is MySQL's query optimizer still stupid? Is it still super slow onĪll query optimizers are stupid at times. While I think that broadly the "PostgreSQL is a bit smarter than MySQL" statement is true, please don't depend on answers this old for details about current versions of software. People apparently still read it and occasionally click on the upvote button. Now, PostgreSQL is not perfect and probably the most obnoxious thing can be, to tune the dreaded VACUUM process for a heavy write database.ĮDIT: I answered this question over ten years ago. Not sure what you call "ease of use" but there are several modern SQL features that I would not want to miss (CTEs, windowing functions) that would define "ease of use" for me. When it comes to Spatial/GIS features Postgres with PostGIS is also much more capable. (treating any expression that can be converted to a non-zero number as "true" is not a proper boolean type) User defined data types (including check constraints) Parallel index creation (since Postgres 11) Roles (groups) to manage user privileges (MariaDB has them, Introduced with MySQL 8.0) SQL/JSON Path expressions (since Postgres 12) Update foo set x = y, y = x or update foo set a = b, a = a + 100 You cannot create a view that uses a derived table (Possible since MySQL 8.0) create view x as select * from (select * from y) You cannot use the table being changed (update/delete/insert) in a sub-select You cannot use a temporary table twice in the same select statement for unique indexes)įull text search on transactional tables (MySQL 5.6 supports this)ĮXCEPT or INTERSECT operator (MariaDB has them) INCLUDE additional column in an indexes (e.g. Window functions (Introduced with MySQL 8.0)įunction based index (supported since MySQL 8.0. Recursive queries (Introduced with MySQL 8.0) Table functions ( select * from my_function() )Ĭommon table expressions (Introduced with MySQL 8.0) Regular expressions don't support replace or substring (Introduced with MySQL 8.0) ![]() Regular expressions don't work with UTF-8 (Fixed with MySQL 8.0) MySQL silently uses an inner join with some syntax variations: Things that MySQL still doesn't have (and PostgreSQL has):Ĭheck constraints (MySQL 8.0. PostgreSQL is a lot more advanced when it comes to SQL features. Also availability of skilled workforce would be a factor. Size of the project: Say an ordering system with roughly 10-100 orders/day per account, couple of thousand accounts, eventually, each can have several hundred to several thousand users.īetter at: being future proof and flexible when it comes to growing and changing requirements. I am looking for few specific points not an overview + I trust StackOverflow more than some random page with 'smart guy' shining his light. Is MySQL's query optimizer still stupid? Is it still super slow on very complicated queries? Its almost 2012 now so I guess we could try and take a fresh look at the issue.īasically I would like to know if there is anything in PostgreSQL that out-weights ease of use, availability and larger developer/knowledge base of MySQL. I have read it all (well most) about mySQL vs pgSQL but most of those posts relate to version 4,5.1 and 7,8 respectively and are quite dated (2008,2009). Simple question - what would better for a medium/big size database with requirement for compatibility with ACID in 2012. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |