| From: | Andrey Borodin <x4mmm(at)yandex-team(dot)ru> |
|---|---|
| To: | Michael Paquier <michael(at)paquier(dot)xyz> |
| Cc: | Justin Pryzby <pryzby(at)telsasoft(dot)com>, Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>, Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, 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:17:26 |
| Message-ID: | 74CD8839-05DD-40F5-9609-58B79AD2151E@yandex-team.ru |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> 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.
BTW we could get rid of whole hole-in-a-page thing if we would set lz4 as default. This could simplify FPI code.
Thanks!
Best regards, Andrey Borodin.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kyotaro Horiguchi | 2021-06-16 08:35:58 | Re: detailed error message of pg_waldump |
| Previous Message | Kyotaro Horiguchi | 2021-06-16 08:00:08 | Re: Duplicate history file? |