The Future of Postgres Sharding
summary
Covers database sharding for PostgreSQL, explaining why sharding is necessary for multi-server read-write scaling versus vertical scaling or read-only scaling. Discusses required future PostgreSQL features for practical sharding such as enhancements to foreign data wrappers, increased parallelism, and mechanisms for global snapshots and transaction control.
AI-written summary · about
chapters (10)
- 0:00Start
- 12:59Vertical Scaling
- 17:41Non-sharding Horizontal Scaling
- 20:26Typical Sharding Criteria
- 28:33Advantages of Fow Sorvlon Aggregate Pushdown
- 30:15Query Routing and DDL to Proper Shards
- 31:53Advantages of Parallel Fow Access
- 32:28Implementing a Global Snapshot Manager
- 33:20Implementing a Global Transaction Manager
- 34:18Conclusion
related talks
33mFive Sharding Data Models and Which is Right
52mSharding PostgreSQL using Foreign Data Wrappers
34mPostgreSQL sharding, state of the art
42mPostgreSQL Distributed & Secure Database Ecosystem Building
42mSharding Postgres without doing it yourself
47mpg_shardman: Sharding in PostgreSQL
51mUsing Postgres FDW with a sharded PostgreSQL Database
53mBreakout Session