> The External TOAST pointer is very limited to the amount of service data > it could keep, that's why we introduced the Custom TOAST pointers in the > Pluggable TOAST. But keep in mind that changing the TOAST pointer > structure requires a lot of quite heavy modifications in the core - along with > some obvious places like insert/update/delete datum there is very serious > issue with logical replication. > The Pluggable TOAST was rejected, but we have a lot of improvements > based on changing the TOAST pointer structure.
Now I see what you meant [1]. I agree that we should focus on refactoring TOAST pointers first. So I suggest we continue discussing this in a corresponding thread and return to this one later.