Christophe Pettus: Table Access Methods Wake Up
The PostgreSQL Table Access Method (TAM) API is experiencing renewed interest with recent extensions. Two significant releases, storage_engine 1.0.7 and pg_sorted_heap 0.13.0, introduce new access methods that enhance functionality. The future of TAM and its integration with PostgreSQL's core features will be crucial in shaping the database's direction.
- ▪The TAM API has been part of PostgreSQL since version 12 but saw little activity until recently.
- ▪Recent extensions have introduced new access methods that improve performance and functionality.
- ▪The community is moving towards more pluggability in TAM, while vendors may resist this change to maintain their competitive edge.
Planet PostgreSQL files mainly under programming. We currently carry 28 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | Postgr |
| Canonical URL | https://postgr.es/p/9jx |
| Publication time | Wed, 20 May 2026 15:00:00 +0000 |
| Retrieval time | 2026-05-20T15:05:02.641Z |
| Last seen | 2026-05-20T15:05:06.214Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | KR-wWwE2JVPi |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
2026-05-20 3 min PostgreSQL Table Access Methods Wake Up The Table Access Method API has been in PostgreSQL since version 12. For most of that time it has been a quiet piece of infrastructure with very little extension activity attached to it — the kind of API that gets a paragraph in the docs, an enthusiastic conference talk, and then five years of silence. That is changing. In the last month, two TAM-shaped extensions shipped substantial releases. storage_engine 1.0.7 adds column-oriented compressed and row-compressed access methods for PG 16–18. pg_sorted_heap 0.13.0 provides a physically sorted heap with zone-map pruning and a planner-integrated vector search hook. Neither is going to displace the default heap tomorrow. Both are doing something interesting enough to look at.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Postgr.
Discussion
0 commentsMore from Postgr
