| From: | Nikita Malakhov <hukutoc(at)gmail(dot)com> |
|---|---|
| To: | Aleksander Alekseev <aleksander(at)timescale(dot)com> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Counterintuitive behavior when toast_tuple_target < TOAST_TUPLE_THRESHOLD |
| Date: | 2022-09-14 19:33:01 |
| Message-ID: | CAN-LCVP39sP=G8HWG4N2FiM4ZCBA4-Hxd=Q3YLV3_vA93aWm0g@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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(at)timescale(dot)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/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2022-09-14 19:33:46 | Re: archive modules |
| Previous Message | Peter Eisentraut | 2022-09-14 19:31:04 | Re: archive modules |