I really suggest MySQL developers and enthusiasts study Postgres in depth. It might answer a lot of the questions you’ve been wondering about.

Owing to the extensive depth of the planner content, including 45 days dedicated to developing the trace tool, 20 days of material preparation, and 10 days of writing, even with full effort I still need five more days for final refinement. I apologize for the delay and appreciate

Plans often fall behind reality. Six months into the Postgres course, I still have no idea when I’ll actually finish it, but at least I think I have already mastered the toughest part, the planner.

Anyone truly passionate about databases should study Postgres internals, especially the planner and extensions. Without this knowledge, a database career is incomplete.

Once you understand Postgres internals, you will at least realize: (1) There is no perfect database in the world today. (2) Building on MySQL, especially for distributed databases, is so painful. (3) MySQL is weak at handling joins, even with more advanced dynamic programming

To explain extensions clearly in my postgres course, I spent a lot of time tracing citus, which took at least a full week. I doubt anyone in the future will dig so deeply into postgres just to write a book or teach a course. Would you?

The distributed planner in citus is basically a heuristic planner with simple logic. A real distributed planner is much more complicated than what citus has. I’ve also seen most of the major flaws in the extension approach.

This case shows that the plan citus picked is definitely not the best. After digging through a lot of traces, I can only say citus still isn’t very mature.

To really understand Postgres extensions, you need to know how the planner works internally. Otherwise, it is impossible to explain how an extension actually works.

The third part of the Postgres course covers extensions. Postgres enthusiasts can skip it, but anyone who truly loves MySQL should take a look.

This course explains how Postgres works under the hood with a strong hands-on focus. It helps people who love databases understand design ideas and DSA much more easily.

Thanks to everyone who bought my course. I didn’t make much money from it, but your support truly means a lot to me and keeps me motivated. Don’t worry about me. No matter how poor I get, I won’t end up on the street. Last week, I spent about a million dollars buying an

From a learning perspective, PostgreSQL is about three times more complex than MySQL, even though its name is only twice as long.

Some DBAs may see MVCC as the hardest part to learn, but in my opinion, the real challenge is DSA, particularly the planner and extension mechanisms. Without understanding these, it is hard to truly understand Postgres at a deeper level.