Does this work with toast stored unchanged differently than logical? Or is it the same in terms need to merge with some last seen state of toasted field to project the whole of a changed tupled? Always a pita.
1. disabled
2. clickhouse, stores toast chunks on clickhouse then pulls them to resolve
3. shadow, stores toast in shadow catalog, obviously less latency than clickhouse but demands disk space