Building a Table Access Method, Part 8: Cache invalidation
A backend keeps its mapping of the arena in its cache.
Badges come from GitHub once the author claims this feed.
A backend keeps its mapping of the arena in its cache.
Every `memtable` table now has an arena with a proper lifecycle, but nothing is stored in it.
In the previous two posts you could see how to manage storage for create and drop and also to work with transactions.
The arena of a memtable relation does not yet survive a rollback.