Re: Counterintuitive behavior when toast_tuple_target < TOAST_TUPLE_THRESHOLD

Поиск
Список
Период
Сортировка
От Nikita Malakhov
Тема Re: Counterintuitive behavior when toast_tuple_target < TOAST_TUPLE_THRESHOLD
Дата
Msg-id CAN-LCVP39sP=G8HWG4N2FiM4ZCBA4-Hxd=Q3YLV3_vA93aWm0g@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Counterintuitive behavior when toast_tuple_target < TOAST_TUPLE_THRESHOLD  (Aleksander Alekseev <aleksander@timescale.com>)
Список pgsql-hackers
Дерево обсуждения
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 <aleksander@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 

В списке pgsql-hackers по дате отправления:

Чтобы сделать работу с сайтом удобнее, мы используем cookie и аналитический сервис «Яндекс.Метрика». Продолжая пользоваться сайтом, вы соглашаетесь с их использованием.