Re: pg_stat_wal: tracking the compression effect - Mailing list pgsql-hackers

From Andrey Borodin
Subject Re: pg_stat_wal: tracking the compression effect
Date
Msg-id B373C608-3A22-4CD8-8630-D78F91BBB2B0@yandex-team.ru
Whole thread Raw
In response to pg_stat_wal: tracking the compression effect  (Ken Kato <katouknl@oss.nttdata.com>)
List pgsql-hackers

> On 25 Aug 2022, at 12:04, Ken Kato <katouknl@oss.nttdata.com> wrote:
>
> What do you think?

I think users will need to choose between Lz4 and Zstd. So they need to know tradeoff - compression ratio vs cpu time
spendper page(or any other segment). 

I know that Zstd must be kind of "better", but doubt it have enough runway on 1 block to show off. If only we could
persistcompression context between many pages... 
Compression ratio may be different on different workloads, so system view or something similar could be of use.

Thanks!

Best regards, Andrey Borodin.


pgsql-hackers by date:

Previous
From: Kyotaro Horiguchi
Date:
Subject: Re: Fix japanese translation of log messages
Next
From: David Rowley
Date:
Subject: Re: Reducing the chunk header sizes on all memory context types