Re: Force re-compression with lz4

From: Magnus Hagander <magnus(at)hagander(dot)net>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: Florents Tselai <florents(dot)tselai(at)gmail(dot)com>, Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>, pgsql-general <pgsql-general(at)lists(dot)postgresql(dot)org>, Ron <ronljohnsonjr(at)gmail(dot)com>
Subject: Re: Force re-compression with lz4
Date: 2021-10-18 07:37:18
Message-ID: CABUevEyJC1dX7RBu_otc9YRjW9BakXTLYoJ0cKrXwFfE957dmQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Mon, Oct 18, 2021 at 7:18 AM Michael Paquier <michael(at)paquier(dot)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!

--
Magnus Hagander
Me: https://www.hagander.net/ <http://www.hagander.net/>
Work: https://www.redpill-linpro.com/ <http://www.redpill-linpro.com/>

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Nick Renders 2021-10-18 11:42:22 Re: PostgreSQL 14: pg_dump / pg_restore error: could not write to the communication channel: Broken pipe
Previous Message Michael Paquier 2021-10-18 07:32:22 Re: Force re-compression with lz4