| From: | Heikki Linnakangas <hlinnaka(at)iki(dot)fi> |
|---|---|
| To: | Andrey Borodin <x4mmm(at)yandex-team(dot)ru>, Michael Paquier <michael(at)paquier(dot)xyz> |
| Cc: | Justin Pryzby <pryzby(at)telsasoft(dot)com>, Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, Peter Geoghegan <pg(at)bowt(dot)ie>, Andres Freund <andres(at)anarazel(dot)de> |
| Subject: | Re: Different compression methods for FPI |
| Date: | 2021-06-16 08:49:51 |
| Message-ID: | 12b029ee-d9db-20f4-f4f8-2b2dad3e5091@iki.fi |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 16/06/2021 11:17, Andrey Borodin wrote:
>> 16 июня 2021 г., в 12:18, Michael Paquier <michael(at)paquier(dot)xyz> написал(а):
>> Among the
>> remaining two I would be tempted to choose LZ4. That's consistent
>> with what toast can use now.
>
> I agree that allowing just lz4 - is already a huge step ahead.
> But I'd suggest supporting zstd as well. Currently we only compress 8Kb chunks and zstd had no runaway to fully unwrap it's potential.
> In WAL-G we observed ~3x improvement in network utilisation when switched from lz4 to zstd in WAL archive compression.
Hmm, do we currently compress each block in a WAL record separately, for
records that contain multiple full-page images? That could make a big
difference e.g. for GiST index build that WAL-logs 32 pages in each
record. If it helps the compression, we should probably start
WAL-logging b-tree index build in larger batches, too.
- Heikki
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrey Borodin | 2021-06-16 08:52:50 | Re: Different compression methods for FPI |
| Previous Message | Peter Eisentraut | 2021-06-16 08:48:20 | Re: Signed vs. Unsigned (some) |