| From: | Nikita Malakhov <hukutoc(at)gmail(dot)com> |
|---|---|
| To: | Matthias van de Meent <boekewurm+postgres(at)gmail(dot)com> |
| Cc: | Aleksander Alekseev <aleksander(at)timescale(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, vignesh C <vignesh21(at)gmail(dot)com>, Jacob Champion <jchampion(at)timescale(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, Robert Haas <robertmhaas(at)gmail(dot)com>, Greg Stark <stark(at)mit(dot)edu>, Teodor Sigaev <teodor(at)sigaev(dot)ru> |
| Subject: | Re: Pluggable toaster |
| Date: | 2023-02-06 20:21:45 |
| Message-ID: | CAN-LCVOpseYfhfgr5MB=OHcCWjOpLk8P56gXxJkyRpU3CB11CQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
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
and simple.
--
Nikita Malakhov
Postgres Professional
https://postgrespro.ru/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2023-02-06 20:30:38 | Re: SLRUs in the main buffer pool - Page Header definitions |
| Previous Message | Andrey Borodin | 2023-02-06 20:16:03 | Re: pglz compression performance, take two |