wangbin579

@DiamondJoe6969 Just wait a bit. Around July 1, it’ll be free for everyone to use.

@wangbin579 🙏 please sir where is this tool

The database world is complex, especially Postgres. To truly understand how Postgres works inside, AI needs enough accurate trace data. That’s why I spent so much time building a trace tool.

@BenjDicken The trace tool will be free to use in the future.

@wangbin579 Is the tool open source?

@nosyeaj @franknnabugo Everyone who buys the course gets all future updates for life.

@wangbin579 @franknnabugo Hi @wangbin579 what about us who bought the version 1?

The deeper I studied Postgres extensions, especially TimescaleDB, pgvector, PostGIS, and PL/pgSQL, the more I realized how amazing Postgres’s design is. It took me another month to really understand how they work inside.

@franknnabugo There’s no documentation yet. I’m planning to release the second version of 'PostgreSQL Uncovered: Internals, Trace Analysis, and Performance' around July 1.

@wangbin579 Any good read you have ?

@franknnabugo It’s not about documenting these, but tracing them. That’s the most effective way to truly understand how a database works internally.

@wangbin579 Documented these? So I can study these extensions and Postgres internals

This paper is really eye-opening for MySQL users. The interesting part is that Postgres actually built GiST like this.

Most core mechanisms in MySQL and Postgres are no longer a mystery. Sometimes, knowing too much takes away the beauty.

@dadua_daku Parallel execution just gives more options and helps avoid bad plans.

@wangbin579 I don't know the query, but parallelism affects cardinality estimation. So with parallel plan it might have picked a better join order.

I saw a strange SQL query (refer to imdbload’s 26c.sql): with Postgres parallel execution on, it finished in seconds; with it off, it couldn’t finish even after hours. Smart people probably already know why.

The Postgres course will likely be upgraded before June 1, with more planner details and broader coverage of extensions. It might become one of the most technically deep courses I’ve ever built.

@0xRaghuboi We've already traced this, so we know how it works.

@wangbin579 pg trgm?

Beyond PostGIS, pgvector, TimescaleDB, and Citus, which Postgres extensions are truly worth tracing next?

MySQL 9.7 suddenly giving the Community Edition the hypergraph optimizer and a sane Hash Join cost model feels like a classic case of “a man speaks kindly when death is near.”

@mfreeman451 Here, tracing means following how the extension runs internally in order to better understand postgres itself.

@wangbin579 Apache AGE? not exactly sure what you're doing or mean by tracing?

@postgresnx This extension has no future.

@wangbin579 try orioledb, the new storage engine

To truly understand MySQL, you need to understand how Postgres approaches the same problems.The intermediate MySQL course is expected to be completed before May 1.

@alexeymakhotkin The SQL comes from github.com/winkyao/join-o…

@wangbin579 What is that schema? Looks like IMDB, but I cannot find exact match.

Be careful with complex SQL in MySQL. One bad plan can create a Cartesian product and bring your server down by consuming massive disk space. Postgres usually handles the same SQL much more safely.

Postgres handles this very well, with a very safe optimizer.