Re: Force re-compression with lz4

Поиск
Список
Период
Сортировка
От Magnus Hagander
Тема Re: Force re-compression with lz4
Дата
Msg-id CABUevEyJC1dX7RBu_otc9YRjW9BakXTLYoJ0cKrXwFfE957dmQ@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Force re-compression with lz4  (Michael Paquier <michael@paquier.xyz>)
Список pgsql-general
Дерево обсуждения


On Mon, Oct 18, 2021 at 7:18 AM Michael Paquier <michael@paquier.xyz> wrote:
On Sun, Oct 17, 2021 at 10:13:48PM +0300, Florents Tselai wrote:
> I did look into VACUUM(full) for it’s PROCESS_TOAST option which
> makes sense, but the thing is I already had a cron-ed VACUUM (full)
> which I ended up disabling a while back; exactly because of the
> double-space requirement.

Please note that VACUUM FULL does not enforce a recompression on
existing values.  See commit dbab0c0, that disabled this choice as it
introduced a noticeable performance penality in some cases when
looking at the compression type of the vacuumed table attributes:

Oh dang, I missed that this was reverted. Thanks for pointing that out!

--

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

Предыдущее
От: Michael Paquier
Дата:
Сообщение: Re: Force re-compression with lz4
Следующее
От: "Nick Renders"
Дата:
Сообщение: Re: PostgreSQL 14: pg_dump / pg_restore error: could not write to the communication channel: Broken pipe