> Not being sarcastic: this type of article always seems to be written with an audience of "people who love to pick a side and hate the other side, but haven't

> Not being sarcastic: this type of article always seems to be written with an audience of "people who love to pick a side and hate the other side, but haven't picked a side yet". > The article picks an extreme example and uses insinuation and condescencion to denigrate MySQL based on one example, but it goes further than that. For example: Yeah, I share this opinion. I may agree with some points Simon makes in the blog post, but I certainly dislike how it's presented. > Maybe, but if I wanted to contribute to Postgres where would I start? There's no bug tracker to look through. With the MySQL family, there is. I really doubt bug tracker is where people start their contributions. I mean, you don't go to a bug tracker, because (a) if it's broken someone else is probably already working on fixing it, and (b) the unsolved issues are rather complex and not quite suitable for new contributors. There's actually a bunch of pages on the wiki that might help you: * https://wiki.postgresql.org/wiki/So,_you_want_to_be_a_developer%3F https://wiki.postgresql.org/wiki/So,_you_want_to_be_a_develo... * https://wiki.postgresql.org/wiki/TODO https://wiki.postgresql.org/wiki/TODO (a nice list of development topics, including some quite simple ones) I'd recommend picking a feature that matters to you and either add it (if it's missing) or improve it in some way. That's how I started contributing - I improved a bunch of stuff in the internal statistics tracking, because I needed that. I improved a bunch of performance regressions, because they were affecting the systems in our production systems. And so on. Then start talking to people on pgsql-hackers. Send a patch, review patches from other people in the commitfests.