Video wird geladen...

Video konnte nicht geladen werden

Zur Startseite

🐘 Introducing Postgres Internals in 3D. 🌟 Stop reading boring diagrams. Start exploring PostgreSQL. An interactive 3D map to understand how Postgres actually works. 100% free. Built for developers.

45,984 Aufrufe • vor 6 Tagen •via X (Twitter)

19 Kommentare

Profilbild von Remotely
Remotelyvor 6 Tagen

wow! 3d!

Profilbild von alex shapalov
alex shapalovvor 6 Tagen

pi in 3d

Profilbild von ActiveRabbit
ActiveRabbitvor 6 Tagen

Finally, Postgres internals you can actually see. 🐘

Profilbild von pgrun.dev
pgrun.devvor 6 Tagen

Start with Disk → Memory → WAL.

Profilbild von alex shapalov
alex shapalovvor 6 Tagen

Good road map!

Profilbild von alex shapalov
alex shapalovvor 6 Tagen

I just spent an hour exploring this 3D map of PostgreSQL internals. Surprisingly addictive and inspiring! Now you’ll finally understand what the Postmaster actually does. 🐘

Profilbild von Gorka Cesium
Gorka Cesiumvor 5 Tagen

I bet @convex is already working on something similar

Profilbild von alex shapalov
alex shapalovvor 5 Tagen

@convex show me the link

Profilbild von Brinkin
Brinkinvor 5 Tagen

this feels like the future of realtime telemetry

Profilbild von alex shapalov
alex shapalovvor 5 Tagen

Exactly! Telemetry should be something you explore, not just dashboards you stare at)

Profilbild von al
alvor 5 Tagen

ooooooo Im going to use this...

Profilbild von alex shapalov
alex shapalovvor 5 Tagen

sure! let's learn PG!

Profilbild von matthew
matthewvor 5 Tagen

This is how is present architecture and system design now. UML and ADR are dead.

Profilbild von alex shapalov
alex shapalovvor 5 Tagen

This is how I present architecture and system design now.

Profilbild von Sujal
Sujalvor 5 Tagen

Can you click into a single query and watch it go through the planner?

Profilbild von alex shapalov
alex shapalovvor 5 Tagen

Click on INSERT

Profilbild von Sujal
Sujalvor 5 Tagen

ha, trying the INSERT one tonight

Profilbild von Brjan | AI Builder
Brjan | AI Buildervor 5 Tagen

interactive 3D maps could make complex concepts way more digestible for devs

Profilbild von alex shapalov
alex shapalovvor 5 Tagen

Yes, 🙌

Ähnliche Videos

Your Postgres is 100x slower than traditional OLAP engines. A deceptively simple OSS extension fixes this. Here's an interview where we dive into the deep engineering around how this is achieved. Joining me (and leading the conversation) is Marco Slot: an engineer with an EXTENSIVE and impressive career history around PostgreSQL: 👉 Created pg_cron in 2017 (3.7k stars) - a tool to run cron-jobs in Postgres 👉 Built pg_incremental - fast, reliable, incremental batch processing inside PostgreSQL itself 👉 co-created pg_lake (after working on Crunchy Data's Warehouse, and getting acquired into Snowflake) 👉 Helped get pg_documentdb (MongoDB-on-Postgres) off the ground Marco Slot is a world-class expert in Postgres extensions. He seriously impressed me with his knowledge over the course of a private LinkedIn conversation, and now that I type out his resume - I understand where it came from. He should be on everyone's radar. So I brought him on the pod. In our full 2-hour deep-dive, we went over: • 🔥 how pg_lake makes analytics 100x faster (literally) • 🔥 perf internals like vectorized execution & CPU branching • 🤔 practical differences between OLTP and OLAP database development (and the age-old mission in uniting both) • 🤔 how (and why) pg_lake intercepts query plans and delegates parts of the query tree to DuckDB • 💡 why Postgres is architecturally terrible at analytical queries (and how vectorized execution fixes this) • 💡 Marco's hard-won experience through a decade+ career in Postgres • 🏆 Iceberg's role as the TCP/IP for tables • 🏆 what the real moat of PostgreSQL is Developments like pg_lake are a real reason why "Just Use Postgres" is much more than a meme, and it'll continue to dominate discourse. I promise you will learn a lot from this episode. Timestamps: (0:02) What is pg_lake? (2:23) Postgres' 100x slower problem and columnar storage experiments they had to make Postgres fast for analytics (6:00) practical examples and internals (16:20) perf internals - vectorized execution & CPU optimization (23:00) pg_lake architecture (why DuckDB isn't embedded) and the connection-per-process issue (29:16) how pg_lake intercepts the query plan tree and delegates parts to DuckDB (41:09) Iceberg catalogs (48:24) postgres to iceberg ingestion patterns (and pg_incremental) (53:40) Marco's (long) career: early AWS, Citus, Microsoft, Crunchy Data & Snowflake (1:04:20) Marco's observations around the merging between OLTP and OLAP (and the subtle dev differences there) (1:15:30) reverse ETL (1:33:08) Iceberg as the TCP/IP for tables (1:35:00) Marco's thoughts on the "Just Use Postgres" fever

Stanislav Kozlovski

16,889 Aufrufe • vor 6 Monaten

Big moment for Postgres! AI coding tools have been surprisingly bad at writing Postgres code. Not because the models are dumb, but because of how they learned SQL in the first place. LLMs are trained on the internet, which is full of outdated Stack Overflow answers and quick-fix tutorials. So when you ask an AI to generate a schema, it gives you something that technically runs but misses decades of Postgres evolution, like: - No GENERATED ALWAYS AS IDENTITY (added in PG10) - No expression or partial indexes - No NULLS NOT DISTINCT (PG15) - Missing CHECK constraints and proper foreign keys - Generic naming that tells you nothing But this is actually a solvable problem. You can teach AI tools to write better Postgres by giving them access to the right documentation at inference time. This exact solution is actually implemented in the newly released pg-aiguide by Tiger Data - Creators of TimescaleDB, which is an open-source MCP server that provides coding tools access to 35 years of Postgres expertise. In a gist, the MCP server enables: - Semantic search over the official PostgreSQL manual (version-aware, so it knows PG14 vs PG17 differences) - Curated skills with opinionated best practices for schema design, indexing, and constraints. I ran an experiment with Claude Code to see how well this works, and worked with the team to put this together. Prompt: "Generate a schema for an e-commerce site twice, one with the MCP server disabled, one with it enabled. Finally, run an assessment to compare the generated schemas." The run with the MCP server led to: - 420% more indexes (including partial and expression indexes) - 235% more constraints - 60% more tables (proper normalization) - 11 automation functions and triggers - Modern PG17 patterns throughout The MCP-assisted schema had proper data integrity, performance optimizations baked in, and followed naming conventions that actually make sense in production. pg-aiguide works with Claude Code, Cursor, VS Code, and any MCP-compatible tool. It's free and fully open source. I have shared the repo in the replies!

Avi Chawla

187,280 Aufrufe • vor 9 Monaten