Re: tableam vs. TOAST

Robert Haas <robertmhaas@gmail.com>

From: Robert Haas <robertmhaas@gmail.com>

To: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>

Date: 2019-06-11T16:17:01Z

Lists: pgsql-hackers

Attachments

v3-0003-Allow-TOAST-tables-to-be-implemented-using-table-.patch (application/octet-stream) patch v3-0003
v3-0001-Split-tuptoaster.c-into-three-separate-files.patch (application/octet-stream) patch v3-0001
v3-0002-Create-an-API-for-inserting-and-deleting-rows-in-.patch (application/octet-stream) patch v3-0002

On Tue, May 21, 2019 at 2:10 PM Robert Haas <robertmhaas@gmail.com> wrote:
> Updated and rebased patches attached.

And again.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

Commits

tableam: New callback relation_fetch_toast_slice.
- ce242ae154dd 13.0 landed
tableam: Allow choice of toast AM.
- 83322e38da1a 13.0 landed
Move heap-specific detoasting logic into a separate function.
- e9fd0415e6e2 13.0 landed
Code cleanup for toast_fetch_datum and toast_fetch_datum_slice.
- d5406dea25b6 13.0 landed
Rename some toasting functions based on whether they are heap-specific.
- 2e8b6bfa90b2 13.0 landed
Create an API for inserting and deleting rows in TOAST tables.
- bd124996ef0d 13.0 landed
Split tuptoaster.c into three separate files.
- 8b94dab06617 13.0 landed
tableam: Move heap-specific logic from needs_toast_table below tableam.
- 1171d7d58545 12.0 cited