The Future of MySQL is Postgres? | Scaling Postgres 313
To get the show notes as well as get notified of new episodes, visit:
www.scalingpostgres.com/episo...
In this episode of Scaling Postgres, we discuss whether the future of MySQL is Postgres, how to use recursive CTEs, work on OrioleDB, and PG17 performance improvements.
Want to learn more about Postgres performance?
Join my FREE mini-course called the PostgreSQL Performance Starter Kit here: www.scalingpostgres.com/cours...
Timestamps:
00:00 - Intro
00:24 - The Future of MySQL is Postgres
03:26 - Recursive CTE's: Transforming and Analyzing Data in PostgreSQL, Part 3
04:20 - Oriole joins Supabase
07:25 - Waiting for Postgres 17: Faster B-Tree Index Scans for IN(...) lists and ANY =
10:01 - Massive DELETEs
11:48 - Auto-archiving and Data Retention Management in Postgres with pg_partman
12:23 - PGXN v2/Architecture
12:47 - 10psql Commands That Will Make Your Life Easier
13:36 - Announcing PGDSAT to satisfy CIS benchmarks for PostgreSQL
14:07 - A Deeper Look Inside PostgreSQL Visibility Check Mechanism
14:51 - PostgreSQL Internals Part3: Understanding Processes in PostgreSQL
15:08 - Outro
#postgres #postgresql
Пікірлер: 8
Wonderful video. Every day PostgreSQL establishes itself as the Operating System for data. This possibility of attachable storage engines caught my attention. A RAM compressed storage engine would be fantastic for readonly replicas and temporary loads. But in S3 I only see it as a lab experience, as the performance would be terrible.
keep the great work
It’s the same like NEONdb what supabase doing 😅
The core team is unlikely to commit syntax hooks into postgres.
I thought sqlite was top of the list... isn't it the most installed piece of software on the planet... on pretty much every OS and device...
For Postgres to replace MySQL/MariaDB it'll first need to get equivalent to Galera and so far I haven't seen any
Recursive cte, ugghhhh