It'll be great to see more opinions on the approach as a whole.
>The problem that I see being raised here, is that there was little >discussion and no observed community consensus about the design of >this complex feature *before* this patch with high complexity was >provided. >The next action that was requested is to take a step back and decide >how we would want to implement type-aware TOASTing (and the associated >patch compression dictionaries) *before* we look into the type-aware >toasting.
We decided to put this improvement as a patch because we thought
that the most complex and questionable part would be the TOAST
implementations (the Toasters) itself, and the Pluggable TOAST is
just a tool to make plugging different TOAST implementations clean
