Next steps for Postgres pluggable storage

PostgreSQL's pluggable storage allows developers to use different storage engines for different tables within the same database, enabling optimized performance for specific workloads. The technology has been introduced in PostgreSQL 12 with initial support for ZHeap, but current progress has stalled due to limitations in the table access method API. Despite this, several initiatives are underway, including community updates and upstreaming code from OrioleDB, which aims to bring pluggable storage to the Postgres core. With ambitious timelines, pluggable storage could land in PostgreSQL 17, making it an even more attractive option for developers.

No tracked trend matches for this post yet.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.