Re: tableam vs. TOAST

Andres Freund <andres@anarazel.de>

From: Andres Freund <andres@anarazel.de>

To: Robert Haas <robertmhaas@gmail.com>

Cc: Alvaro Herrera <alvherre@2ndquadrant.com>, Prabhat Sahu <prabhat.sahu@enterprisedb.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>

Date: 2019-09-05T19:10:15Z

Lists: pgsql-hackers

Hi,

On 2019-09-05 13:42:40 -0400, Robert Haas wrote:
> Done, thanks. Here's the rest again with the additional rename added
> to 0003 (formerly 0004). I think it's probably OK to go ahead with
> that stuff, too, but I'll wait a bit to see if anyone wants to raise
> more objections.

Well, I still dislike making the toast chunk size configurable in a
halfhearted manner.

Greetings,

Andres Freund

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