It's an interesting question then; the situations I see are the opposite: MySQL is the compatible solution already functioning, and a user would have to choose to change to Postgres.
Hey ("barely able to read"), thanks for being childish. It adds humour.
Maybe I misread your post -- you were asking why we don't change from MySQL to Postgres, since MySQL is the default server in most cases.
You were also converting a question about MySQL into an argument of "Postgres vs MySQL"; I was trying to explain why we don't change to Postgres. See, change-to-Postgres is an important part: there's no obvious benefit that outweighs the cost of changing. The cost of changing is also the cost of changing all of our dependencies to use Postgres.
So "why don't we change to Postgres?" Because it works, it's wellknown (we don't have to explain it), it has more compatibilities in the products our areas use.
Better than Postgres? Who cares? Maybe it is. We haven't had a reason to consider that, we're too busy getting to work, getting things done. p.I don't expect you to read this far; I expect you to take apart small subtle spelling mistakes, but you can take my lack of response to mean "hey, he's working, rather than wasting time debating bike shed paint colour options"
Many of us MySQL users see your Postgres question the same way: why use Postgres? There's 10 users of Postgres, and if I randomly toss both names into a room, I don't have to explain what MySQL is. Hell, half think I said "postfix" and leave the room.
What's MS SQL? OK, I'm kidding, but it makes me wonder if you've checked MySQL lately. I haven't had a reason to check Postgres, so I maybe just-as-satisfied with MySQL as you are with Postgres.
MySQL works for many of us. We don't want to switch to a different database in this tier of performance/cost. Plus, it's well-known outside of its fan-base, and is supported by a host of servers.
I'm not inviting a Postgres-vs-the-world fight here, I'm pragmatic, and the one that works and has better compatibility TODAY is MySQL. Maybe next year, that'll be Postgres among the circles I work in. Today, that tier is held by MySQL, smaller to SQLite, and larger to Oracle.
Bad advice.
Work experience can be faked, and everyone knows that. Degrees are harder to fake.
Now's a bad time to limit your options to "can only work in home country". Internationally, I see more countries require higher degrees to get work visas.
Two years of experience is not weak, by any means, but academic achievement is externally-verifiable.
For any international thoughts, go with the degree: Minimum degree for British Tier-1 Visa is Masters. Chinese see Ph.D as we see Masters, and a simple B.Sc is "well, OK, but weak".
While you're in the academic mode (no sleep, lots of study, brain like a sponge) use that to soak up a few more diplomas.
"A great many people think they are thinking when they are merely rearranging their prejudices." -- William James