Re:Pluggable Storage Committed in Postgres
by michelpp on Friday April 05, 2019 @01:22AM
(#19579937)
Thank for the context, this is great! I'm looking into this now to see if I can use it with my project pggraphblas, i was hoping to make an FDW where each column is backed by a matrix, making essentially a "property graph" that can be queries with straight SQL, but this looks much more interesting and also easier to use.
next step --> "ZHEAP" = a storage engine to provide better control over bloat:
* http://amitkapila16.blogspot.com/2018/03/zheap-storage-engin... ( 5 March 2018 )
"PLUGGABLE STORAGE IN POSTGRESQL" (2018 PGCONF.EU ; Andres Freund)
pdf: https://anarazel.de/talks/2018-10-25-pgconfeu-pluggable-stor...
""Why?
● ZHeap – UNDO based storage, address bloat and write amplification problems
● Columnar Storage
● Experiments
""
"PostgreSQL has long prided itself in being extensible. But for a number of years people have wished for the ability to not only introduce new datatypes and functions, but also to add new forms of storing data. The introduction of foreign data wrappers (FDWs) allowed to satisfy some of those use-cases. They however are not fully suitable for native data storage, quite fundamentally they don't allow for index creation, foreign keys, etc.
Over the last years people have on and off worked on making table storage pluggable. It looks like PostgreSQL 12 might finally get builtin support for that, based on work of Haribabu Kommi, myself and others.
This talk will go over the reasons why it is useful to make storage pluggable (my personal reason is to allow the introduction of zheap, a new undo based table storage that is nearly free of table bloat) and how the new APIs work, and what further use-cases the pluggable storage APIs have."