| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | Dominique Devienne <ddevienne(at)gmail(dot)com> |
| Cc: | pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: How to force "re-TOAST" after changing STORAGE or COMPRESSION? |
| Date: | 2023-10-02 23:57:26 |
| Message-ID: | ZRtY5lEDPlSQuore@paquier.xyz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Mon, Oct 02, 2023 at 04:42:15PM +0200, Dominique Devienne wrote:
> According to the doc, the table is NOT changed.
> In my case, I DO want to have the bytea column rewritten
> according to the new STORAGE and/or COMPRESSION.
> The doc doesn't mention how to achieve that.
Yes, the compression type of the existed toasted values are not
changed after an ALTER SET, and that's not something one would do on a
daily basis, either.
> VACUUM?
> VACUUM FULL?
> Else?
VACUUM was considered as an option to force a rewrte, but it has been
removed because we were not sure that this is the correct path to do
so or that in some cases forcing the hand of the user was incorrect.
It was also creating a penalty in some of the hot loops of area:
commit: dbab0c07e5ba1f19a991da2d72972a8fe9a41bda
committer: Michael Paquier <michael(at)paquier(dot)xyz>
date: Mon, 14 Jun 2021 09:25:50 +0900
Remove forced toast recompression in VACUUM FULL/CLUSTER
Related thread:
https://postgr.es/m/20210527003144.xxqppojoiwurc2iz@alap3.anarazel.de
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Abhishek Bhola | 2023-10-03 00:08:16 | Re: pgBackRest for a 50 TB database |
| Previous Message | David G. Johnston | 2023-10-02 22:25:02 | Re: How to investigate deadlocks |