Hi! I've noticed this behavior half a year ago during experiments with TOAST, and TOAST_TUPLE_THRESHOLD really works NOT the way it is thought to. I propose something like FORCE_TOAST flag/option as column option (stored in attoptions), because we already encountered multiple cases where data should be stored externally despite its size. Currently I'm working on passing Toaster options in attoptions.
Thoughts? On Wed, Sep 14, 2022 at 7:12 PM Aleksander Alekseev < aleksan...@timescale.com> wrote: > Hi hackers, > > > 1. Forbid setting toast_tuple_target < TOAST_TUPLE_THRESHOLD > > Reading my own email I realized that this of course was stupid. For > sure this is not an option. It's getting late in my timezone, sorry :) > > -- > Best regards, > Aleksander Alekseev > > > -- Regards, Nikita Malakhov Postgres Professional https://postgrespro.ru/
