Re: WAL compression setting after PostgreSQL LZ4 default change - Mailing list pgsql-hackers

From wenhui qiu
Subject Re: WAL compression setting after PostgreSQL LZ4 default change
Date
Msg-id CAGjGUA+rT0OczFZFSX0qgnfwbxWhzva+xKOQQzqj4e3KtjTkmg@mail.gmail.com
Whole thread
In response to Re: WAL compression setting after PostgreSQL LZ4 default change  (Hannu Krosing <hannuk@google.com>)
List pgsql-hackers
Hi 

> Based on this, I agree with the original suggestion to default to
>    zstd > lz4 > pglz
> I don't think we need to "tune" the compression levels for either of the
> algorithms. The defaults seem pretty reasonable.

Thank you for your test , It looks like Michael Paquier's suggestion was right—zstd doesn't have much difference in CPU consumption at default compression levels, and it achieves a higher compression ratio. On another note, I recall there was a patch discussing zstd compression for TOAST, but it hasn't been active for a long time. Since zstd offers a higher compression ratio, I think it's worth pushing this forward.


Thanks 

pgsql-hackers by date:

Previous
From: Peter Smith
Date:
Subject: Re: pg_createsubscriber: allow duplicate subscription names
Next
From: Tomas Vondra
Date:
Subject: Re: WAL compression setting after PostgreSQL LZ4 default change