Future of table access methods
summary
Postgres gains a concrete patch set to let alternative table access methods do real work: a new enum for row references that adds row ID (an arbitrary byte array) to replace fixed itempointer semantics, changes to return the correct slot on inserts into partitions, a new tuple insert with arbiter API to replace speculative tokens for ON CONFLICT, custom ANALYZE hooks, a vadm cache callback for complex caches, and index-definition callbacks for TAM-managed indexes. audioDB exists as an index‑organized prototype using an undo log and its own B‑tree implementation; patches land on GitHub and are planned for pgsql-hackers.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 1:00Postgres table access overview
- 5:55The row ID patch
- 12:05Conflict handling and checks
- 18:31Advanced API improvements
- 23:34Cache management
- 25:39Collaboration and conclusions
- 29:28Q&A session
related talks
50mSolving PostgreSQL Wicked Problems
42mAnatomy of Table-Level Locks in PostgreSQL
39mAnatomy of Table-Level Locks in PostgreSQL
54mBreakout Session
49mSELECT 'amazing features' FROM "postgresql"
21mAnalytics in Postgres –A decade in the making
51mExploring new enhancements and improvements Fujitsu has delivered to
01h 09mReplacing Oracle Features in PostgreSQL: HA, Functions & Extensibility