Why PostgreSQL is better than MySQL
blog.2ndquadrant.com
Why PostgreSQL is better than MySQL
1–10 of 100 posts
Re: Why PostgreSQL is better than MySQL
#2Does anyone have a link to a collective list of all known bugs in PostgreSQL?
Re: Why PostgreSQL is better than MySQL
#3MySQL is bad because they've tracked a bug across 3 different companies & working groups.
Postgres is good because we have no open bug tracker whatsoever and we're always adding new features!
I can't figure out who this article is for - certainly not DBAs!
Re: Why PostgreSQL is better than MySQL
#4Does anyone have a link to a collective list of all known bugs in PostgreSQL?
https://wiki.postgresql.org/wiki/Open_Items
This seems to be the canonical list.
Re: Why PostgreSQL is better than MySQL
#5MySQL is bad because they've tracked a bug across 3 different companies & working groups. Postgres is good because we have no open bug tracker whatsoever and we're always adding new features! I can't figure out who this article is for - certainly not DBAs!
2nd Quadrant is a DBA-as-a-service company that does only Postgres, so it makes sense that the target audience is decision-makers trying to pick between databases who are themselves not DBAs (but probably in the position of hiring DBAs, either as normal employees or as a company to contract with).
Re: Why PostgreSQL is better than MySQL
#6Does anyone have a link to a collective list of all known bugs in PostgreSQL?
https://wiki.postgresql.org/wiki/Open_Items This seems to be the canonical list.
Wow, this surprises me a lot, especially combined with the consensus position that Postgres is good, robust software. What is Postgres doing right and how can other projects follow their lead?
Re: Why PostgreSQL is better than MySQL
#7[deleted]
Re: Why PostgreSQL is better than MySQL
#8Does anyone have a link to a collective list of all known bugs in PostgreSQL?
https://wiki.postgresql.org/wiki/Open_Items This seems to be the canonical list.
FWIW that's a list of "open items" for PostgreSQL 10 release. So it's not really a "global" authoritative list of open issues, but something the project uses to make sure we deal with all known issues in the development version before the first release.
The claim that PostgreSQL does not have a bug tracker is not entirely accurate - there is no bugzilla/debbugs/...-style bugtracker (although it's a recurrent topic in discussions), but we do have pgsql-bugs mailing list. Which is mostly fine, as long as you fix bugs promptly and don't keep unsolved bugs lying around for years.
If you need to know what was fixed in a particular release, see either the release notes (high-level summary), or commits in the stable branches (those are typically just bugfixes, and the commit messages usually include a link to the relevant pgsql-bugs thread).
Re: Why PostgreSQL is better than MySQL
#9I'm a huge Postgres fan and yes I'm probably biased towards it. I do think it's probably the best open source database out there, but I also don't love these types of posts.
What makes something better than another things is a whole host of things, not just highlighting one really bad case from the other side. I'm sure if the MySQL world wanted they could point out ways that MySQL is so much better than Postgres. Just look back at how long it too for us to get upsert, we're finally getting a better replication story in recent years. To take this one case and highlight it doesn't put the Postgres community in a positive light and it's a shame, because most I know within the community value good engineering work.
MySQL has had a lot of people that contribute to it and has some good things about it, it might be worthwhile for us to pay more attention to where they are better and just focus on improving Postgres and leaving things at that.
Re: Why PostgreSQL is better than MySQL
#10Earlier quoted context omitted.
https://wiki.postgresql.org/wiki/Open_Items This seems to be the canonical list.
Wow, this surprises me a lot, especially combined with the consensus position that Postgres is good, robust software. What is Postgres doing right and how can other projects follow their lead?
Fix bugs, don't track them.