| From: | Andrey Borodin <x4mmm(at)yandex-team(dot)ru> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: adding 'zstd' as a compression algorithm |
| Date: | 2022-02-17 06:12:50 |
| Message-ID: | C891A99F-513E-4103-9FB4-9F5A53DD6D32@yandex-team.ru |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> 15 февр. 2022 г., в 23:20, Robert Haas <robertmhaas(at)gmail(dot)com> написал(а):
>
> Anyway, those are my thoughts. What are yours?
+1 for adding Zstd everywhere. Quite similar patches are already a part of "libpq compression" and "zstd for pg_dump" commitfest entries, so pushing this will simplify those entries IMV.
Also I like the idea of defaulting FPI compression to lz4 and adding Zstd as wal_compression option.
I don't think Zstd is obvious choice for default FPI compression: there are HW setups when disks are almost as fast as RAM. In this case lz4 can improve performance, while Zstd might make things slower.
Thanks!
Best regards, Andrey Borodin.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Kapila | 2022-02-17 06:36:51 | Re: row filtering for logical replication |
| Previous Message | Kyotaro Horiguchi | 2022-02-17 05:58:38 | Re: [PATCH] Fix out-of-bouds access (src/common/wchar.c) |